Develop Project Management Plan
Foundational concept
Not named in the current ECO. Still worth knowing — it underpins the situational questions and PMI's own experience verification uses the process groups.
Develop Project Management Plan is the process of defining, preparing, and coordinating all plan components and consolidating them into an integrated project management plan.
Know it well enough for the exam? Questions on Develop Project Management Plan are scenario-based, not definitional.
Practice it freeExplanation
This process produces the project management plan, the single most important document for guiding project execution. The plan integrates all subsidiary plans (scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder management plans) along with baselines for scope, schedule, and cost. It serves as the central reference for how the project will be planned, executed, monitored, controlled, and closed.
Key inputs to this process include the project charter, outputs from other planning processes, enterprise environmental factors, and organizational process assets. The primary tools and techniques are expert judgment, data gathering (such as brainstorming and checklists), interpersonal and team skills (conflict management, facilitation, meeting management), and meetings. The plan is progressively elaborated as more information becomes available.
Once the baselines within the project management plan are approved, changes can only be made through the Perform Integrated Change Control process. The plan is not a static document; it may be updated throughout the project. However, any change to a baseline requires a formal change request and approval, ensuring that project performance is measured against an agreed-upon reference.
Key Points
- •Integrates all subsidiary management plans and baselines into one comprehensive document
- •The project charter is a key input; outputs from other planning processes feed into it
- •Changes to baselines require formal change requests through integrated change control
- •Progressively elaborated as more project information becomes available
Exam Tip
The project management plan is approved by the sponsor and key stakeholders. Once baselines are set, any changes must go through Perform Integrated Change Control — you cannot modify baselines informally.
Frequently Asked Questions
Related Topics
Project Charter
A project charter is a document issued by the project sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Work Breakdown Structure (WBS)
A work breakdown structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Schedule Baseline
The schedule baseline is the approved version of the schedule model that is used as a basis for comparison with actual results to determine if corrective or preventive action is needed.
Cost Baseline
The cost baseline is the approved version of the time-phased project budget, excluding management reserves, used as a reference for measuring and monitoring cost performance.
Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests, approving or rejecting changes, managing changes to deliverables, project documents, and the project management plan, and communicating the decisions.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Part of
Integration Management
Practice Develop Project Management Plan
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.