The Project Management Plan: A Living Document for Execution and Control

PMBOK v8 Definition

The project management plan specifies how the project will be executed, monitored and controlled, and closed. It defines the basis for all project decisions and is a living document that can be expected to change over time. This plan is not a process but a comprehensive document that integrates all subsidiary management plans.

Why It Matters for the Exam

The project management plan appears in approximately 15-20% of PMI exam questions, particularly in scenarios asking what document guides project execution or defines how changes should be managed. Exam questions frequently test your ability to identify which subsidiary plans belong to the project management plan versus other project documents.

Key Points to Remember (for the exam)

• Living Document: The project management plan is expected to change over time – it is not static
• Basis for All Decisions: Every project decision must align with the project management plan
• Components Include: Change management plan, communications management plan, financial management plan, iteration plan, procurement management plan, quality management plan, requirements management plan, release plan, resource management plan, risk management plan, schedule management plan, scope management plan, sourcing strategy plan, stakeholder engagement plan, and test plan
• Integration Focus: The plan unifies all subsidiary plans into one coherent document
• Not a Project Charter: The project charter authorizes the project; the project management plan defines how to execute it
• Configuration Management Plan: A component of the project management plan that tracks project artifacts and monitors/controls changes to them

Typical PMI Exam Example

A project manager is about to begin project execution. The sponsor asks what document defines how scope changes will be handled. The project manager should reference the change management plan, which is a component of the project management plan.

PMI Exam Traps

• Trap: Confusing the project management plan with the project charter

• Reality: The charter authorizes the project and assigns the project manager; the project management plan guides execution, monitoring, and closure

• Trap: Thinking the project management plan is finalized before execution begins

• Reality: It is a living document that changes over time based on stakeholder recommendations and project needs

• Trap: Assuming the project management plan is one single document without components

• Reality: It typically consists of 15+ subsidiary plans (change, communications, financial, iteration, procurement, quality, requirements, release, resource, risk, schedule, scope, sourcing strategy, stakeholder engagement, and test plans)

• Trap: Confusing the configuration management plan with the change management plan

• Reality: Configuration management tracks and controls artifacts; change management controls changes to the project baselines

Important PMI Connections

Quick Review Questions

1. Which document defines the basis for all project decisions and is expected to change over time?
2. Name at least five subsidiary plans that are components of the project management plan.
3. What is the difference between the change management plan and the configuration management plan?
4. During which process group is the project management plan primarily created?
5. If a stakeholder requests a change during execution, which component of the project management plan should the project manager reference first?

PMBOK v8 Reference

Section 2.1.6 - Project Management Plan (definition and components as provided in the PMBOK v8 RAG context)