This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: 1 Chapter 5 Planning Fundamentals Project Management for Business, Engineering, and Technology Common Elements of Project Plan 1. Scope Statement, Charter, SOW 2. Detailed requirements 3. Project organization and responsibility for tasks 4. Detailed work definition (WBS or PBS and work package/work task details) 5. Detailed schedules with milestones 6. Project budget and cost accounts 7. Quality plan Elements of Project Plan 8. Risk plan 9. Work review plan 10. Testing plan 11. Change control plan 12. Documentation plan 13. Procurement plan 14. Implementation plan Element 2 has already been discussed. This chapter focuses on elements 1,3,4, and aspects of 5 and 13. The remaining elements are addressed in later chapters. Scope, Charter, and SOW Scope, charter, or SOW: Is the first item on project master plan. Variations on same theme Purpose provide broad description of master plan/project to stakeholders directed at core project team, project organization, primary stakeholders Scope Describes breadth of project, areas to be covered by project and deliverables & areas not covered. Includes: Objectives of project from perspective of contractor Requirements Deliverables Milestones Limits and exclusions: what project does not include SOW SOW, Statement of Work, is the scope document for contracted projects Appears in RFP, proposal, contract, as well as master plan 2 Defining the SOW 1. For contracted project work Contractor and customer agree on definition of work required, work proposed, and basis for costs, schedules, and related matters. There are two SOWs, SOW in master plan SOW in contract (CSOW) SOW in contractor’s project plan must contain same information and requirements as stated in CSOW. Contractor’s SOW and CSOW might be worded differently, but both should have exact same interpretation in terms of work and end results Defining the SOW 2. Suggestions Ensure that SOW and WBS correspond to each other. Both must be clear; neither contractor nor customer question what has to be done. Requirements for every end-item, task, and report must be clear enough so parties responsible will be able to sign-off acceptance of results. Never specify tasks using “as necessary” or “as required”. Where judgments must be made, specify who will make them, procedures for making them, and potential impact of judgments on cost and schedule escalation. Issues in Defining SOW 2. Suggestions: Specify requirements using active terminology (“shall” or “will”) Never use passive terminology (“should” or “try to”). “shall” = must do “will” = desirable to do Issues in Defining SOW 2. Suggestions Categorize specifications applicable to entire project separately from those applicable to only parts of project....
View Full Document
- Fall '10
- Project Management