KEVOS® Project Delivery Handbook
Project Integration Management
Every failed project tells the same story: brilliant specialists working in silos, each delivering their piece — while the whole thing quietly falls apart.
In this handbook article
- Why Integration Matters More Than Any Single Knowledge Area
- What Exactly Is Project Integration Management?
- The Integration Function — Key Actions
- How Integration Works: The Five-Phase Project Management Process
- Phase Breakdown
- The Integrator's Toolkit: Where Best Practices Meet Process
- Value Improving Practices Across the Lifecycle
- Total Cost Management Tools
- Management's Role in Integration
- The Pitfalls: Where Integration Breaks Down
- Key Takeaways
Every failed project tells the same story: brilliant specialists working in silos, each delivering their piece — while the whole thing quietly falls apart. Integration is the discipline that prevents this. It is the central nervous system of every project, and the project manager is its brain.
Why Integration Matters More Than Any Single Knowledge Area
Here is an uncomfortable truth that most textbook introductions gloss over: you can have a perfect scope, a flawless schedule, and a precise budget — and still deliver a catastrophic project.
How? Because those elements were never wired together.
The Project Management Institute (PMI) identifies ten knowledge areas. Nine of them — scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder management — are components. Integration is the tenth knowledge area, and it is fundamentally different. It does not produce a deliverable of its own. Instead, it is the connective tissue that makes every other knowledge area function as a unified system.
Dr. Nick Lavingia, in his landmark paper on improving profitability through effective project management, makes this point with financial precision: projects are the vehicle through which business opportunities become valued business assets. Successful projects — those delivered on time, within budget, and meeting business objectives — directly improve Return on Capital Employed (ROCE). But this only happens when every element of the project is orchestrated, not merely managed in isolation.
Core Principle: Integration is the function through which the project manager coordinates the efforts of the team to accomplish the project goals. It is not a phase — it is a continuous discipline that runs from inception to closure.
What Exactly Is Project Integration Management?
Integration management is the umbrella process that unifies, consolidates, and coordinates all project management activities and processes across the project lifecycle. While a cost engineer focuses on budgets and a scheduler focuses on timelines, the project manager focuses on ensuring that decisions in one domain do not silently destroy outcomes in another.
The Integration Function — Key Actions
The project manager's integration responsibilities include:
- Planning for integration across all knowledge areas
- Developing an integrated WBS, schedule, and budget (the "triple baseline")
- Continually reviewing and updating the project plan as conditions change
- Assuring control and adherence to the project plan
- Resolving conflict situations between functional teams
- Removing roadblocks that impede cross-functional work
- Setting priorities when resources are contested
- Making administrative and technical decisions across interfaces
- Resolving customer or client problems that span multiple domains
- Assuring project transfer (handover to operations)
- Maintaining communication links across organisational interfaces
Key Distinction: Any manager must focus on group goals. But the project manager must be more concerned with integration than a functional manager, precisely because the project team is composed of personnel drawn from many different functional areas — each with their own priorities, methods, and reporting lines.
How Integration Works: The Five-Phase Project Management Process
Integration does not exist in the abstract. It operates through a structured project management process (PMP). Lavingia describes a five-phase gated model that provides the mechanism for effective communication between decision-makers, multifunctional project team members, and stakeholders.
Relationship details
| From | Relationship | To |
|---|---|---|
| Phase 1 — Identify & Assess — Opportunities | Gate 1 | Phase 2 — Select from — Alternatives |
| Phase 2 — Select from — Alternatives | Gate 2 | Phase 3 — Develop Preferred — Alternative |
| Phase 3 — Develop Preferred — Alternative | AFE — (Full Funding | Phase 4 — Execute — (Detail Design, — Procurement, — Construction) |
| Phase 4 — Execute — (Detail Design, — Procurement, — Construction) | Gate 4 | Phase 5 — Operate & — Evaluate |
Phase Breakdown
| Phase | Purpose | Key Deliverables | Integration Focus |
|---|---|---|---|
| Phase 1 — Identify & Assess | Clearly frame the business goal; test for strategic fit | Preliminary plan & assessment; Class 1 estimate (~1% engineering) | Aligning business strategy with project feasibility |
| Phase 2 — Select from Alternatives | Generate and evaluate options; identify the preferred path | Alternative development; Class 2 estimate; preferred alternative identified | Coordinating technical, economic, and strategic evaluations |
| Phase 3 — Develop Preferred Alternative | Fully define scope; refine estimate to funding quality | Refined estimate (Class 3, ±10% accuracy); funding submission (AFE) | Freezing scope; integrating cost, schedule, and quality baselines |
| Phase 4 — Execute | Detail design, procurement, and construction | Implemented execution plan; minimum scope changes; finalised operating plan | Real-time control across all knowledge areas; change management |
| Phase 5 — Operate & Evaluate | Monitor asset performance; capture lessons | Business evaluation (1–2 years post-completion); post-project assessment | Closing the feedback loop; transferring lessons to future projects |
Critical Insight: The first three phases — collectively called Front End Loading (FEL) — are the most important determinant of project success. Decisions made during FEL lock in approximately 80% of a project's total lifecycle cost. Integration during these early phases is where the greatest value is created.
The Integrator's Toolkit: Where Best Practices Meet Process
Integration is not just a mindset — it requires specific tools and practices applied at the right time. Lavingia maps these onto the PMP roadmap as Value Improving Practices (VIPs) and Total Cost Management (TCM) tools.
Value Improving Practices Across the Lifecycle
| Workstream | Activity | Type | Timing / dependency / duration |
|---|---|---|---|
| Strategic Practices | Decision & Risk Analysis | Activity | active · 0 · 4 |
| Strategic Practices | Project Execution Planning | Activity | active · 0 · 4 |
| Strategic Practices | Lessons Learned (Seek | Activity | active · 0 · 4 |
| Technical Practices | Value Improving Practices (IPA | Activity | active · 1 · 3 |
| Technical Practices | Peer Review | Activity | active · 1 · 3 |
| Technical Practices | Pre-Funding Assessment | Activity | active · 2 · 3 |
| Post-Execution | Post Project Assessment | Activity | active · 4 · 5 |
| Post-Execution | Lessons Learned (Share | Activity | active · 4 · 5 |
| Post-Execution | Business Evaluation | Activity | active · 4 · 5 |
Total Cost Management Tools
| TCM Tool | When Applied | Purpose |
|---|---|---|
| Economic Analysis | Phases 1–3 | Compare NPV, ROR, and payout across project portfolio |
| Cost Estimating | All phases (progressive refinement) | Produce P10/P50/P90 estimates with explicit contingency |
| Planning/Scheduling | Phases 2–4 | Develop CPM resource-loaded schedules |
| Benchmarking | Phases 2–4 | Compare against industry database for cost and capacity targets |
| Contracting/Procurement | Phases 2–4 | Strategic sourcing through pre-qualification, bidding, and award |
| Performance Measurement | Phase 4 | Earned value tracking of physical progress vs. plan |
| Cost Control/Forecasting | Phase 4 | WBS-based budget tracking with trending and forecasting |
| Progress Reporting | Phases 4–5 | Plan vs. actual on scope, cost, schedule, and safety |
| Finance/Audit | Phase 5 | Capital vs. expense classification; asset accounting |
Management's Role in Integration
Integration is not solely the project manager's burden. Lavingia identifies five critical roles that senior management must play:
| Role | What It Means in Practice |
|---|---|
| Accountability | A business evaluation should be conducted 1–2 years post-completion; the project sponsor is held accountable for financial outcomes |
| Accessibility | Management actively participates in gate-keeping meetings at the end of each phase and communicates frequently with the project team |
| Leadership | Clear expectations and objectives are established for the project team from the outset |
| Resources | The right people are provided at the right time, with adequate funding |
| Behaviours | Visible support and positive reinforcement for following the PMP, applying best practices, and sharing lessons learned |
Warning: When management delegates integration entirely to the project manager without active participation, two things happen: decisions are delayed at gate reviews, and the project team loses confidence that the organisation is genuinely committed to the process. Both are precursors to project failure.
The Pitfalls: Where Integration Breaks Down
1. Treating integration as a phase, not a discipline. Integration is not something you "do" at the start and finish. It is a continuous function. The moment you stop actively integrating, functional silos re-emerge.
2. Confusing project management software with integration. A Gantt chart in Microsoft Project is a scheduling tool, not an integration tool. Integration requires human judgement — resolving conflicts, setting priorities, making trade-off decisions across interfaces.
3. Underinvesting in FEL. The temptation to rush to execution is the single most expensive mistake in project management. Independent Project Analysis (IPA) has demonstrated statistically that projects with inadequate front-end loading consistently experience cost overruns and schedule delays.
4. No post-project feedback loop. Without post-project assessments and business evaluations, the organisation cannot learn. The integration function extends beyond project closure — it connects the current project's outcomes to the next project's inputs.
Relationship details
| From | Relationship | To |
|---|---|---|
| Phase 1 — Initiating | leads to | Phase 2 — Planning |
| Phase 2 — Planning | leads to | Phase 3 — Executing |
| Phase 3 — Executing | leads to | Phase 4 — Monitoring & Controlling |
| Phase 4 — Monitoring & Controlling | leads to | Phase 5 — Closing |
| Phase 5 — Closing | leads to | Lessons Learned |
| Lessons Learned | leads to | Phase 1 — Initiating |
Key Takeaways
- Integration is the PM's primary function — not scope, not cost, not schedule. Those are components. Integration is the system.
- The five-phase PMP provides the structural backbone for integration, with gate reviews serving as management checkpoints.
- Front End Loading (Phases 1–3) is where the most consequential integration decisions are made. Skipping or compressing FEL is the fastest path to cost overruns.
- Value Improving Practices and TCM tools must be applied at the right phase to be effective — timing matters as much as technique.
- Management must actively participate in integration through accountability, accessibility, leadership, resourcing, and visible behavioural support.
- Post-project assessment and business evaluation close the loop, turning one project's experience into the next project's advantage.
Next in the series: Part 2 — Scope Management: From WBS Architecture to Killing Scope Creep. We dismantle the work breakdown structure, explore how scope verification actually works, and confront the silent killer of projects: uncontrolled scope change.