2.1 Linear Project Life Cycles and Phase Gates

Linear Project Life Cycles and Phase Gates

Quick Answer: A linear project life cycle is a phased, sequential delivery model comprising the four phases named in APM BoK7 — Concept, Definition, Deployment and Transition — suited to projects where requirements can be clearly specified upfront. Handover, commissioning, acceptance and formal closure all sit inside Transition; APM has no separate Closure phase. At the conclusion of each phase, formal gate reviews evaluate performance against the business case and determine whether to proceed, hold, rework, or terminate the project.

What is a Project Life Cycle?

Definition (APM BoK7 glossary): A life cycle is a framework comprising a set of distinct high-level stages required to transform an idea or concept into reality in an orderly and efficient manner. BoK7 adds that life cycles "offer a systematic and organised way to undertake project-based work and can be viewed as the structure underpinning deployment". A phase is the major subdivision of a life cycle.

A project life cycle is therefore the framework of inter-related phases through which a project moves from its initial inception to its formal closure. Rather than treating a project as an unbroken, continuous continuum of activity, project management structures the work into distinct, manageable stages. This structured segmentation provides governance, enhances control, and enables progressive elaboration—the ongoing refinement of plans, estimates, and specifications as information matures.

A life cycle serves as the master blueprint for project delivery. It defines the sequence of activities, specifies the governance boundaries between stages, establishes mandatory documentation checkpoints, and dictates when major commitments of capital and resources occur. Crucially, life cycles allow organizations to manage risk proactively by limiting financial exposure to one phase at a time.

---

Why Structure Projects into Sequential Phases?

Embarking on a complex project without stage boundaries creates severe operational and financial vulnerabilities. Structuring a project into discrete sequential phases delivers several strategic and practical benefits:

1. Incremental Financial Commitment and Risk Mitigation: Capital investments are released in tranches corresponding to phase boundaries. An organization does not commit the entire budget upfront; instead, it funds only the Concept phase, then the Definition phase, committing major deployment capital only after risks and solutions are thoroughly analyzed.
2. Governance and Strategic Alignment: Organizational priorities, market dynamics, and regulatory environments evolve over time. Phase boundaries allow senior leadership to confirm that the project remains aligned with overall business strategy before authorizing further spend.
3. Progressive Elaboration and Planning Accuracy: In early stages, uncertainty is high and estimates are coarse (e.g., order-of-magnitude estimates with high variance). As the project progresses through Definition, detailed analysis produces precise schedules, cost baselines, and technical specifications, reducing the cone of uncertainty.
4. Structured Resource Mobilization: Different phases require radically different skillsets. Concept requires strategic analysts and economists; Definition requires systems architects, design engineers, and schedulers; Deployment demands site managers, contractors, and builders; and Transition requires trainers, change managers and — for contract close-out and financial reconciliation — commercial auditors. Phasing ensures specialized resources are engaged only when needed.
5. Formal Decision Gateways: Phase boundaries create natural pauses where independent assurance, peer reviews, and executive gatekeepers evaluate deliverable quality and project health before work progresses.

---

The Four Phases of the APM BoK7 Linear Life Cycle

Definition (APM BoK7 glossary): A linear life cycle is a life cycle that aims to complete a project within a single pass through a set of distinct phases that are completed serially and span from the development of the initial concept to the deployment of an ultimate output, outcome or benefits.

Learn this list exactly. BoK7 section 1.2.2 states that "a typical linear life cycle encompasses multiple phases" and then names four: Concept, Definition, Deployment and Transition. APM's own PFQ sample paper asks for "the correct sequence for the stages of a linear project life cycle" and the published answer is Concept, Definition, Deployment, Transition.

Concept ──► Definition ──► Deployment ──► Transition

Why there is no separate "Closure" phase

Many general project management texts (and most PMI-influenced training material) show a fifth Closure phase. APM does not. The BoK7 glossary is explicit:

• Transition: "The fourth phase in a linear cycle where results are handed over, commissioned and accepted by the sponsor, culminating in formal closure."
• Handover: "The point as part of the transition phase of a linear life cycle, where deliverables are commissioned and handed over to the permanent organisation to adopt."
• Closure: "The formal end point of a project, programme or portfolio; either because planned work has been completed or because it has been terminated early."

So in APM's model closure is a point, not a phase, and handover sits inside Transition. Administrative closure, contract close-out, team demobilisation, the post-project review and the lessons learned report all still happen — they are simply the closing activities of the Transition phase. If a PFQ question offers a five-phase linear life cycle ending in "Closure", that option is wrong.

In a pure linear model, each phase must be substantially completed and approved at a decision gate before the subsequent phase commences.

1. Concept Phase

• BoK7 wording: "Development of an initial idea through initial studies and high-level requirements management, and assessment of viability, including an outline business case."
• Purpose: To identify the problem, need, or commercial opportunity, explore potential solutions at a high level, verify strategic fit, assess feasibility, and determine whether the initiative justifies further detailed investigation.
• Key Inputs: Organizational strategic goals, business opportunity briefs, customer requests, problem statements, regulatory mandates, and high-level stakeholder aspirations.
• Core Activities: Initial stakeholder identification, high-level feasibility studies, options exploration (including the 'do nothing' option), rough-order-of-magnitude (ROM) cost and schedule estimation, preliminary risk identification, and appointment of the Project Sponsor.
• Primary Outputs: The Outline Business Case, preliminary scope statement, feasibility report, and the formal submission for entry into Definition.

