ABSTRACT
At this point, the project manager has a project plan with sections for charter, scope, schedule, budget, quality, risk, stakeholders, communication, and teaming.
These are all interdependent, and consistency across all this work is important. Since each piece of the plan builds on prior sections, the project plan is likely consistent if the project manager looks backwards to prior pieces of the project plan as he continues development. For example, the tasks of the schedule section build on the work packages of the WBS in the scope section. As the project manager completes the schedule, he looks back to the WBS to see if changes might be necessary. Budget information builds on the tasks; once the budget is complete, he looks back to see if any additions or deletions to tasks might be necessary. Quality builds on the top level deliverables of the WBS, and risk builds on all of these components. As he builds on the information of prior sections, the project manager determines if changes are necessary and ensures he incorporates the impact of these changes as appropriate. For example, if he added a risk response task to the WBS, he verifies that he’s added the necessary schedule and budget to the project plan.
