Predictive vs Adaptive vs Hybrid: Development Approach Selection

PMBOK v8 Definition

The development approach defines how the project team creates deliverables throughout the project life cycle. Predictive approaches plan deliverables upfront, structured in a Work Breakdown Structure (WBS). Adaptive approaches progressively define deliverables through a backlog at the beginning of each iteration. Hybrid approaches combine elements from both predictive and adaptive methodologies, providing flexibility to adapt to changing conditions while retaining control over predictable aspects. This process also identifies quality requirements and standards for deliverables and determines how the project will demonstrate compliance.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about development approach selection, tailoring, and project life cycle configuration. Questions test your ability to determine which approach fits specific project characteristics—particularly when requirements are uncertain, deliverables can be modularized, or multiple teams are involved. Expect scenario-based questions asking you to identify the best approach for a given situation.

Key Points to Remember (for the exam)

• Predictive Approach: Deliverables structured in WBS at project start; best when requirements are clear and stable
• Adaptive Approach: Deliverables progressively defined through backlog; requirements refined each iteration
• Hybrid Approach: Combines predictive and adaptive elements; most projects benefit from this approach today
• Common Pattern: Early processes use adaptive development, followed by predictive rollout phase
• Hybrid Levels: Level 1 (predictive dominant), Level 2 (balanced), Level 3 (adaptive dominant)
• Key Benefit: Helps stakeholders and project team understand value delivered through product, service, or result
• Practical Application: Different deliverables in same project can use different approaches (e.g., adaptive software + predictive data center construction)

Typical PMI Exam Example

A project manager is planning a software implementation that requires custom development (uncertain requirements) but must be deployed in a new data center (fixed specifications). The project manager should use a hybrid approach—adaptive for the software development (backlog-driven iterations) and predictive for the data center construction (WBS-structured deliverables).

PMI Exam Traps

• Trap: Thinking predictive and adaptive are mutually exclusive Reality: Most projects benefit from hybrid approaches combining both methodologies

• Trap: Confusing WBS (predictive) with backlog (adaptive) Reality: WBS structures deliverables upfront; backlog defines deliverables progressively per iteration

• Trap: Believing adaptive means no planning Reality: Adaptive approaches plan at the beginning of each iteration, not upfront for the entire project

• Trap: Assuming hybrid always means 50/50 split Reality: Hybrid exists on a spectrum (Levels 1-3) where one approach may dominate

Important PMI Connections

Quick Review Questions

1. A project has two main deliverables—one with clear requirements and one with high uncertainty. What development approach should the project manager select?

2. In an adaptive approach, when are deliverables defined and structured?

3. What are the three levels of hybrid approaches on the predictive-to-adaptive spectrum?

4. A project uses adaptive development for the first phases, then switches to predictive for rollout. What type of approach is this?

5. What is the key benefit of identifying the development approach early in the project?

PMBOK v8 Reference

Section 4.2 - Develop Project Management Plan (Development Approach and Life Cycle) Sections 4-8 through 4-11 - Hybrid Approach Patterns