Project Life Cycles: Predictive and Adaptive Development Approaches
PMBOK v8 Definition
Project life cycles are the series of phases that a project passes through from its start to its completion. The PMBOK v8 defines two primary development approaches: Predictive Approaches, where scope, time, and cost are determined early in the project, and Adaptive Approaches, where requirements are detailed iteratively and the project evolves through cycles. These approaches are detailed in Section 4.2 of the PMBOK v8, which falls under the broader topic of Project Life Cycles (Section 4).
Why It Matters for the Exam
This concept appears frequently in PMI exam questions testing your ability to select the correct development approach based on project characteristics—such as level of uncertainty, complexity, and stakeholder involvement. Expect situational questions where you must match a project scenario (e.g., fixed requirements vs. evolving user needs) to the appropriate approach.
Key Points to Remember (for the exam)
- Predictive Approaches: Scope, time, and cost are defined upfront; work is performed in a sequential, phase-by-phase manner. Best for projects with clear, stable requirements and low uncertainty.
- Adaptive Approaches: Requirements are detailed iteratively; the project progresses through short cycles (e.g., sprints) with frequent feedback. Best for projects with high uncertainty, evolving requirements, or complex environments.
- Project Phases (Section 4.1): A project may have multiple phases (e.g., concept, development, implementation, closeout). The life cycle approach determines how phases are sequenced and managed.
- Common Confusion: "Predictive" is often confused with "Waterfall"—they are similar, but PMBOK v8 uses "Predictive" as the standard term. "Adaptive" includes Agile, Scrum, and other iterative frameworks.
- Key Exam Tip: The choice between predictive and adaptive is driven by uncertainty and requirement stability, not by project size or team preference alone.
- Holistic View (Section 3.3): The principle "Adopt a Holistic View" reminds you to consider the entire project context—including organizational culture, stakeholder needs, and risk—when selecting the life cycle approach.
Typical PMI Exam Example
Scenario: A company is building a new software platform for a client with well-defined regulatory requirements that will not change. The project has a fixed budget and a deadline. Question: Which development approach is most appropriate? Answer: Predictive approach, because requirements are stable and scope is defined upfront.
PMI Exam Traps
- Trap: Assuming "Adaptive" always means "Agile" in the strict sense. Reality: Adaptive includes any iterative approach (e.g., incremental, spiral) where requirements evolve through cycles.
- Trap: Thinking Predictive approaches are always "slower" or "worse." Reality: Predictive is ideal when requirements are clear and changes are costly (e.g., construction, regulated industries).
- Trap: Confusing "Project Life Cycle" with "Product Life Cycle." Reality: Project life cycle focuses on project phases (start to finish); product life cycle covers the entire product lifespan (including operations and disposal).
- Trap: Believing a project can only use one approach for its entire duration. Reality: Some projects use a hybrid approach—predictive for early phases, adaptive for later phases—depending on changing conditions.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Phases (4.1) | Defines the structure of the life cycle | Phases are sequential in predictive; iterative in adaptive. Know how phases differ between approaches. |
| Project Management Principles (3.2) | Guiding framework | The principle "Focus on Value" (3.4) drives the choice of approach—adaptive prioritizes delivering value early. |
| Performance Domains (3.2) | Aligned with life cycle | The "Development Approach and Life Cycle Performance Domain" directly governs how you select and tailor the approach. |
| Sponsor, Customer, or Product Owner (2.5.2) | Key stakeholder roles | In adaptive approaches, the Product Owner is critical for prioritizing backlog; in predictive, the Sponsor approves scope changes. |
Quick Review Questions
- A construction project has fully defined blueprints, a fixed budget, and a strict timeline. Which development approach is most appropriate?
- A software startup is building a new app where user requirements are expected to change frequently based on market feedback. Which approach should be selected?
- What is the primary factor that determines whether a predictive or adaptive approach is used?
- In which PMBOK v8 section would you find the detailed definitions of predictive and adaptive approaches?
- A project uses a hybrid approach—predictive for initial planning and adaptive for development. Is this acceptable according to PMBOK v8?
PMBOK v8 Reference
Section 4 - Project Life Cycles
Section 4.1 - Project Phases
Section 4.2 - Project Development Approaches
Section 4.2.1 - Predictive Approaches
Section 4.2.2 - Adaptive Approaches