Develop Project Management Plan

Sensei Short Scroll 3 Planning Process Group

Develop Project Management Plan

Introduction: Why This Matters

The project management plan is the single most important document a project manager produces during Planning. It integrates all subsidiary plans and baselines into one cohesive guide that directs execution, monitoring, and closing. Without this plan, teams lack alignment, stakeholders lack clarity, and changes become chaotic (Project Management Institute, 2021).

On the PMP exam, many situational questions test whether you understand that the project management plan must be consulted before making decisions, such as approving changes, reallocating resources, or updating baselines. In practice, the plan is the reference point for all controlled project actions.

Purpose and Objectives

Primary Purpose: To create an integrated document that defines how the project will be executed, monitored, controlled, and closed.

Key Objectives:

  • Integrate all subsidiary plans and baselines.
  • Define the methodology and approach (predictive, agile, or hybrid).
  • Provide a consistent framework for decision making and communication.
  • Establish standards for scope, schedule, cost, quality, risk, and resource management.
  • Serve as the reference for change control and performance measurement.

Overview

The project management plan is not a single document created in one pass. It evolves as subsidiary plans are developed and is progressively elaborated. This process pulls together outputs from all other planning activities and fuses them into one integrated guide.

  • Planning focus: Consolidate decisions about how the work will be done and controlled.
  • Coverage: Includes subsidiary plans, baselines, life cycle, and development approach.

Characteristics

  • Input driven: Uses the project charter, outputs from other planning processes, enterprise environmental factors, and organizational process assets.
  • ITTO focus: Relies on expert judgment, data gathering, interpersonal and team skills, and planning workshops to create a realistic and aligned plan.
  • Integrated output: Produces a single project management plan that includes all baselines and subsidiary plans.
  • Progressively elaborated: The plan is updated and refined as more information becomes available and as approved changes are incorporated.

ITTO View

Inputs

  • Project charter.
  • Outputs from other planning processes (scope, schedule, cost, risk, quality, and others).
  • Enterprise environmental factors (policies, culture, regulations).
  • Organizational process assets (templates, governance standards).

Tools and Techniques

  • Expert judgment (PMO, senior leaders, subject matter experts).
  • Data gathering (brainstorming, checklists, focus groups).
  • Interpersonal and team skills (facilitation, conflict resolution).
  • Meetings (planning workshops, alignment sessions).

Outputs

  • Project management plan (integrated document with all baselines and subsidiary plans).

What the Project Management Plan Includes

Subsidiary plans:

  • Scope management plan.
  • Requirements management plan.
  • Schedule management plan.
  • Cost management plan.
  • Quality management plan.
  • Resource management plan.
  • Communications management plan.
  • Risk management plan.
  • Procurement management plan.
  • Stakeholder engagement plan.

Baselines:

  • Scope baseline (scope statement, WBS, WBS dictionary).
  • Schedule baseline (finalized network diagram and dates).
  • Cost baseline (time phased budget).

Additional components:

  • Change management plan.
  • Configuration management plan.
  • Performance measurement baseline.
  • Project life cycle description.
  • Development approach (predictive, agile, or hybrid).

Practical Example

Context: Airport Expansion Project.

Background: An international airport is expanding to add a new terminal.

Activities:

  • Scope baseline: Defines the terminal layout, systems, and services.
  • Schedule baseline: Key milestones include ground breaking, structural completion, systems installation, and final handover.
  • Cost baseline: Budget phased across construction, equipment, and commissioning.
  • Risk management plan: Identifies risks such as supply chain delays, regulatory approvals, and weather impacts.
  • Communications plan: Defines updates to government officials, airlines, and the public.
  • Development approach: Hybrid, with predictive methods for construction and agile methods for IT integration.

Outcome: With an integrated plan, leadership aligns on expectations, teams coordinate effectively, and risk is proactively managed.

Common Pitfalls

Treating the plan as a static document

  • Pitfall: Plan is created once and never updated.
  • Prevention: Update the plan through approved change control as the project evolves.

Siloed planning

  • Pitfall: Teams create independent plans that do not integrate.
  • Prevention: Use the project management plan to unify all subsidiary plans.

Overly detailed too early

  • Pitfall: Attempting to plan every detail at project start.
  • Prevention: Apply rolling wave planning. Detail near term work and keep later phases at a higher level.

Skipping stakeholder engagement

  • Pitfall: Plans developed without sufficient stakeholder input.
  • Prevention: Use workshops and reviews to build shared ownership.

Sensei Tip : Think of the project management plan as the master scroll that ties together all other scrolls. Without it, the project fragments into disconnected pieces.

Exam Alert : If a question mentions a change request or decision during execution, the best first step is usually to review the project management plan and then follow formal change control, not to approve or reject the change on the spot.

Exam Lens

Patterns on the PMP Exam:

  • The document that guides execution and control is the project management plan.
  • When a change is requested, review the plan and follow Perform Integrated Change Control.
  • If scope, schedule, or cost are unclear, the plan or baselines are incomplete and Planning is not finished.
  • On the exam, the project manager integrates. They do not manage in silos.

Sample Question

Question: During execution, a team member proposes a change to the product scope that could add value. What should the project manager do first?

  1. Approve the change since it adds value.
  2. Reject the change since scope is already defined.
  3. Review the project management plan to evaluate impacts and follow change control.
  4. Add the change to the backlog and inform stakeholders later.

Correct Answer: C. The plan provides the framework for evaluating and processing change requests.

Quick Recap Table

Element Why It Matters Exam Watch Point
Integrated master document Aligns all subsidiary plans and baselines. Always refer to the plan before acting.
Baselines Provide measurable references. Variance and forecasting questions rely on them.
Change and configuration plans Define control procedures. Many questions hinge on proper change control.
Progressive elaboration Plans evolve as information emerges. Watch for rolling wave scenarios.
Development approach Sets predictive, agile, or hybrid structure. Expect questions testing methodology fit.

Key Takeaways

  • The project management plan integrates all other plans and baselines into a single guiding document.
  • It defines how the project will be executed, monitored, controlled, and closed.
  • It evolves progressively and must be maintained through change control.
  • On the exam, always consult the plan before taking action.
  • In practice, a well developed plan provides alignment, credibility, and confidence.

Next Step

With the Project Management Plan established, the next step in Planning is to define scope management. We begin with Plan Scope Management, which sets the framework for how scope will be defined, validated, and controlled.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.

Scroll to Top