2. Definition Phase

• BoK7 wording: "Development of a detailed definition, plans and statement of requirements that include a full justification for the work."
• Purpose: To evaluate the options explored in Concept, select the preferred solution, capture detailed stakeholder requirements, and develop the comprehensive baseline plan required to deliver the project.
• Key Activities: Comprehensive requirements capture and engineering, options appraisal and trade-off analysis, selecting the preferred technical and delivery approach, developing the Work Breakdown Structure (WBS) and schedule, resource profiling, risk register population and risk analysis, formulating procurement and contract strategies, and finalizing quality management plans.
• Primary Outputs: The Project Management Plan (PMP) (the output of integrated planning), the Full Business Case, the approved deployment baseline (scope, quality, resourced schedule and associated cost), and supplier contracts or procurement packages.

3. Deployment Phase

• BoK7 wording: "Implementation of plans and verification of performance through testing and assurance to realise intended outputs, outcomes and benefits."
• Purpose: To execute the work packages defined in the PMP, monitor and control progress against the deployment baseline, manage risks, issues and stakeholders, implement formal change control, and manufacture, construct, or assemble the agreed deliverables.
• Key Activities: Managing project teams and specialist subcontractors, progress monitoring and reporting, executing quality control inspections and tests, proactively managing emerging issues and risks, managing communication across stakeholder groups, and controlling scope modifications via formal change control procedures.
• Primary Outputs: Fully constructed, tested, and verified project deliverables (outputs), progress status reports, risk and issue registers, change registers, and quality records.

4. Transition Phase (Handover, Acceptance and Formal Closure)

• BoK7 wording: "Handover, commissioning and acceptance of outputs to the sponsor and wider users, culminating in formal closure."
• Purpose: To hand over the verified deliverables into the operational environment, ensure users and operational staff are fully prepared, achieve formal acceptance sign-off, and then bring the project to a formal administrative, financial and contractual end.
• Handover and acceptance activities: User acceptance testing, pre-commissioning and final commissioning trials, operational staff training, end-user familiarisation, transferring maintenance contracts and operating manuals, updating enterprise asset registers, and obtaining formal acceptance certificates.
• Closure activities (still inside Transition): Closing supplier contracts and settling final commercial accounts, administrative closure of products, archiving project files and baseline data, disbanding the project team, closing down financial cost codes, holding the post-project review, and writing the lessons learned report.
• Primary Outputs: Signed handover / acceptance certificate, operational documentation (as-built drawings, maintenance manuals, warranties), trained users and operators, post-project review report, documented lessons learned, archived project repository, and formal closure sign-off.

Where do adoption and benefits realisation go? They are not part of the linear life cycle. BoK7 adds them only in the extended life cycle (see section 2.3). Operation and termination are added only in the product life cycle. Keep the three models separate in your head.

---

Comprehensive Linear Life Cycle Phase Matrix

The following matrix details each phase of the linear life cycle across its purpose, inputs, activities, outputs, and the central question evaluated at its conclusion.

---

Gate Reviews (Decision Gates) and Governance

A gate review (also known as a decision gate, stage gate, or tollgate) is a formal, mandatory governance checkpoint situated between adjacent phases of the life cycle. At a gate review, the project’s performance to date, current risk exposure, and forward-looking plans are formally scrutinized by the Project Sponsor, governance board, or executive steering group.

Ownership and Roles at the Gate

• Project Sponsor (Chair): The Sponsor owns the business case and chairs the gate review. The Sponsor is accountable for deciding whether the project continues to represent a worthwhile organizational investment.
• Project Manager: Prepares and presents the evidence, including the PMP, progress reports, risk evaluations, and phase completion documentation.
• Governance Board / Key Stakeholders: Provide strategic oversight, challenge assumptions, assess organizational impact, and confirm resource availability.

Gate Review Decision Outcomes

A gate review culminates in one of four formal decisions:

1. Go (Proceed): The phase deliverables meet required quality standards, the business case remains compelling, risks are acceptable, and plans for the next phase are robust. Unconditional authorization and funding for the next phase are granted.
2. Go with Conditions: The project may proceed to the next phase, but specific minor shortcomings, outstanding actions, or informational gaps must be resolved by a specified deadline.
3. Hold / Rework: Critical uncertainties, planning flaws, or unacceptable risks exist. The project is paused without authorizing the next phase until the team reworks plans, refines the business case, or mitigates critical risks for re-evaluation.
4. Stop (Terminate): The business case is no longer viable, strategic alignment has been lost, technological obsolescence has occurred, or projected costs outweigh expected benefits. The project is terminated immediately, preventing further waste of corporate capital.

Key Criteria for Passing a Gate

To pass a gate review successfully, a project must demonstrate:

• Continued Business Justification: The return on investment, net present value, or strategic benefits remain positive and aligned with corporate goals.
• Satisfactory Deliverable Quality: Deliverables required for the concluding phase meet defined quality criteria and specifications.
• Robust Forward Planning: The plan for the upcoming phase is detailed, realistic, and supported by appropriate schedule and cost estimates.
• Resource Availability: Necessary funding, personnel, specialist equipment, and supplier capacity are confirmed for the next stage.
• Manageable Risk Exposure: Identified threats are within organizational risk appetite, and viable mitigation strategies are in place.