5.1 Develop Project Management Plan

5.1 Develop Project Management Plan
Inputs Tools & Techniques Outputs

The process of building a single, approved plan that integrates all subsidiary plans and baselines to guide how the project will be carried out, monitored, controlled, and closed. It aligns the team and stakeholders on approach, governance, and how changes will be handled.

Purpose & When to Use

  • Create one integrated plan that pulls together scope, schedule, cost, quality, resources, communications, risks, procurement, and stakeholder strategies into a coherent whole.
  • Align the plan with the project charter, benefits expectations, and organizational policies.
  • Decide the life cycle and development approach (predictive, agile, or hybrid) and tailor methods and controls accordingly.
  • Define how performance will be measured, how decisions are made, and how changes are evaluated and approved.
  • Used on every project, primarily during planning, and updated as needed when approved changes occur.

Mini Flow (How It's Done)

  • Review the charter, business case, and benefits plan to confirm objectives and success criteria.
  • Select the life cycle and development approach and document tailoring decisions.
  • Compile or refine subsidiary plans: scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder engagement.
  • Establish baselines for scope, schedule, and cost once planning data are stable.
  • Define governance: roles, decision rights, stage gates, and management reviews.
  • Set up the change control and configuration control processes, including forms, thresholds, and a review board if needed.
  • Decide performance measures and reporting methods, such as burn charts or earned value metrics.
  • Integrate all content into a single plan, ensure consistency across sections, and resolve conflicts.
  • Circulate the draft for feedback, incorporate comments, and obtain required approvals to baseline the plan.
  • Publish the approved plan in the PMIS, communicate key elements to stakeholders, and use it to guide execution and control.

Quality & Acceptance Checklist

  • Includes approved scope, schedule, and cost baselines and they are consistent with each other.
  • All needed subsidiary plans are present, aligned, and do not conflict.
  • Life cycle, development approach, and tailoring decisions are stated with rationale.
  • Governance, roles, responsibilities, and escalation paths are clear.
  • Change control and configuration control processes are defined with thresholds and authority levels.
  • Performance metrics, reports, and cadence are specified and practical.
  • Assumptions, constraints, and dependencies are captured and traceable.
  • Compliance with organizational standards, policies, and templates is confirmed.
  • Approval, version control, and baseline status are recorded and communicated.
  • The plan is realistic, achievable with available resources, and supports the benefits expected.

Common Mistakes & Exam Traps

  • Confusing the plan with the charter; the charter authorizes the project, while the plan guides how work will be done and controlled.
  • Starting execution before the integrated plan is approved and baselined.
  • Assuming the project manager writes the plan alone instead of facilitating inputs from the team and stakeholders.
  • Forgetting to define change control and configuration control, leading to uncontrolled changes.
  • Treating the plan as static; on exams, updates require approved change requests before altering baselines.
  • Equating the plan with just a schedule or Gantt chart; it is a comprehensive management document.
  • Not aligning the plan with the chosen delivery approach, causing mismatched ceremonies or controls.
  • Omitting stakeholder communication and engagement strategies, which undermines buy-in and decision speed.

PMP Example Question

After the team completes the scope, schedule, cost, risk, and other subsidiary plans, what should the project manager do next?

  1. Begin executing the work because enough planning has been done.
  2. Integrate the subsidiary plans into a single plan, resolve inconsistencies, and obtain approval to baseline it.
  3. Baseline only the schedule and start work while the rest is finalized.
  4. Update the business case to reflect team estimates.

Correct Answer: B — Integrate the subsidiary plans into a single plan, resolve inconsistencies, and obtain approval to baseline it.

Explanation: The next step is to produce an approved, integrated project management plan before execution begins. Baselines and governance must be in place to control the work.

AI for Project Managers — Build Plans Faster, Lead Better

Turn messy inputs into structured project plans in minutes. If you are a project manager tired of spending hours on documentation, this course shows you how to use AI to work faster while staying fully in control.

This is not a generic AI course. You will learn how to use AI as a practical co-pilot to build real project artifacts—charters, WBS, schedules, risk registers, and executive reports—using structured, reliable prompt frameworks.

You will also learn how to keep your project aligned across scope, schedule, cost, and risk, and how to interpret performance data like Earned Value Management to support better decisions and communication.

Everything is designed for immediate use. You get ready-to-use prompt templates and workflows you can apply right away in your projects. Watch the video to see how it works and start building your first AI-supported project plan.

Explore the Course


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now