Project Phase End: Definition and Decision Gate Review

Project Phase End: Definition and Decision Gate Review

PMBOK v8 Definition

A phase gate is "a review at the end of a phase in which a decision is made to continue to the next phase, to continue with modification, or to end a program or project." A project phase is "a collection of logically related project activities that culminates in the completion of one or more deliverables." A project review is "an event at the end of a phase or project to assess the status, evaluate the value delivered, and determine if the project is ready to move to the next phase or transition to operations."

Why It Matters for the Exam

The PMI exam frequently tests your understanding of phase-end reviews as critical governance checkpoints. Questions appear in situational scenarios where you must identify whether a project should proceed, be modified, or be terminated based on phase-end review results. The distinction between a phase gate, project review, and regular status meeting is a common testing point.

Key Points to Remember (for the exam)

  • Phase Gate Purpose: Decision point to continue, continue with modification, or end the program/project
  • Project Review Purpose: Assess status, evaluate value delivered, and determine readiness for next phase or transition to operations
  • Phase Characteristics: Cost and staffing are low at start, increase during work, drop rapidly as phase ends; risk and uncertainty are highest at phase start
  • Phase Types: Phases may be sequential, transitional, or overlapping
  • Deliverable Completion: Each phase culminates in completion of one or more deliverables and/or outcomes
  • Decision Criteria: Entrance criteria and exit criteria are defined for each phase
  • Key Distinction: Phase gate = decision review; Project review = comprehensive assessment including value evaluation

Typical PMI Exam Example

A project manager is completing the design phase of a construction project. The team has delivered all required design documents. The project sponsor schedules a meeting to review the deliverables, assess whether the project should proceed to procurement, and evaluate if the value delivered justifies continued investment. This meeting is best described as a phase gate and a project review.

PMI Exam Traps

  • Trap: Confusing phase gate with a regular status meeting

  • Reality: A phase gate is a formal decision review at phase end; a status meeting is ongoing progress monitoring

  • Trap: Thinking phase gates only allow "continue" or "stop" decisions

  • Reality: Phase gates also allow "continue with modification" as a valid decision

  • Trap: Assuming all phases must be sequential

  • Reality: Phases can be sequential, transitional, or overlapping depending on the project life cycle

  • Trap: Confusing "outcome" with "deliverable"

  • Reality: An outcome is "an end result or consequence of a process or project"; a deliverable is a tangible output produced during a phase

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Project PhaseDefines the scope of the gatePhase gates occur at the end of each project phase
DeliverablePhase completion triggerPhase ends when one or more deliverables are completed
Risk Breakdown Structure (RBS)Risk categorization toolRisks are categorized by project phase to identify exposure areas
Organizational Breakdown Structure (OBS)Resource assignment toolShows relationship between project activities and performing organizational units

Quick Review Questions

  1. What three possible decisions can result from a phase gate review?

  2. What is the difference between a phase gate and a project review?

  3. During which part of a project phase are cost and staffing levels typically lowest?

  4. When risks are categorized by project phase, what is the primary benefit for risk response development?

  5. What must be completed for a project phase to be considered finished?

PMBOK v8 Reference

Section 4.1 - Project Phases (Also referenced in definitions for phase gate, project review, outcome, and organizational breakdown structure)