Hybrid approach
What you'll be able to do
Hybrid = some parts predictive, some parts adaptive — match the approach to the work.
- Hybrid = different approaches for different parts of the project.
- Most common real-world choice in large organisations.
- Reconcile two cadences (milestones + iterations) in reporting.
Hybrid combines predictive and adaptive elements within a single project. PMBOK gives the example of a data-centre rollout where the building construction is predictive (physical, milestone-paced) and the computing capability inside is adaptive (iterated with feedback). Hybrid is the most common real-world choice — pure predictive and pure adaptive are surprisingly rare in large organisations.
Hybrid is not a compromise; it's a tailored choice. The art is identifying which parts of the project benefit from which approach and aligning the team's working practices accordingly. The hybrid PM must reconcile two cadences: predictive milestones with adaptive increments, and the reporting that goes with both.
Watch for hybrid scenarios on the exam where one part of the project is unambiguously predictive (regulated, fixed-scope) and another is unambiguously adaptive (exploratory, feedback-driven). The PMI-correct answer is usually to *not* force one approach across the whole project.
Key points
- Hybrid = different approaches for different parts of the project.
- Most common real-world choice in large organisations.
- Reconcile two cadences (milestones + iterations) in reporting.
- Common on enterprise IT, infrastructure-plus-software programs.
Ask a PMBOK tutor
Paste this lesson plus your question into a fresh chat. Claude is a strong PMP study coach — try asking for additional worked examples, a comparison across PMBOK editions (6e vs 7e vs 8e), or a tougher scenario.