Study guide
2.1 Linear Life Cycles and Why Work Is Phased
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.1 Linear Life Cycles and Why Work Is Phased
Key Takeaways Explain This Topic AI
A linear life cycle runs work through sequential phases with decision gates, suiting stable requirements and strong progressive-commitment governance.
Projects use phases in linear life cycles to structure progressive funding, risk reduction, quality reviews, clear accountability, and go/no-go decisions.
A phase is a block of work; a gate is the decision event at its boundary — scenarios that skip reviews describe a missing gate, not a missing phase.
Linear suits stable requirements, well-understood solutions, and contexts where regulators or funders demand formal stage approval.
Weak phasing shows up as late design change, unreviewed business cases, premature procurement, or spend running ahead of progress.
Last updated: August 2026
Why life cycles matter on the PMQ
In the APM Project Management Qualification , life cycles sit in Area A ( Setting up for success ). A project life cycle is the structured series of phases or iterations through which a temporary endeavour moves from idea to completion of project work. Life-cycle design shapes planning, governance, risk handling, stakeholder engagement, change control, and how benefits are later realised.
PMQ long-response and scenario questions often ask you to recommend a life cycle , justify it against project context , or compare features . Memorising labels is not enough: you must explain distinctive features , when each is applicable , and why linear work is phased .
Linear life cycles
A linear life cycle (also called sequential or phase-gate) moves the project through ordered phases. Typical high-level sequence in APM-aligned thinking is along the lines of concept/initiation → definition/design → deployment/development → transition/handover → closure, with local tailoring. Work in a later phase is intended to start only when earlier phase objectives and decision criteria have been met.
Distinctive features of linear life cycles
Sequential progression — phases run largely one after another rather than as many overlapping learning loops.
Decision gates (stage gates) — formal reviews decide whether to continue, stop, re-scope, or re-plan before major further commitment.
Front-loaded definition — requirements and solution design are intended to be understood well before full-scale build or construction.
Predictive planning — baselines for scope, schedule, and cost are established early and controlled through change control.
Clear phase deliverables — each phase has defined outputs (for example a business case, design package, completed asset, or handover pack).
Why projects are structured as phases in linear life cycles
Phasing is not bureaucracy for its own sake. In a linear model, phases support progressive commitment : the organisation invests relatively little early (concept and definition) and only commits large funds, suppliers, and operational disruption after confidence has improved. Phases also:
Reduce risk by forcing early work on feasibility, requirements, and design before irreversible spend.
Create governance checkpoints so sponsors and boards can re-test the business case, compliance, and strategic fit.
Improve quality through phase-end reviews, assurance, and configuration of approved baselines.
Clarify accountability — different skills and contracts can dominate different phases (for example designers early, constructors later).
Enable controlled stop/go — a gate can kill a weak project before deployment waste multiplies.
If requirements are still unstable at late gates, a pure linear approach becomes fragile: change is expensive once detailed design and build are underway.
When linear is applicable
Linear suits contexts where requirements are relatively stable , the solution is well understood , interfaces are known, and regulators or funders demand formal stages . Classic examples include construction of a known building type, heavy civil infrastructure with fixed standards, or pharmaceutical manufacturing facility work with prescribed validation stages. Linear also fits organisations whose culture values detailed upfront approval and fixed budgets.
Naming the phases without over-committing
APM does not mandate one universal set of phase names, and exam scenarios use whatever labels the organisation uses. What examiners reward is that you can describe what a phase is for , not that you recite a particular five-word sequence. A workable mental model:
Phase (typical label) Question the phase answers Typical gate decision
Concept Is there a problem or opportunity worth investigating? Fund definition work?
Definition What exactly will we do, at what cost, by when, with what risks? Approve the full business case and baselines?
Deployment Can we build, test, and assure the solution to the baseline? Continue, re-plan, or stop at interim reviews?
Transition Is the receiving organisation ready to operate and support it? Accept handover into business-as-usual?
Closure Is everything settled — contracts, finances, lessons, records? Formally close the project
Two traps follow. First, do not claim phases never overlap. In practice a linear project may start long-lead procurement during definition; the point is that major commitment follows the gate, not that no activity crosses a boundary. Second, do not equate "phase" with "gate." A phase is a block of work; a gate is a decision event at its boundary. A scenario that says "the project passed into build without a review" describes a missing gate , not a missing phase .
What goes wrong when phasing is weak
PMQ scenarios frequently describe symptoms rather than naming the cause. Learn to read backwards from the symptom to the phasing failure:
"Design changes are still arriving during construction." Definition finished before requirements were stable, or the gate approved an immature design.
"Nobody can say whether the project is still worth doing." Gates exist on paper but the business case is not re-tested at them.
"The supplier was appointed before the specification was agreed." Procurement ran ahead of definition, transferring requirement risk to a contract that cannot absorb it.
"We are 80% spent and 40% complete." Progressive commitment failed: money was released without evidence that earlier phase objectives were met.
In a long response, name the phase boundary that was crossed too early, state which decision should have been taken there, and say who owned that decision.