Task 23: Integrate Planning Activities
Integration is the discipline that transforms a collection of separate plans into a single coherent project. ECO Task 23 — the final task in the Process domain — demands that project managers consolidate project and phase plans, assess them for dependencies and gaps, critically evaluate continued business value, collect and analyze planning data, and determine what information is truly critical for decision-making. This is where the PM earns the title of integrator: the person who sees the whole picture when everyone else sees pieces.
PMI places integration at the heart of project management because no plan stands alone. The scope plan interacts with the schedule plan, which interacts with the cost plan, which interacts with the quality plan, which interacts with the risk plan — and all of them interact with stakeholder expectations and organizational strategy. Task 23 is the meta-task that ensures these interactions are intentional, not accidental, and that the resulting project plan is greater than the sum of its parts.
ECO Enablers for Task 23
The PMP Exam Content Outline structures integration planning around five enablers that represent the integrative work across all project management knowledge areas:
- Consolidate project/phase plans. Individual plans — scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder engagement — must be woven into a single integrated project management plan. This is not simple aggregation; it requires resolving conflicts, aligning assumptions, and ensuring internal consistency across all subsidiary plans.
- Assess consolidated project plans for dependencies, gaps, and continued business value. Once consolidated, the integrated plan must be stress-tested. Are there dependency chains that create hidden bottlenecks? Are there gaps where no plan addresses a critical activity? Most importantly, does the project still justify its existence — is the business case still valid?
- Collect and analyze data to make informed project decisions. Planning is data-driven, not intuition-driven. The PM must gather work performance data, analyze it for trends and variances, and use the resulting work performance information to make decisions and generate work performance reports for stakeholders.
- Determine critical information requirements. Not all data is equally important. The PM must identify what information is critical for decision-making — the vital few metrics that truly indicate project health versus the trivial many that create noise.
Consolidating Project and Phase Plans
The integrated project management plan is the master document that defines how the project will be executed, monitored, controlled, and closed. It consolidates all subsidiary management plans and baselines into a single authoritative source. But consolidation is not cut-and-paste — it demands that the PM resolve conflicts between subsidiary plans before they become execution problems.
Common consolidation conflicts include schedule assumptions that don't match cost estimates (the schedule says three months but the budget only covers two), resource plans that conflict with procurement lead times (the resource plan assumes equipment arrives in week 2, but procurement says the lead time is 8 weeks), and quality requirements that are incompatible with the approved budget (the quality standard demands extensive testing, but the budget doesn't fund it).
The PM's role during consolidation is to identify these discrepancies and facilitate resolution — escalating to the sponsor when trade-off decisions exceed the PM's authority. The integrated plan that emerges should be internally consistent: every assumption in one subsidiary plan should be reflected in all others.
Phase Plans and the Rolling Wave Approach
For large or long-duration projects, planning often occurs in phases using a rolling wave approach. Detailed planning is performed for the near-term work (the current phase) while longer-term work is planned at a higher level, with detail added as the project approaches each subsequent phase. The PM must integrate these phase plans into the overall project management plan and ensure that phase transitions are explicitly planned — including phase-gate criteria, handoff activities, and go/no-go decision points.
The PMP exam draws a sharp distinction between the project management plan (which includes subsidiary plans, baselines, and the change management plan) and project documents (such as the risk register, issue log, stakeholder register, lessons learned register, and requirements documentation). Changes to the project management plan require formal integrated change control. Changes to project documents typically do not. Knowing which artifact is which — and the change control implications — is a high-frequency exam topic.
Assessing Plans for Dependencies, Gaps, and Continued Business Value
Once plans are consolidated, the PM must assess the integrated whole. This assessment has three dimensions: dependencies, gaps, and business value.
Dependency Assessment
Dependencies are not limited to schedule logic. The integrated plan must be checked for cross-domain dependencies — places where a decision or constraint in one knowledge area creates a dependency in another. For example, a risk response plan may depend on procurement contracts (contingency suppliers), a quality management approach may depend on resources with specialized certifications, and a communications plan may depend on stakeholder availability that is governed by the resource management plan. These hidden dependencies are a primary source of plan failures, and the PM is responsible for surfacing them during integration.
Gap Analysis
Gap analysis examines the integrated plan for omissions — activities, deliverables, resources, or governance structures that are required but not addressed by any subsidiary plan. Common gaps include missing transition planning (how the project output moves into operations), missing decommissioning activities for legacy systems, overlooked regulatory approvals that must precede certain work, and missing handoff activities between project phases or teams.
PMI expects the PM to conduct gap analysis proactively — not to discover gaps during execution when they become crises. The question "what are we not planning for?" is as important as "what are we planning for?"
Continued Business Value Assessment
The business case that justified the project at initiation may not remain valid. Market conditions change, organizational strategy shifts, competitors move, and the cost-benefit equation evolves. The PM has a professional responsibility to periodically reassess whether the project still delivers sufficient business value to justify its continued investment.
| Assessment Trigger | What to Evaluate | PM's Responsibility | Potential Outcome |
|---|---|---|---|
| Phase gate reviews | Has the business case changed during the preceding phase? Are the original assumptions still valid? | Present updated cost-benefit analysis at each phase gate. Flag material changes to the sponsor and governance body. | Continue to next phase, adjust scope/budget/schedule, or terminate the project. |
| Significant external change | Regulatory change, market disruption, competitor action, technology shift, economic downturn. | Assess impact on the business case. Escalate to sponsor with options: continue, pivot, or stop. | Re-baseline the project with updated assumptions or recommend termination if value is lost. |
| Major scope change request | Does the proposed change alter the value proposition? Does it invalidate any original business case assumptions? | Update the benefits management plan to reflect the change. Ensure the business case remains viable after the change. | Approve change with updated benefits documentation or reject change because it undermines business value. |
| Cost or schedule overrun | Has the project become so expensive or late that the original ROI is no longer achievable? | Recalculate the business case with actuals and revised forecasts. Present the updated numbers honestly — do not obscure bad news. | Sponsor may accept reduced ROI, inject additional funding, reduce scope, or terminate. |
Collecting and Analyzing Data for Informed Decisions
Data is the fuel of project decision-making. PMI structures the data-to-decisions pipeline as a hierarchy: raw observations and measurements become work performance data, which is analyzed in context to produce work performance information, which is compiled and communicated to stakeholders as work performance reports. Each layer adds analysis, context, and actionable insight.
The PM must determine what data to collect (defining data collection methods and frequency), how to analyze it (selecting appropriate analytical techniques for the type of data and the decisions it supports), and how to present it (tailoring reports to the audience — executives need summary dashboards; team members need detailed task-level data).
Key analytical techniques include variance analysis (comparing planned vs. actual), trend analysis (examining performance over time to forecast future outcomes), earned value analysis (integrating scope, schedule, and cost data), root cause analysis (determining why variances occurred), and alternative analysis (evaluating options for corrective or preventive action). The PMP exam tests these analytical techniques in scenario-based questions that require you to select the appropriate technique for the situation described.
Determining Critical Information Requirements
Not all information is equally important. PMI's concept of critical information requirements recognizes that project managers and stakeholders are inundated with data, and the key skill is filtering signal from noise. Critical information is data that, if missing or wrong, would cause a decision-maker to make a materially different choice.
Determining critical information requirements involves identifying who needs what information, at what level of detail, at what frequency, and for what decision. The communications management plan documents these requirements, but determining them requires the PM to understand the project's strategic objectives and the decisions each stakeholder group must make.
PMI draws a precise three-level hierarchy that appears repeatedly on the exam: Work Performance Data (raw observations — "we completed 12 of 40 planned activities this week"), Work Performance Information (data in context — "we are 30% complete against a planned 45%, which is a schedule variance of −15%"), and Work Performance Reports (formatted for stakeholders — the status report with charts, analysis, forecasts, and recommendations). The key exam distinction: Monitoring and Controlling processes take data as input and produce information as output. The Monitor and Control Project Work process takes information and produces reports. Confusing these levels is a common exam trap.
Integrating Across the Project Lifecycle
Integration planning is not a one-time activity — it recurs at key points throughout the project lifecycle. At project initiation, integration means aligning the project charter with organizational strategy. During planning, it means consolidating subsidiary plans into the integrated project management plan. During execution, it means incorporating approved changes into all affected plans. During monitoring and controlling, it means analyzing integrated performance data. And at closure, it means ensuring all plans are satisfied and all loose ends are tied.
The project manager is the integrator — the one person responsible for ensuring that all the pieces work together. This is the role PMI defines as uniquely belonging to the project manager: not the deepest expert in any single domain, but the person who ensures all domains are aligned toward a common goal.
Study Checklist for Task 23
- ✅ Can you explain the difference between consolidating plans (weaving subsidiary plans into one integrated whole) and simply aggregating them?
- ✅ Do you understand the three dimensions of plan assessment: dependency analysis (cross-domain dependencies), gap analysis (what's missing), and continued business value (is the project still justified)?
- ✅ Can you distinguish the project management plan (subsidiary plans + baselines, under change control) from project documents (registers, logs, reports, not under the same change control rigor)?
- ✅ Do you know the data-information-reports hierarchy — work performance data (raw) → work performance information (analyzed/contextualized) → work performance reports (formatted for stakeholders)?
- ✅ Are you able to identify critical information requirements — the vital few data points that decision-makers actually need — and explain how they differ from the broader universe of available data?
- ✅ Can you describe the PM's responsibility to assess continued business value at phase gates and after significant external changes, including the professional obligation to recommend termination when value is lost?
- ✅ Do you understand rolling wave planning and how phase plans integrate into the overall project management plan?
- ✅ Can you apply data analysis techniques — variance analysis, trend analysis, earned value analysis, root cause analysis, and alternative analysis — to the appropriate scenario-based questions?
Task 23 closes the Process domain with the discipline that makes project management a distinct profession: integration. The project manager is not the owner of any single knowledge area — the PM is the owner of the connections between them. Master integration, and you master the PMP mindset. Return to the ECO Study Guide Index to review other tasks or practice Process Domain questions.
← Back to ECO Study Guide Index | Practice Process Domain Questions →