PROJECTMANAGEMENTPrinciplesandPractices文件材料.ppt

* * * * * * Use the skiing exercise. * * * * * * * Project progress reviews are necessary; but they should focus on looking AHEAD rather than looking back (except to learn from the past). Stakeholders are more interested in whether or not you think you’ll arrive on time, within budget, and with the functionality - rather than dwell on all of your accomplishments to date (although they should be celebrated). * * * * * Ask the class - get participation. Look for time (schedule), cost (budget), and performance (functionality). * * * * Standard work (KOS-C) exists for each major phase. More about this in a few slides. * * Every project needs a sponsor (more than 3 may be too many). Who will clarify the goals, remove obstacles, secure resources, reward the team for success? Who cares about this project? Who has it on their MPCP? If you struggle with these questions, your project is doomed. When someone says “I’m the sponsor”, you can then confirm the roles in this slide with them. Do they understand what it means to be a sponsor? * * * * * * KOS-C postings to support business case analysis include DRA/Bus Case, Determining Price, and Determining Volume. * I’m trying to figure out how (and how deeply) to mention system engineering here. There’s certainly a fit for SE in the initiation stage, where an output is the requirements documents (Kathy Jo Connors will talk about requirements on 5/17). SE can also play a role in the planning stage with the WBS development, and in the execution stage with testing, and the closure stage with customer verification. Keech will talk about Image Quality and SE on 5/22. Toby Berke will address reliability on 5/24. * * WBS on pp. 19-24….some of this was copy/pasted directly into the KOS-C WBS section. The KOS-C version may provide a little more detail that isn’t necessary in the 1-day course. * * When you get to “task” level, you should have a small phrase with a verb and noun, e.g., “purchase concrete” or “pour concrete”. Exa