Whether you are running a waterfall software rollout, an agile product sprint, or a blended contact centre transformation, every project you manage passes through the same five foundational phases — Initiating, Planning, Executing, Monitoring & Controlling, and Closing.
What has changed with PMBOK 8 (2025) is the layer beneath those phases: the life cycle approach you choose to run the work. PMBOK 8 formally positions four delivery approaches — predictive, iterative, adaptive (agile), and hybrid — as equally valid options. No single approach is the default anymore. The choice depends on your project’s requirements clarity, rate of change, and stakeholder engagement model.
Practitioner note: In 20+ years of project delivery, the shift I see most often is teams defaulting to waterfall out of habit rather than fitness for purpose. PMBOK 8 pushes back on that directly — and it is the right call.
This article covers both the classic five-phase structure (which still holds under PMBOK 8) and the updated life cycle thinking you need to know for the PMP exam and for real-world delivery.
What Is the Project Management Life Cycle?
The project management life cycle is the overarching structure that takes a project from its business case through to formal closure. It is distinct from the methodology you use (Scrum, PRINCE2, SAFe) and distinct from the life cycle approach (predictive vs. hybrid). Think of it this way:
| Layer | What It Defines | Example |
| Life Cycle Phases | The stages all projects go through | Initiating → Planning → Executing → M&C → Closing |
| Life Cycle Approach | How work is organised and value delivered | Predictive, Iterative, Adaptive, Hybrid |
| Methodology / Framework | Specific practices, roles, artefacts | Scrum, PRINCE2, SAFe, Kanban |
PMBOK 8 defines the project life cycle as “the structure that provides the basis for managing the project — determining how phases are sequenced, how deliverables are produced, how decisions are made, and how value is delivered to stakeholders.”
PMBOK 8: The Four Life Cycle Approaches
Before walking through each phase, it is worth understanding the four approaches PMBOK 8 formally defines. Your choice of approach shapes how each phase is executed.
| Approach | How It Works | Best Fit | Common Example |
| Predictive (Waterfall) | Sequential phases, plan-driven | Stable, well-understood scope | Construction, compliance projects |
| Iterative | Repeated cycles with progressive refinement | Evolving requirements, exploratory scope | Product prototyping, R&D |
| Adaptive / Agile | Short delivery cycles, continuous value release | Rapidly changing requirements | Software development, digital products |
| Hybrid | Predictive for stable elements, adaptive for changing ones | Complex projects with mixed scope | Contact centre tech upgrades, transformation programmes |
PMBOK 8 explicitly positions Hybrid as the approach most commonly appropriate for modern, complex projects — it is no longer a workaround. It is the norm.
The 5 Phases of the Project Management Life Cycle
Regardless of which life cycle approach you use, your project moves through these five process groups. In a predictive project they run largely in sequence. And in an adaptive project they may overlap heavily or iterate within sprints. In hybrid they will do both, depending on the workstream.
Phase 1: Initiating
Purpose: Formally authorise the project or a new phase, and establish a shared understanding of why the project exists.
Initiating is triggered when:
- A new project or business need is identified
- A new phase of an existing project begins
- Significant problems require a re-evaluation of the original business case
What Happens in Initiating
This phase is shorter than most people expect, but getting it right is foundational. Key activities include:
- Project Charter: Documents the project’s purpose, high-level scope, constraints, and the authority granted to the project manager. Under PMBOK 8 the Charter remains the primary authorisation artefact.
- Stakeholder Identification: Creating the initial Stakeholder Register — identifying who is affected, their interests, and their potential influence on outcomes.
- Feasibility and Alignment: Confirming the project delivers value aligned with organisational strategy (one of PMBOK 8’s 6 principles: ‘Focus on Value’).
- Project Manager Selection: The PM is formally assigned with defined authority and accountability.
- Environmental Scoping: Reviewing enterprise environmental factors (EEFs) and organisational process assets (OPAs) — culture, systems, historical lessons.
PMBOK 8 Update — Initiating
PMBOK 8 reinforces the principle of stewardship and system thinking at the point of initiation. Before authorising, project sponsors should ask:
- Does this project align with current organisational priorities?
- Have we considered the full system of stakeholders, not just the immediate sponsor?
- What life cycle approach is most appropriate for this type of work?
Practitioner Tip: The most common mistake I see at Initiating is rushing the Charter to get to ‘real work.’ A weak Charter costs you 10× in Executing. Spend the time here.
Phase 2: Planning
Purpose: Establish the full scope, refine objectives, and define the roadmap required to achieve project outcomes.
Planning is revisited when:
- Project initiation is complete and approval is granted
- Executing surfaces new information requiring plan updates
- Monitoring & Controlling identifies deviation requiring re-planning
What Happens in Planning
- Project Management Plan: The master document integrating scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder plans.
- Scope Definition: Project Scope Statement, Work Breakdown Structure (WBS), and WBS Dictionary — the foundational ‘what we will and will not do.’
- Schedule Development: Activity list, network diagram (PDM), critical path analysis, resource-levelled schedule with realistic duration estimates.
- Cost Baseline: Bottom-up cost estimates, contingency reserves, and approved budget (BAC — Budget at Completion).
- Risk Planning: Risk Register, risk response strategies (avoid, transfer, mitigate, accept, exploit for opportunities), risk owners assigned.
- Stakeholder Engagement Plan: How you will communicate, engage, and manage expectations across all stakeholder groups.
- Kick-off Meeting: Formal alignment of team and stakeholders on the plan, roles, and success criteria before execution begins.
PMBOK 8 Update — Planning
PMBOK 8 introduces a more explicit connection between planning and value delivery. Plans should answer:
- How does each deliverable connect to a measurable benefit?
- What governance checkpoints (phase gates) exist to re-validate the plan?
- How will complexity and uncertainty be managed — not just risk?
In a Hybrid approach, Planning covers predictive elements (infrastructure, compliance) in full upfront, while adaptive elements (features, user experience) are planned at the iteration level using a backlog and sprint planning cadence.
Practitioner Tip: In contact centre and operations projects, the planning gap I see most is schedule compression — stakeholders push for aggressive timelines without adjusting scope or resources. Plan the triangle first; negotiate the timeline second.
Phase 3: Executing
Purpose: Complete the work defined in the project management plan to satisfy project requirements and produce deliverables.
Executing is triggered when:
- Planning is formally approved and the project is kicked off
- Integrated Change Control approves a change requiring re-execution
What Happens in Executing
- Direct and Manage Project Work: Coordinating resources, vendors, and teams to produce deliverables according to the plan.
- Quality Assurance: Performing quality audits and process checks to confirm work meets defined standards before deliverables are accepted.
- Team Development and Leadership: Acquiring, developing, and managing the project team — coaching, resolving conflicts, recognising performance.
- Stakeholder Engagement: Actively engaging stakeholders, managing their expectations, and adjusting communications as needed.
- Procurement Management: Working with sellers and vendors, managing contracts, and ensuring vendor deliverables meet quality standards.
- Work Performance Data Collection: Gathering raw data on progress — task completion, costs incurred, issues logged — as inputs to Monitoring & Controlling.
PMBOK 8 Update — Executing
PMBOK 8’s principle of ‘Adapt to Context’ is most visible in Executing. The way work gets done changes depending on life cycle:
| Life Cycle | Executing Looks Like |
| Predictive | Structured work packages, formal deliverable sign-offs, change requests through CCB |
| Iterative | Sprint cycles producing progressively refined outputs, retrospectives after each iteration |
| Adaptive | Daily stand-ups, sprint demos, continuous backlog refinement, working software over documentation |
| Hybrid | Predictive workstreams run alongside agile sprints; integration points managed at phase gates |
Practitioner Tip: Executing is where most projects either gain or lose trust with stakeholders. Visible progress reporting — even informal — is worth more than a perfect status report sent 48 hours late.
Phase 4: Monitoring & Controlling
Purpose: Track, review, and regulate project progress; identify variance from the plan; and initiate corrective action when required.
This phase runs in parallel throughout the entire project — it does not wait for Executing to complete. Key triggers include:
- Work performance data produced during Executing
- Requested changes — corrective actions, preventive actions, defect repair
- Completed deliverables requiring formal verification
- Signals from Initiating (scope creep risk) or Planning (baseline drift)
What Happens in Monitoring & Controlling
- Performance Measurement: Using Earned Value Management (EVM) metrics — CPI, SPI, EAC, VAC — to quantify schedule and cost health against baseline.
- Integrated Change Control: Reviewing, approving, or rejecting all change requests through the Change Control Board (CCB). Every approved change triggers an update to the project management plan.
- Scope Verification: Formal stakeholder inspection and acceptance of completed deliverables (this is different from quality control, which is internal).
- Risk Monitoring: Reviewing risk register, tracking risk triggers, assessing residual and secondary risks, and deploying contingency plans as needed.
- Stakeholder Engagement Monitoring: Assessing whether engagement levels remain appropriate and adjusting communications accordingly.
PMBOK 8 Update — Monitoring & Controlling
PMBOK 8 places stronger emphasis on measuring outcomes, not just outputs. The question is no longer only ‘are we on time and budget?’ but:
- Are the deliverables produced actually delivering the intended value?
- Are stakeholders receiving the benefits they were promised?
- Are we adapting fast enough when the environment changes?
In adaptive and hybrid environments, M&C operates at two levels: sprint-level (daily/weekly velocity, burndown charts) and project-level (overall benefits realisation tracking).
Practitioner Tip: The EVM metrics most project managers track — CPI and SPI — tell you where you are. The metric most project managers ignore — TCPI (To-Complete Performance Index) — tells you what you need to do next to recover. Build that into your status reports.
TCPI is the To-Complete Performance Index — it tells you the cost efficiency you must achieve on all remaining work to hit your target.
Formula (to meet the original Budget at Completion):
TCPI = (BAC − EV) / (BAC − AC)
Formula (if BAC is no longer realistic and you’re targeting the revised EAC):
TCPI = (BAC − EV) / (EAC − AC)
Where:
- BAC = Budget at Completion (original approved budget)
- EV = Earned Value (value of work actually completed)
- AC = Actual Cost (what you’ve spent so far)
- EAC = Estimate at Completion (revised forecast of total cost)
How to read the result:
- TCPI < 1.0 — you have room to spend a bit more per unit of work remaining (easier target)
- TCPI = 1.0 — you must perform exactly as planned going forward
- TCPI > 1.0 — you must be more efficient than you have been (harder target; the higher it is, the less realistic recovery becomes)
A common rule of thumb: if TCPI exceeds 1.10, the original BAC is likely unachievable and a formal re-baseline (new EAC) should be presented to the sponsor.
Phase 5: Closing
Purpose: Formally complete or close the project, phase, or contract — and ensure organisational learning is captured.
Closing is triggered by:
- Successful completion of all project deliverables
- Completion of a discrete project phase requiring formal closure
- Project termination (early closure due to changed priorities, funding, or conditions)
What Happens in Closing
- Final Product Verification: Confirming all work is complete and all acceptance criteria have been met.
- Formal Acceptance: Obtaining formal sign-off from the customer or sponsor — this is the legal and contractual closure point.
- Financial Closure: Final cost reconciliation, releasing budget reserves, closing procurement contracts, and settling all vendor accounts.
- Handoff: Transitioning the completed product or service to the operational team, including documentation, training, and support handover.
- Lessons Learned: Facilitating a structured retrospective and documenting what worked, what did not, and what should be repeated or avoided.
- Archive: Indexing and archiving all project records — plans, baselines, change logs, risk registers — for future reference and audit.
- Team Release: Formally releasing project team members and acknowledging their contributions.
PMBOK 8 Update — Closing
PMBOK 8 gives significantly more weight to benefits realisation in Closing. The question is whether value was actually delivered — not just whether deliverables were handed over. This connects directly to the ‘Focus on Value’ principle.
For adaptive and hybrid projects, Closing may involve a final retrospective at both the iteration level and the project level, ensuring organisational learning is captured at both granularities.
Practitioner Tip: Lessons Learned sessions fail when they become blame sessions or are skipped entirely due to time pressure. Run them as structured facilitated workshops within two weeks of closure — before the team disperses and memory fades.
Phase Gates: The PMBOK 8 Checkpoint Model
PMBOK 8 introduces a stronger emphasis on phase gates — structured decision points at the end of each phase (or iteration) where the project is formally reviewed before proceeding.
At each phase gate, the review team typically assesses:
- Is the deliverable or milestone complete to the required standard?
- Has the value proposition changed since the last gate?
- Are the assumptions still valid?
- Should the project proceed, pause, re-scope, or terminate?
Phase gates are particularly critical in hybrid delivery models, where they serve as the integration point between predictive and adaptive workstreams.
How to Choose the Right Life Cycle Approach
PMBOK 8 provides clear decision criteria. Use this framework when selecting your approach:
| Decision Dimension | Lean Predictive If… | Lean Adaptive If… |
| Requirements Clarity | Scope is well-defined and stable | Scope is evolving or uncertain |
| Rate of Change | Low — environment is stable | High — frequent stakeholder or market changes |
| Complexity & Risk | Moderate — known unknowns dominate | High — unknown unknowns dominate |
| Stakeholder Availability | Limited — stakeholders available at milestones | High — stakeholders can engage frequently |
| Regulatory Constraints | High — compliance requires full upfront specification | Low — flexibility in approach is permitted |
In most real-world projects, the answer lands in Hybrid territory — predictive for governance, compliance, and infrastructure; adaptive for features, UX, and discovery work.
PMBOK 8’s 6 Principles Mapped to the 5 Phases
PMBOK 8 grounds its guidance in six principles. Here is how they show up across the life cycle phases:
| PMBOK 8 Principle | Where It Shows Up Most |
| Be a Diligent, Respectful, and Caring Steward | Initiating — ethical project authorisation and stakeholder identification |
| Create a Collaborative Project Team Environment | Planning & Executing — team building, conflict management, psychological safety |
| Effectively Engage with Stakeholders | All phases — but especially Initiating and Monitoring & Controlling |
| Focus on Value | Planning — value mapping; Closing — benefits realisation review |
| Recognise, Evaluate, and Respond to System Interactions | Monitoring & Controlling — system-level performance and risk response |
| Demonstrate Leadership Behaviours | Executing — team motivation, decision-making under pressure, influence without authority |
Frequently Asked Questions
Are the 5 phases the same as the 5 process groups in PMBOK?
Yes — and no. Historically, PMBOK referred to these as Process Groups (Initiating, Planning, Executing, Monitoring & Controlling, and Closing). PMBOK 8 moves away from the Process Group and ITTO (Inputs, Tools, Techniques, Outputs) structure that defined earlier editions. The five-phase logic remains valid as a practical framework, but PMBOK 8 organises its guidance around Performance Domains and Principles rather than Process Groups.
Did PMBOK 8 remove the 49 processes?
PMBOK 8 does not retain the structured list of 49 processes with prescribed ITTOs that characterised PMBOK 6. It takes a principle-led and outcomes-focused approach. For PMP exam candidates, this means a greater emphasis on situational judgement and life cycle selection rather than ITTO memorisation.
Is hybrid delivery appropriate for all projects?
No. PMBOK 8 positions hybrid as the most commonly appropriate approach for complex, modern projects — but simpler, well-defined projects often run better as fully predictive. The key is deliberate selection based on the dimensions covered in the table above, not defaulting to whichever approach the team is most familiar with.
How do the 5 phases apply to agile projects?
In a fully adaptive (agile) project the five phases still exist, but they collapse in scale and overlap heavily. Initiating may take one sprint. Planning happens at multiple levels — release planning, iteration planning, daily — rather than once upfront. Monitoring & Controlling happens in daily stand-ups and sprint reviews. Closing occurs at both the iteration and project level.
What is the difference between project life cycle and project management life cycle?
The project life cycle describes the work itself — the phases of creating the product (design, build, test, deploy). The project management life cycle describes how the project is managed (Initiating, Planning, Executing, M&C, Closing). The two run in parallel; the project management life cycle provides the governance wrapper around the technical work.
Related Resources on ProjInsights
Deepen your knowledge with these practitioner guides:
- PMBOK 8th Edition: Full Practitioner Guide (ProjInsights)
- What’s New in PMBOK 8 vs PMBOK 7 — Key Changes Explained
- Earned Value Management: CPI, SPI, and TCPI Explained
- How to Write a Project Status Report (Template + Examples)
- Project Charter Template — Free Download
- Lessons Learned Workshop Facilitation Guide
Conclusion
The five phases of the project management life cycle — Initiating, Planning, Executing, Monitoring & Controlling, and Closing — remain the backbone of structured project delivery. What PMBOK 8 adds is a more sophisticated framework for deciding how to run the work within those phases.
The biggest practical takeaway from PMBOK 8 is this: the life cycle approach you choose is a strategic decision, not an administrative one. Choosing predictive for a fast-changing digital product, or adaptive for a compliance-heavy infrastructure upgrade, will create problems that no amount of skilled execution can fix.
Match your approach to the nature of the work. Run the five phases with discipline. And measure value delivered — not just milestones hit.
If you found this article useful, explore the PMBOK 8 full guide and our suite of project management tools and calculators on ProjInsights.com.
For more project management resources, in-depth guides, templates, and practitioner insights, visit projinsights.com.