Figure Predictive Adaptive: Development Life Cycle Approaches in

PMBOK v8 Definition

The PMBOK v8 presents development life cycles along a spectrum from predictive to adaptive approaches. Predictive life cycles (also called waterfall) define scope, schedule, and cost early, with detailed planning upfront and execution in phases. Adaptive life cycles (including agile) use iterative and incremental delivery, with requirements evolving through collaboration and frequent feedback. The "Figure Predictive Adaptive" concept encompasses the spectrum shown in Figures 4-5 through 4-11, including hybrid combinations where predictive and adaptive approaches are used simultaneously or sequentially within a single project.

Why It Matters for the Exam

The PMI exam frequently tests the ability to distinguish between predictive, adaptive, and hybrid life cycles, and to select the appropriate approach based on project characteristics. Expect scenario-based questions where you must identify which life cycle approach best fits a given situation, or recognize hybrid combinations shown in Figures 4-8 through 4-11.

Key Points to Remember (for the exam)

• Predictive Life Cycle (Figure 4-4): Detailed planning upfront; scope, schedule, and cost are defined early; changes are controlled through formal processes
• Predictive with Incremental Delivery (Figure 4-5): Predictive planning with delivery of completed increments to customers
• Adaptive Development Approach (Figure 4-6): Iterative cycles with evolving requirements; scope is flexible, time and cost are fixed
• Agile Approaches Spectrum (Figure 4-7): Plotted by breadth and depth of agile practices
• Hybrid: Adaptive then Predictive (Figure 4-8): Adaptive development phase followed by predictive rollout
• Hybrid: Simultaneous (Figure 4-9): Adaptive and predictive approaches used concurrently throughout the life cycle
• Largely Predictive with Adaptive Component (Figure 4-10): Primarily predictive project with a small adaptive element
• Largely Adaptive with Predictive Component (Figure 4-11): Primarily adaptive project with a predictive element

Typical PMI Exam Example

A software development project has well-understood regulatory requirements that must be delivered first, but user interface features are expected to change based on customer feedback. The project manager selects a hybrid approach: predictive planning for compliance modules, followed by adaptive development for UI features. This matches Figure 4-8 (Adaptive Development Followed by a Predictive Rollout) or a simultaneous hybrid from Figure 4-9.

PMI Exam Traps

• Trap: Assuming "predictive" means no delivery until the end

  • Reality: Figure 4-5 shows predictive with incremental delivery—completed increments are delivered throughout

• Trap: Confusing "adaptive" with "no planning"

  • Reality: Adaptive approaches plan iteratively; they do not eliminate planning, they plan in shorter cycles

• Trap: Thinking hybrid means only sequential phases

  • Reality: Figure 4-9 shows simultaneous hybrid—adaptive and predictive approaches can coexist throughout the life cycle

• Trap: Believing agile always means no documentation

  • Reality: Adaptive approaches balance documentation with working deliverables; Figure 4-7 shows agile varies in breadth and depth

Important PMI Connections

Quick Review Questions

1. A project has stable requirements and regulatory deadlines. Which development approach is most appropriate according to PMBOK v8?
2. Figure 4-8 shows adaptive development followed by predictive rollout. In what project scenario would this hybrid approach be suitable?
3. What is the key difference between a purely predictive life cycle (Figure 4-4) and a predictive life cycle with incremental delivery (Figure 4-5)?
4. When using a simultaneous hybrid approach (Figure 4-9), how are adaptive and predictive elements managed together?
5. According to Figure 4-7, what two dimensions are used to plot agile approaches?

PMBOK v8 Reference

Section 4 – Project Life Cycles, Figures 4-5 through 4-11 (Pages 62-67)