II.1. How to develop an integrated project management plan and plan delivery

Executive Summary

The primary driver of project failure is not the absence of planning, but the commencement of formal commitments based on a partial or unstable understanding of the project landscape. Documentation often simulates maturity, where approved templates and active meetings mask a failure to test underlying assumptions against the environment. To ensure strategic delivery, project managers must distinguish between information that merely narrows uncertainty and critical information that decides plan viability. Successful delivery requires a shift from purely measuring process success (adherence to baselines) to ensuring outcome success (realization of strategic value). This briefing document outlines the methodologies for landscape diagnosis, development approach selection, and the integration of subsidiary plans into a coherent governing system.

I. Diagnosing the Project Landscape and Context

The project manager must begin by evaluating whether the project is understood well enough to justify current planning decisions. Disciplined documentation can be misleading if the assumptions beneath the work have not been tested against the environment that governs delivery.

1.1 Environmental and Organizational Factors

Judgment of the project landscape depends on two primary sources that must be analyzed in tandem:

Enterprise Environmental Factors (EEFs): These represent conditions the project must absorb but cannot control. Internal EEFs include culture, infrastructure, and resource capability. External EEFs include regulation, market conditions, and industry standards.
Organizational Process Assets (OPAs): These represent formalized organizational learning, such as governance frameworks, templates, risk databases, and lessons learned repositories. They indicate how the organization has previously distributed authority and stabilized delivery.

1.2 Critical Information Requirements

Information is deemed critical when proceeding without it forces the project to commit scope, schedule, or cost against an assumption that could later invalidate the plan.

The Identification Failure: The project fails to recognize missing information before commitment, leading to variance and rework that appears later as a schedule or cost problem.
The Conversion Failure: The project recognizes critical information is missing but proceeds anyway, treating a planning risk as a known-uncertain assumption. This inevitably results in change requests against an unstable baseline.

1.3 Systemic Complexity vs. Uncertainty

Effective governance requires a clear distinction between uncertainty and complexity:

Uncertainty: Involves incomplete knowledge regarding requirements or technology.
Complexity: Involves the pattern of relationships and dependencies within the project and its environment.

A Dependency Structure Matrix (DSM) should be used to make coupling visible. If the DSM reveals dense coupling across components or teams, local errors are likely to propagate, requiring a heavier integration logic regardless of whether requirements are clear.

II. Strategic Alignment and Defining Success

A project can meet all process baselines and still fail if the result no longer solves the strategic problem that justified the investment.

2.1 Process Success vs. Outcome Success

Process Success: Asks whether the project remained controlled against scope, schedule, cost, and quality baselines.
Outcome Success: Asks whether strategic, financial, or operational objectives were realized.

The project manager must use the Benefits Management Plan to define metrics and accountability for realization, ensuring that resource consumption continues to move the organization toward the desired future state.

2.2 Authorized Boundary Alignment

The integrated project management plan must operationalize the Project Charter. Misalignment occurs when internal plans are coherent with one another but inconsistent with the strategic intent, funding parameters, or decision authority established in the charter. Integration is best understood as disciplined alignment to these authorized boundaries rather than mere document accumulation.

III. Selecting and Tailoring the Development Approach

Approach selection is a resource allocation decision regarding where to commit definition early and where to preserve room for learning.

3.1 The Development Spectrum

The project manager selects an approach based on the project’s uncertainty and complexity profile:

Predictive: Concentrates effort on early definition and baseline stability. This is appropriate when requirements are stable and the project gains more from early commitment than from deferring it.
Adaptive (Agile/Iterative/Incremental): Preserves room for learning and frequent feedback. This is used when requirements or technology are expected to evolve.
Hybrid: Combines predictive and adaptive structures. This is effective for projects with diverse workstreams that require different governance logics, provided the boundaries between stable and evolving work are clear.

3.2 Diagnostic Tools for Selection

The Stacey matrix helps evaluate requirement uncertainty and technical uncertainty together.

Low Uncertainty: Favors predictive sequencing for efficiency.
High Uncertainty: Favors adaptive cycles to reduce the cost of hardening commitments too soon.
Mixed Signals: The project manager must determine which uncertainty is more likely to create expensive downstream rework and recommend an approach that protects against that specific risk.

IV. Project Execution Strategy and Tailoring

Execution strategy is distinct from the development approach. While the development approach dictates governance and commitment, the execution strategy dictates how work is organized, sourced, and released.

4.1 Key Execution Decisions

The project manager must recommend a strategy based on the dominant risk the project faces:

Sequencing: Staged sequencing is preferred when dependencies are dense or adoption risk is high. Parallel streams are used when workstreams are weakly coupled and speed is a priority.
Sourcing (Make-or-Buy/Build-vs-Integrate): Internal builds preserve control but may strain capacity. Integrating existing components can accelerate delivery but introduces interface risks.
Release and Handoff: Value is only created when a solution can be absorbed and operated. Phased releases can reduce operational risk but increase coordination costs.
Decision Rights: Authority must be placed where trade-offs can be made quickly enough to protect the work without bypassing required governance.

V. Developing the Integrated Plan

The integrated project management plan prevents planning fragmentation by ensuring that subsidiary plans (scope, schedule, cost, etc.) do not carry hidden contradictions.

5.1 Integration Tests

The project manager performs several tests to ensure the governing system is reconcilable:

Test Type	Objective
Boundary Consistency	Ensures all plans reflect the same authorized scope and funding limits from the charter.
Assumption Compatibility	Checks if the schedule, resource, and cost assumptions can all hold true simultaneously.
Control Operability	Ensures governance thresholds are translated into actionable decision paths.
Benefit Traceability	Confirms measures of progress are connected to the actual benefits logic in the business case.
Dependency Logic	Exposes instances where one plan relies on a condition that another plan has not yet secured.

5.2 Foundational Estimation

Estimation is a governance problem. The choice of technique must match the maturity of the work definition:

Analogous Estimating: Used when info is limited but historical comparators are genuinely similar.
Parametric Estimating: Used when there is a defensible statistical relationship between historical data and work.
Bottom-up Estimating: Used when the Work Breakdown Structure (WBS) is sufficiently decomposed for high precision.
Multipoint Estimating: Used when activity uncertainty can be analyzed through optimistic, pessimistic, and most likely ranges.

VI. Maintenance, Control, and Data Discipline

A plan remains useful only as long as it is treated as the governing reference for decisions. This requires ongoing reassessment and disciplined change control.

6.1 Change Control and Plan Integrity

The “assess and implement changes” process prevents adaptation from occurring without system-level judgment. The project manager must evaluate how a change affects the entire system (scope, risk, resources, and benefits) rather than treating it in isolation. If decisions are being made outside the plan, it indicates the governance route is unusable and requires a formal reset.

6.2 Data-Driven Decisions

Metrics must be selected based on their ability to improve decisions. The following five criteria are used to evaluate the measurement system:

Reliability: Does the measure produce consistent information?
Validity: Does it measure the actual condition intended?
Timeliness: Does info arrive early enough to influence action?
Sensitivity: Does the measure change when the underlying condition changes?
Effort-to-Value Ratio: Is the reporting burden justified by the decision benefit?

Leading indicators should be used to reveal emerging conditions, while lagging indicators confirm realized performance.

6.3 Integrating Sustainability

Sustainability is a planning issue, not an administrative add-on. Environmental and social consequences must be considered during early scope, sourcing, and risk response decisions. Ignoring these factors can lead to a project that is financially persuasive in the short term but lacks long-term viability or stakeholder acceptance. Integration involves testing sustainability where choices are still adjustable to protect the outcome’s credibility after delivery.