Schedule Delivery Phases: Connecting Business Value Through Project Life Cycles

PMBOK v8 Definition

The project life cycle consists of phases that connect the delivery of business and stakeholder value from the beginning to the end of the project. Represent the project work—from project launch to close—in project phases, ensuring the phases include the appropriate exit criteria. A holistic approach to delivering the project outcomes is developed by selecting and developing a delivery schedule that demonstrates the project is planned in a holistic manner with no gaps or areas of misalignment.

Why It Matters for the Exam

Schedule Delivery Phases is frequently tested because it bridges the Project Life Cycle concept with the Schedule Performance Domain—two areas the PMI exam emphasizes in situational and definition-based questions. Expect questions that test whether you understand that phases must connect value delivery, not just represent sequential work blocks, and that exit criteria are mandatory gates between phases.

Key Points to Remember (for the Exam)

Core Principle: Project life cycle phases connect the delivery of business and stakeholder value from start to end—not just task completion.
Exit Criteria: Every phase must include appropriate exit criteria before proceeding to the next phase. This is a non-negotiable PMBOK requirement.
Holistic Planning: The delivery schedule must demonstrate holistic planning with no gaps or areas of misalignment across the entire project life cycle.
Schedule Documentation: Must include task dependencies, durations, resource allocations, and milestones based on the selected development approach (predictive, adaptive, or hybrid).
Development Approach Alignment: Scheduling approaches must be consistent with the project deliverables and the chosen development approach.
Phase Types: Phases may be sequential, transitional, or overlapping—the exam tests that you recognize all three are valid.
Life Cycle Independence: Project life cycles are independent of product life cycles—a common exam trap.

Typical PMI Exam Example

A project manager is planning a software development project using an adaptive approach. The project has four phases: Discovery, Development, Testing, and Deployment. During the Discovery phase, stakeholders request that the Development phase begin before Discovery is fully complete. What should the project manager do?

Answer: Recognize that overlapping phases are acceptable per PMBOK v8, but ensure exit criteria for the Discovery phase are still defined and partially met before transitioning.

PMI Exam Traps

Trap: Confusing "project phases" with "project management process groups"
- Reality: Phases are sequential/overlapping work periods delivering value; process groups (Initiating, Planning, etc.) are management activities applied within each phase.
Trap: Thinking all phases must be sequential
- Reality: Phases can be sequential, transitional, or overlapping—all are valid depending on project needs.
Trap: Assuming exit criteria are optional if the team is experienced
- Reality: PMBOK v8 explicitly requires appropriate exit criteria for all phases, regardless of team maturity.
Trap: Confusing project life cycle with product life cycle
- Reality: Project life cycles are independent of product life cycles; a project may produce outputs that enable product outcomes over time.

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Schedule Performance Domain	Output of / Enables	The delivery schedule is a key outcome of defining phases; exam tests alignment between phases and schedule
Development Approach (Predictive/Adaptive/Hybrid)	Determines phase structure	Predictive uses sequential phases; adaptive uses overlapping/iterative phases
Exit Criteria	Mandatory component of each phase	Exam tests that exit criteria must be defined and met before phase transition
Business Value Delivery	Primary purpose of phases	Phases must connect value delivery—not just complete work packages
Project Life Cycle	Foundational framework	Provides the structure within which phases are organized; tested as the "big picture" context

Quick Review Questions

What is the primary purpose of project life cycle phases according to PMBOK v8?
A project has three phases with no documented exit criteria. Is this compliant with PMBOK v8? Why or why not?
In an adaptive project, can phases overlap? What must still be in place for each phase?
What essential elements must schedule documentation include, based on the selected development approach?
True or False: A project life cycle is the same as a product life cycle. Explain your answer.

PMBOK v8 Reference

Section 2 – Project Management Performance Domains (Schedule Performance Domain) Section 4 – Project Life Cycles Table 2-7 – Check Outcomes: Schedule Performance Domain