Project Life Cycles and Development Approaches in

PMBOK v8 Definition

A project life cycle is the series of phases that a project passes through from its initiation to its closure (PMBOK v8, Section 57-74). Development approaches are the methods used to create and evolve the project's product, service, or result during the project life cycle, and include predictive, adaptive, hybrid, and incremental approaches (PMBOK v8, Section 59-68). The delivery cadence—how frequently deliverables are provided—is directly linked to the chosen development approach and project life cycle structure (PMBOK v8, Section 69).

Why It Matters for the Exam

This topic appears frequently in PMI exam questions because it forms the foundational framework for selecting the appropriate project management methodology. Questions test your ability to match project characteristics (uncertainty, complexity, regulatory requirements) with the correct development approach and life cycle structure. Expect scenario-based questions asking which approach is best for a given project situation.

Key Points to Remember (for the exam)

• Three Main Development Approaches: Predictive (traditional waterfall), Adaptive (agile/iterative), and Hybrid (combination of both) (PMBOK v8, Section 59-68)
• Project Phases vs. Life Cycle: Phases are sequential stages within a life cycle; the life cycle encompasses all phases from initiation to closure (PMBOK v8, Section 57-59)
• Delivery Cadence Relationship: Predictive approaches have single delivery at end; adaptive approaches have frequent, incremental deliveries; hybrid approaches have mixed cadence (PMBOK v8, Section 69)
• Progressive Elaboration: The iterative process of increasing the level of detail in a project plan as more accurate information becomes available (PMBOK v8, Section 71)
• Gate Reviews: Formal reviews at the end of each phase to assess performance and authorize continuation to next phase (PMBOK v8, Section 58)
• Project Variables: Scope, schedule, cost, quality, resources, and risk are all influenced by the chosen development approach (PMBOK v8, Section 68)
• Common Confusion: Confusing "project phases" with "development approach"—phases exist in all life cycles, but the approach determines how work is performed within those phases

Typical PMI Exam Example

A project has well-defined requirements that are unlikely to change, strict regulatory compliance needs, and a fixed budget. The project team is experienced with traditional methods. Which development approach is most appropriate? Answer: Predictive (waterfall) approach, as it provides clear phase gates and stable requirements management.

PMI Exam Traps

• Trap: Thinking adaptive approaches have no phases

• Reality: All project life cycles have phases; adaptive approaches simply have shorter, iterative phases with continuous planning

• Trap: Confusing hybrid approach with simply using agile tools

• Reality: Hybrid intentionally combines predictive and adaptive elements based on project needs, not just tool selection

• Trap: Assuming delivery cadence is fixed by approach

• Reality: Delivery cadence can be adjusted within an approach; it's a separate decision linked to stakeholder needs

• Trap: Believing progressive elaboration only applies to adaptive approaches

• Reality: Progressive elaboration occurs in all approaches, but at different rates and levels of detail

Important PMI Connections

Quick Review Questions

1. A project has high uncertainty in requirements but needs regulatory approval at specific milestones. Which development approach is most appropriate?

2. What is the relationship between delivery cadence and development approach?

3. How do gate reviews function differently in predictive versus adaptive life cycles?

4. When would a hybrid development approach be preferred over a purely predictive or adaptive approach?

5. What is progressive elaboration and how does it apply to different development approaches?

PMBOK v8 Reference

Section 57-74 - Project Life Cycles (including delivery cadence, development approaches, and Project Management Focus Areas)