Planning (Focus Area)
Focus Areas are not project phases. They describe categories of work that can occur at any point in the life cycle and often overlap dynamically.
Definition
The Planning Focus Area consists of those processes, practices, or actions that establish the intended scope of the effort, define and refine the objectives, and develop the course of action required to attain those objectives. Activities may include developing a product backlog or a project management plan.
Planning can follow a progressive, iterative, or rolling wave approach according to the project phase or life cycle. As project changes are encountered, update planning may be required at any moment — this ongoing refinement is called progressive elaboration. Highly predictive approaches tend to front-load planning; highly iterative approaches perform brief high-level roadmapping up front followed by consistent frequent planning throughout. The key benefit is to define the course of action for successfully completing the project or phase.
Processes by Domain
Planning is the most process-dense focus area — nearly every domain contributes processes here.
| Process | Domain |
|---|---|
| Integrate and Align Project Plans | Governance Domain |
| Plan Sourcing Strategy | Governance Domain |
| Plan Scope Management | Scope Domain |
| Elicit and Analyze Requirements | Scope Domain |
| Define Scope | Scope Domain |
| Create WBS / Product Backlog | Scope Domain |
| Plan Schedule Management | Schedule Domain |
| Develop Schedule | Schedule Domain |
| Plan Financial Management | Finance Domain |
| Estimate Costs | Finance Domain |
| Develop Budget | Finance Domain |
| Plan Stakeholder Engagement | Stakeholders Domain |
| Plan Communications Management | Stakeholders Domain |
| Plan Resource Management | Resources Domain |
| Estimate Resources | Resources Domain |
| Plan Risk Management | Risk Domain |
| Identify Risks | Risk Domain |
| Perform Risk Analysis | Risk Domain |
| Plan Risk Responses | Risk Domain |
Key artifacts created
- Project management plan — unified plan containing all subsidiary plans and baselines
- Scope baseline — scope statement + Work Breakdown Structure (WBS) + WBS dictionary
- Schedule baseline — approved project schedule with milestones and critical path
- Cost baseline — time-phased budget including contingency reserve (excludes management reserve)
- Requirements Documentation — functional and non-functional requirements with traceability
- Risk Register — identified risks with probability/impact ratings and response strategies
- Change Management Plan — change control board, approval thresholds, escalation paths
- Stakeholder engagement plan — engagement strategies per stakeholder
- Communications management plan — methods, frequency, channels per stakeholder
- Resource management plan / team charter — roles, responsibilities, RACI Chart
- Integrated Baseline — scope + schedule + cost baselines combined as PMB
Key activities
- Integrate and align all plan components into a unified project management plan
- Define and refine project objectives, scope statement, and Requirements Documentation
- Develop schedule baseline (activity list, network diagram, CPM, critical path)
- Develop cost baseline (estimate costs, develop budget, establish reserves)
- Plan quality management (acceptance criteria, quality metrics, QA/QC approach)
- Plan resource management (team charter, RACI Chart, resource calendar)
- Plan risk management and populate initial Risk Register
- Plan stakeholder engagement and communications management
- Plan sourcing strategy (make-or-buy decisions, contract types)
- Establish Change Management Plan and change control board (CCB)
Agile / hybrid considerations
- Planning is iterative — release planning at portfolio/program level, sprint planning at team level each iteration
- Inverted Triangle: in adaptive, scope is variable; time and budget are fixed — the plan reflects this constraint model
- Rolling wave planning: near-term activities planned in detail; distant activities planned at high level and elaborated as project unfolds
- Adaptive teams replace the project management plan with a lightweight backlog and team agreements; roadmapping replaces detailed upfront scope/schedule/cost baselines
Exam angle
- Planning is ongoing: plans are progressively elaborated throughout the life cycle — wrong answers treat planning as a one-time upfront activity that ends when execution begins
- Amount of planning matches complexity: over-planning on a simple project is waste; under-planning on a complex, high-risk project is negligence — tailor the depth
- Adaptive planning is intentional: absence of a detailed upfront scope baseline in agile is a deliberate and valid choice — not a sign of poor discipline
- Plan vs. baseline: a working estimate can be updated freely; a baseline is the approved version — changing a baseline requires formal change control through the CCB