Integrate & Align Project Plans
The first Planning-focus-area process in the process-by-process pipeline through all 40 PMBOK processes — full ITTO (Inputs, Tools & Techniques, Outputs) detail for the process that consolidates every other Planning process's output into one master Project Management Plan, plus reference illustrations, the PMP Mindset behind it, and a 100-question practice quiz.
Each stepper item represents an entire focus area, not a single step — Planning alone has 19 processes across 7 domains, so it will take several steps (6, 7, 8…) to finish it. The stepper flips to "done" only once every process in that column has a finished page.
| Domain | Planning Process(es) | Status |
|---|---|---|
| Governance | Integrate & Align Project Plans | ✅ Step 6 (this page) |
| Governance | Plan Sourcing Strategy (incl. Procurement Steps, Contract Types) | ✅ Step 7 |
| Scope | Plan Scope Management, Elicit and Analyze Requirements, Define Scope, Develop Scope Structure | ⬜ upcoming |
| Schedule | Plan Schedule Management, Develop Schedule | ⬜ upcoming |
| Finance | Plan Financial Management, Estimate Costs, Develop Budget | ⬜ upcoming |
| Stakeholders | Plan Stakeholder Engagement, Plan Communications Management | ⬜ upcoming |
| Resources | Plan Resource Management, Estimate Resources | ⬜ upcoming |
| Risk | Plan Risk Management, Identify Risks, Perform Risk Analysis, Plan Risk Responses | ⬜ upcoming |
Governance Integrate & Align Project Plans — Definition
Reference illustration: the whole idea in one picture — Scope, Schedule, Cost, Quality, Risk (and the rest of the subsidiary plans) get pieced together into one Integrated Project Management Plan that defines how the project is executed, monitored, controlled, and closed.
- One process out of Planning's 19 — it is the one process that all 18 others roll up under, since every other Planning process across all 7 domains feeds its output into this one integrative process.
- Definition: the process of bringing together all subsidiary management plans, baselines, and supporting project documents into a single, integrated project management plan.
- Defines how the project will be executed, monitored, controlled, and closed.
- The approved project management plan becomes the baseline against which performance is measured throughout the project.
Performance Domain: Governance · Focus Area: Planning — per the PMBOK 8th Edition Process Chart (see the reference table below). This is process 1 of 19 in Planning.
Governance Integrate & Align Project Plans — Inputs
Reference illustration: the four input categories feeding Integrate & Align Project Plans — the approved Project Charter, output from other Planning processes, Enterprise Environmental Factors, and Organizational Process Assets.
- Provides high-level project description, key deliverables, and assumptions used as the starting point for the PM plan.
- Defines the authority of the PM and the success criteria.
- All subsidiary management plans.
- All baselines.
- Organizational culture, infrastructure, regulations, PMIS.
- Standard templates, lessons learned, configuration management knowledge base.
EEF is external to the organization's control (culture, infrastructure, regulations, the PMIS the organization already runs on); OPA is the organization's own reusable, controllable knowledge (templates, lessons learned, configuration-management history). When a question asks which bucket something falls into, ask whether the organization actually controls it.
Governance Integrate & Align Project Plans — Tools & Techniques
Reference illustration: expert judgement, the four data-gathering tools, the three interpersonal & team skills, meetings, and the Project Canvas — the full toolkit used to integrate the subsidiary plans.
- Expert judgement — input from people with specialized knowledge in the relevant management domains (scope, schedule, cost, risk, procurement, etc.).
Data gathering
- Elicit ideas and approaches for integrating plans.
- Confirm all required components of the PM plans are addressed.
- Gather feedback on the proposed approach.
- One-on-one with subject matter experts and stakeholders.
Interpersonal & team skills
- Resolve competing demands among management plans.
- Drive consensus across plan owners.
- Keep planning meetings focused and productive.
Meetings & the Project Canvas
- Meetings — a planning workshop to integrate the subsidiary plans.
- Project Canvas — a visual tool to outline and plan the key parts of the project.
Governance Integrate & Align Project Plans — Outputs
Reference illustration: the integrated Project Management Plan, its sponsor approval, the predictive-project change-control rule, and the quick management-plan-vs-baseline distinction.
- The integrated, approved master document that defines how the project is executed, monitored, controlled, and closed.
- Includes the development approach (predictive, iterative, hybrid) for each major deliverable.
- References all subsidiary management plans: scope, schedule, cost, quality, resources, communication, risk, procurement, stakeholder engagement.
- Approved by the sponsor before execution begins.
Once the plan is approved, any change to any component requires an approved change request. If a project management plan document is signed, changes can only be made through a formal change request.
- Defines how the project will be executed, monitored, controlled, and closed.
- Tells you the actual work / project-related details — start date, end date, actual scope, etc.
The PMP Mindset
Think of this process as the "master assembly" of project planning — the ITTO above covers the mechanics, but the exam rewards understanding why this process matters, not just what feeds into it.
"These can't just sit here separately, Barney — they've all gotta line up as ONE plan." The individual plans can't just sit side by side — they have to be checked, coordinated, and pulled into one aligned direction.
You may have separate plans for scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholders, but the project manager cannot manage these as independent documents. They must be brought together into one coherent Project Management Plan that explains how the project will actually be managed from execution through monitoring, control, and closure.
This is why Integrate & Align Project Plans is such an important Planning process. The other Planning processes develop the individual management plans and baselines; this process brings those pieces together and checks that they are consistent, coordinated, and aligned with the project's objectives.
Start with the right inputs
The right inputs lay the foundation for a strong, integrated plan.
The approved Project Charter provides the foundation. It establishes the project's high-level purpose, key deliverables, assumptions, success criteria, and the project manager's authority. The project manager then brings in the outputs from the other Planning processes — the subsidiary management plans, baselines, and relevant project documents.
The project manager must also consider the environment in which the project operates. Enterprise Environmental Factors (EEF) such as organizational culture, infrastructure, regulations, and the PMIS can influence how the project will be managed. Organizational Process Assets (OPA) — including templates, lessons learned, historical information, and configuration-management knowledge — provide organizational knowledge that can improve the plan.
Integration requires people, not just paperwork
Different perspectives. Better decisions. A stronger plan. Integration is a team sport.
The project manager does not simply copy and paste the individual plans together. Expert judgment is used to understand how the different management domains interact. For example, a change in scope can affect schedule, cost, resources, risk, procurement, and stakeholder expectations.
The team may use brainstorming, checklists, focus groups, and interviews to gather information and identify gaps. Conflict management, facilitation, and meeting management help resolve competing requirements and create agreement among the people responsible for different parts of the plan. A planning workshop can bring the plan owners together, while a Project Canvas can provide a visual way to see how the major pieces of the project fit together.
The key output: one integrated Project Management Plan
All the plans come together here — one integrated plan to guide the project from start to finish, signed off by the sponsor before execution begins.
The result is the Project Management Plan — the integrated, approved master document that describes how the project will be executed, monitored, controlled, and closed. It brings together and references the subsidiary management plans and incorporates the appropriate baselines. It also establishes the development approach — predictive, iterative, or hybrid — for the major deliverables where appropriate.
The individual plans must not contradict one another. Integration means understanding the relationships and managing the project as one system.
Before execution begins, the plan is formally approved by the appropriate authority, typically including the sponsor. Once approved, it becomes the authorized framework for managing the project.
For a predictive project, this approval is especially important. If an approved component of the Project Management Plan needs to change, the project manager should not simply edit the document. The proposed change goes through the formal change control process and, when approved, the relevant plan or baseline is updated accordingly.
Remember the "HOW" vs. "WHAT/WHEN" distinction
Different focus. Both are essential. If a question asks "How will the project be managed?", think Project Management Plan; if it asks "What was approved, and how does performance compare?", think baseline.
A useful PMP exam shortcut:
- How will we execute, monitor, control, and close the project?
- The approved reference points for what is being delivered and measured — scope, schedule, and cost commitments — and the reference against which performance is compared.
The PMP mindset
When PMP questions present multiple competing plans, stakeholders, or constraints, think integration before action. Do not optimize one part of the project while ignoring the impact on the others. The project manager's job is to see the whole system, reconcile the individual pieces, obtain the necessary approval, and then manage the project against the approved plan and baselines.
Every subsidiary plan, baseline, and document — brought together into one.
Reference The 40-Process Chart — PMBOK 8th Edition
Source: printed handout, "PMBOK 8th Edition Process Chart — Andrew Ramdayal, PMP Exam Prep Course," Technical Institute of America. This chart is being built one focus area at a time as each step's notes are transcribed — it now shows the completed Initiating column plus the first two cells of Planning; the rest of Planning, Executing, Monitoring & Controlling, and Closing will be filled in as those steps are covered.
| Performance Domain | Initiating | Planning |
|---|---|---|
| Governance | Initiate Project or Phase | Integrate & Align Project Plans; Plan Sourcing Strategy |
| Scope | — | — |
| Schedule | — | — |
| Finance | — | — |
| Stakeholders | Identify Stakeholders | — |
| Resources | — | — |
| Risk | — | — |
Recall Recall Quiz
Straight recall — Integrate & Align Project Plans, full ITTO, straight from the sections above.
Scenario Case Study Quiz
Short, standalone situational questions — apply the concepts above to one scenario at a time.
New Format Long Case Studies
Matches the newer PMI exam format: one longer scenario, several linked questions. 5 case studies, 6 questions each — one per topic cluster (Definition, Inputs, Tools: data gathering, Tools: interpersonal skills, Output), starring Mumtaz, Rekha, Waheeda, Zeenat, and Asha.
Advanced Step 1–6 Mix
Conceptual questions that combine everything covered so far — mindset fundamentals, principles & leadership, development approaches & lifecycles, process groups & performance domains, the Initiating focus area, and Integrate & Align Project Plans itself — phrased as scenarios and direct questions rather than by curriculum step number.