17.2 Why an Integrated Plan Matters
Key Takeaways
- Siloed plans built on different assumptions produce a project that looks controlled while its own documents disagree with each other.
- Integration makes conflicts visible early — a schedule that assumes resources the resource plan does not provide fails at the planning stage rather than in delivery.
- An integrated plan is the reference that change control acts on: without it, the impact of a change cannot be assessed across all dimensions.
- Building the plan collaboratively secures the commitment of the people who must deliver it and improves estimate quality.
- Maintaining the plan through change control keeps it authoritative; an out-of-date plan is quietly replaced by informal understandings.
Outcome 19b is short — understand the importance of producing an integrated project management plan — and it is answered well only by explaining what goes wrong without one. The value of integration is invisible until you look at a project whose plans disagree with each other.
Siloed plans vs integrated planning
Siloed planning produces separate high-quality documents that do not agree. Integrated planning forces reconciliation of assumptions, dates, and owners.
| Siloed symptom | What goes wrong | Integrated response |
|---|---|---|
| Schedule built without resource limits | Dates look green; work cannot be staffed | Resource-loaded or resource-checked schedule |
| Budget built from top-down target only | Cost baseline ignores bottom-up estimates and risk | Reconcile estimate, contingency, and funding |
| Quality gates not on the network | Testing and acceptance crush the end date | Quality activities as scheduled work with dependencies |
| Risk register not linked to plan | Responses unfunded and untimed | Risk responses with owners, cost, and schedule impact |
| Comms plan ignores milestones | Stakeholders surprised at cutover | Communications tied to decision points and transitions |
| Procurement lead times ignored | Critical materials arrive after need dates | Procurement milestones on the critical path |
| BAU blackouts ignored | Cutover planned for operational peak | Dependencies with BAU calendars in the schedule |
Scenario A — siloed "green" status
A digital transformation reports schedule green, cost amber, and risk red in three different tools with different cut-off dates. The sponsor asks whether the project is healthy. Because plans are siloed, nobody can answer whether the risk responses that would restore the schedule are funded. The project manager should re-baseline an integrated view: one data date, one set of assumptions, and a single impact story for board decision — not three dashboards that cannot be added together.
Scenario B — quality plan after design freeze
A construction fit-out freezes design and commits a fixed-price installer while the quality plan still lists long factory acceptance tests that were never put on the programme. When tests are inserted late, either quality is sacrificed or the schedule breaks. Integrated planning would have put acceptance activities, hold points, and supplier lead times into the schedule and budget before freeze and award.
Importance of producing an integrated PMP (LO19b)
The syllabus stresses why integration matters, not only what sits in the document:
- Decision quality — options (crash, descope, buy vs make) can be compared across time, cost, risk, and benefits.
- Realistic commitments — promises to stakeholders reflect resource and procurement reality.
- Control — variance analysis needs a coherent baseline; siloed baselines produce fake variance.
- Accountability — named approaches and owners reduce "I thought someone else owned that."
- Assurance readiness — independent assurance can test plan completeness and use.
- Change discipline — integrated impact assessment is impossible without an integrated starting point.
- Life-cycle continuity — new team members and suppliers can onboard to one plan of record.
- Benefits protection — delivery choices remain traceable to outcomes and transition needs.
Exam trap: Saying the PMP is "important for communication" only. Communication is one benefit; the deeper point is coordinated control of interdependent constraints under governance.
Building and maintaining the integrated plan
Development
Typical development path (wording varies):
- Confirm mandate, objectives, constraints, and success criteria from the business case / project brief.
- Define scope and breakdown structures (see next section).
- Sequence activities, estimate duration and cost, identify resources and procurement.
- Assess risk and quality requirements; insert responses and quality activities.
- Reconcile conflicts (resource overallocation, funding gaps, impossible dates).
- Agree communication, governance, and change approaches.
- Seek baseline approval from the appropriate authority.
- Communicate the authorised plan and store the controlled version.
Maintenance
The PMP is living but controlled. Forecasts may update frequently; baselines change only through authorised change or formal re-planning. Progress reporting compares actuals and forecasts to the integrated baseline. Major reviews and gates re-test whether the plan still supports a viable business case.
| Maintenance activity | Purpose |
|---|---|
| Progress updates | Refresh forecasts and % complete against baseline |
| Risk and issue reviews | Keep threats/opportunities linked to plan impacts |
| Change control | Assess multi-dimensional impact before baseline edits |
| Re-estimating | Replace outdated estimates when learning improves accuracy |
| Configuration of plan documents | Ensure the team uses the current authorised version |
Scenario C — iterative delivery still needs integration
An agile software programme plans sprints in detail only for the near term. Stakeholders wrongly conclude "we do not need a project management plan." Still required at integrated level: product vision and scope boundaries, release roadmap, budget envelope, risk approach, Definition of Done / quality standards, dependency management with BAU and other teams, and governance for scope trade-offs. Detail is wave-planned; integration of constraints and approaches is not optional.
Answer pattern for integrated planning questions
When a scenario shows conflict between time, cost, quality, or supply:
- State the purpose of an integrated PMP (coordinated baseline for execution and control).
- Name relevant contents (scope, schedule, cost, risk, quality, resources, comms, change, governance).
- Explain why siloed plans fail in the scenario facts.
- Recommend reconciliation and re-baselining under the right authority.
- Link to assurance, reviews, and change control where relevant.
That structure matches LO19 and prepares the ground for schedule management (LO20): schedule is one integrated component, not a standalone Gantt chart disconnected from scope and cost.
A project has a detailed schedule, a separate cost spreadsheet, and a risk register, but the three use different assumptions and cut-off dates. What is the main problem?
Why is producing an integrated PMP important for change control?