Project Approach Used: Hybrid, Predictive, and Adaptive Methods

PMBOK v8 Definition

The project approach used is the combination of predictive, adaptive, or hybrid development approaches throughout the project life cycle. These approaches are viewed as a spectrum, with predictive on one end and adaptive on the other, and hybrid as a mix of both. A hybrid approach may include a small adaptive element within a primarily predictive project, or a largely adaptive approach with a predictive component.

Why It Matters for the Exam

This concept appears frequently in questions about tailoring, development life cycles, and choosing the right approach for specific project contexts. You will see it in situational questions where you must identify which approach best fits a given project scenario, and in questions about how to manage projects with mixed requirements.

Key Points to Remember (for the exam)

• Three Approaches on a Spectrum: Predictive → Hybrid → Adaptive (Figure 4-2 in PMBOK v8)
• Hybrid Definition: A combination of predictive and adaptive approaches throughout the life cycle
• Two Hybrid Patterns Tested: (1) Small adaptive element within a primarily predictive project, (2) Largely adaptive approach with a predictive component
• Common Hybrid Example: Construction project (predictive) with IT integration (adaptive) – e.g., smart building with complex IT systems
• Hybrid Scheduling: High-level schedule uses predictive techniques for milestones, while subordinate streams use adaptive or predictive methods depending on their characteristics
• Four Common Hybrid Patterns: Early processes use adaptive development, followed by a predictive rollout phase (Figure 4-8 through 4-11)
• Tailoring Focus: In hybrid approaches, scheduling combines the flexibility of adaptive methods with the structured planning of a predictive approach

Typical PMI Exam Example

A project involves building a new data center (predictive construction) while simultaneously developing custom software that will run in that center (adaptive development). The project manager decides to use a hybrid approach, planning the construction with predictive techniques and managing the software development in sprints. This is a correct application of hybrid project management.

PMI Exam Traps

• Trap: Thinking hybrid means 50% predictive and 50% adaptive Reality: Hybrid can be any combination – a small adaptive element in a predictive project, or a predictive component in an adaptive project

• Trap: Confusing development approach with project life cycle Reality: The development approach (predictive, adaptive, hybrid) defines how the project is managed and executed; the project life cycle is the overall framework of phases

• Trap: Assuming all phases of a hybrid project use the same approach Reality: With a hybrid approach, various phases can be approached differently – early processes may be adaptive, followed by a predictive rollout phase

• Trap: Thinking adaptive projects have no schedule structure Reality: Adaptive projects use timeboxed schedules with short-term planning horizons (sprints/iterations); hybrid combines this with predictive milestone planning

Important PMI Connections

Quick Review Questions

1. A construction project to build a smart building with complex IT systems should use which development approach?

2. What are the two specific patterns of hybrid approach described in PMBOK v8?

3. In a hybrid approach, how is scheduling typically handled?

4. What are the three development approaches on the spectrum from predictive to adaptive?

5. Can different phases of a hybrid project use different approaches? If so, give one example pattern.

PMBOK v8 Reference

Section 4 – Project Life Cycles (Figures 4-2, 4-8 through 4-11) and related content on development approaches and hybrid methods.