Study guide
2.3 Project Life Cycles and Extended Life Cycles
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
2.3 Project Life Cycles and Extended Life Cycles
Key Takeaways Explain This Topic AI
A project life cycle covers temporary project work through to completion of deliverables and handover; an extended life cycle also addresses operation, adoption, benefits realisation, and often disposal or decommissioning.
Outputs are what the project creates, outcomes are the changed state they enable, and benefits are the measurable improvements that follow — usually owned in business-as-usual.
A project can succeed in project-life-cycle terms and still fail in extended-life-cycle terms if outputs are never adopted.
Extended-life-cycle thinking starts at initiation: design, requirements, contracts, and transition planning all set what is possible after closure.
The extended life cycle does not replace project closure; both are still required.
Last updated: August 2026
Learning outcome 1b asks for knowledge of the differences between a project life cycle and an extended life cycle . It looks like a definition question and is often answered as one — which is why it is a reliable source of dropped marks. The difference is not merely that one is longer; it is that the two models measure different kinds of success and hand accountability to different people .
Project life cycle versus extended life cycle
APM teaching distinguishes the temporary project life cycle from a broader extended life cycle that connects delivery to lasting organisational value.
Project life cycle
The project life cycle is the managed path of the temporary organisation from initiation through delivery and project closure. It focuses on creating agreed outputs (deliverables) and completing project processes: defining work, deploying the solution, transitioning it to users or operations, capturing lessons, releasing the project team, and closing contracts and accounts as appropriate.
In a project-life-cycle view, success is often framed as delivering the agreed scope, to quality, within time and cost, and handing over cleanly. That is necessary but not always sufficient for organisational value.
Extended life cycle
An extended life cycle looks beyond project closure into the period when outputs are used. It typically includes:
Adoption and embedding — people actually use the new process, system, or facility as intended.
Operation / business-as-usual — the receiving organisation runs and supports the product or asset day to day.
Outcomes and benefits realisation — measurable improvements (for example cost savings, safety performance, revenue, service quality) are tracked against the business case.
Disposal or decommissioning (where relevant) — end-of-life retirement, data deletion, site restoration, or asset replacement planning.
The extended view matters because many projects "finish on time" yet fail to deliver benefits if training is weak, operations are unready, or no one owns post-handover measurement. For PMQ answers, say clearly that the extended life cycle links project outputs to outcomes and benefits , not that it removes the need for project closure.
Comparison
- Focus Project life cycle Extended life cycle
- Time horizon Temporary project duration Beyond project closure into use and often end of life
Primary concern Outputs, project controls, handover, closure Adoption, operations, benefits, disposal/decommissioning
Typical end point (project view) Project closed after transition/handover Value realised (and later asset/service retired if applicable)
Key accountability shift Project manager / project team during delivery Sponsor and operational owners for ongoing benefits
Business case link Justification to start and continue the project Confirmation that intended value is actually achieved
Where the two models disagree about success
Set the two definitions side by side and the examinable tension appears immediately.
A project can be completely successful in project-life-cycle terms and a failure in extended-life-cycle terms : delivered to scope, on time, within budget, handed over — and then barely used, because training was thin, the operating model never changed, or nobody owned the outcome. The reverse also happens: a project that overran and overspent can still be judged a success once benefits land far above forecast.
That is why APM separates outputs , outcomes , and benefits :
Concept What it is Who typically owns it When it appears
Output The deliverable the project creates (a system, a building, a trained team) Project manager By project closure
Outcome The changed state the output makes possible (staff work a new way) Operational / business owner During and after transition
Benefit The measurable improvement that the outcome delivers (cost per case falls 12%) Benefit owner, usually in business-as-usual Often long after closure
The project life cycle is built to deliver outputs . The extended life cycle is what carries them through outcomes to benefits , and often on to disposal or decommissioning at end of life.
Why this matters before closure, not after
The practical trap is treating the extended life cycle as something that begins when the project ends. It does not. Decisions taken early in the project determine whether the extended phases are even possible:
Design choices set operating and maintenance cost for decades — the economic sustainability of the outcome.
Requirements decide whether the benefit is measurable at all ; if no baseline is captured before go-live, the improvement can never be evidenced.
Contract terms decide who holds support and end-of-life obligations .
Transition planning decides whether operational owners are named and ready rather than discovered at handover.
For an exam answer: say that the extended life cycle links project outputs to outcomes and benefits, and often to disposal , that it does not remove the need for project closure, and that planning for it starts at initiation — not at handover.