The project management plan describes the development approach, life cycle, and how the project will be executed and controlled. It identifies when project management reviews are needed and contains the performance measurement baseline (scope, schedule, and cost baselines). It integrates plans for managing:
Category | Icon | Description |
---|---|---|
Scope + Resources | π― + π₯ | What is included in the project and who/what resources are needed |
Requirements + Communications | π + π’ | Stakeholders' needs and how info is shared |
Schedule + Risk | π + β οΈ | When tasks happen and how risks are managed |
Cost + Procurement | π° + π | Budgeting and acquiring necessary goods/services |
Quality + Stakeholder Engagement | β + π€ | Maintaining standards and involving stakeholders |
Management plans describe the strategy and approach for managing the project β including constraints and integration points like communications and stakeholder engagement.
Key questions to ask:
Management plans contain:
to ensure consistent, predictable results.
Management plans are tailored per project and evolve in format and detail.
Example: Cost Management
In Agile/hybrid environments, separate management plans may not exist as discrete documents; instead, theyβre embedded in product backlogs and release roadmaps. Plans include risk response, delivery timing, and work planning.
The doing part of the plan β how work will be performed.
For example, the cost management plan executing component answers:
Defines how progress will be:
Imagine how this applies to: Scope, schedule, quality, resources, communications, risk, procurement, stakeholder engagement.
Additional plans include:
The centralized artifact that integrates all individual management plans and baselines, including:
Agile and hybrid approaches may tailor these components adaptively.
Baseline | Includes | Icon |
---|---|---|
Scope baseline | Project scope statement, WBS, WBS dictionary | π― |
Schedule baseline | Agreed schedule, milestones | π |
Cost baseline | Time-phased budget (approved spending plan) | π° |
Deviations prompt assessment and possibly change requests. Baseline changes are documented carefully. Effective risk management reduces baseline deviations.
Defines how requirements will be:
Prepares for controlling changes to avoid negative impact:
Details artifact management:
Ensures stakeholders have access to latest documents and versions.
Aspect | Description | Icon |
---|---|---|
Project Life Cycle | Phases needed to produce deliverables (plan-driven to change-driven) | π |
Development Approach | Range from plan-driven to change-driven approaches | π οΈ |
Management Reviews | Scheduled milestones for evaluating progress and adjusting plans | β |
Tailoring | Customizing processes and extent of use based on project needs | βοΈ |
Individual Management Plans | Plans for scope, schedule, cost, quality, resources, communications, risk, procurement, stakeholder engagement | π |