Hybrid Approach: Combining Predictive and Adaptive Life Cycles
PMBOK v8 Definition
A hybrid development approach is a combination of adaptive and predictive approaches, incorporating elements from both methodologies throughout the project life cycle. This approach provides flexibility to adapt to changing conditions while retaining control over predictable aspects, making it suitable when certain project components benefit from a predictive approach (e.g., infrastructure setup) while others require an adaptive approach (e.g., user interface development and integration).
Why It Matters for the Exam
The hybrid approach appears frequently in PMI exam questions testing your ability to select the appropriate development approach based on project characteristics. Questions typically present a scenario with mixed requirements—some well-defined and stable, others uncertain and evolving—and ask you to identify the correct approach. The PMI exam tests your understanding that most modern projects benefit from a hybrid approach rather than exclusively adaptive or predictive methodologies.
Key Points to Remember (for the exam)
- Definition: A hybrid approach is a combination of adaptive and predictive approaches throughout the life cycle
- Three Levels (PMI Disciplined Agile®): Level 1 (predictive dominant with adaptive elements), Level 2 (balanced combination), Level 3 (adaptive dominant with predictive components)
- Common Patterns: Early processes use adaptive development, followed by predictive rollout phase
- When to Use: Projects with two main deliverables where one uses adaptive and the other uses predictive approach
- Key Examples: Construction with IT integration (smart building), healthcare solutions (electronic medical records), software installed in new data center (adaptive software + predictive data center construction)
- Flexibility Principle: Various phases can be approached differently; subsidiary streams can use different ways of working
- Not Either/Or: Focusing exclusively on either adaptive or predictive does not fully address modern project complexities
Typical PMI Exam Example
A hospital project involves implementing an electronic medical records system. The infrastructure setup (servers, network, hardware) has clearly defined requirements and can be planned predictively. However, the user interface development and integration require flexibility as end-user needs evolve during development. What development approach should the project manager select?
Answer: A hybrid approach, combining predictive for infrastructure and adaptive for UI development.
PMI Exam Traps
-
Trap: Assuming a project must be either fully predictive or fully adaptive
- Reality: Most projects benefit from a hybrid approach that combines both
-
Trap: Thinking hybrid means using the same approach for all project phases
- Reality: Different phases can use different approaches; subsidiary streams can use different ways of working
-
Trap: Confusing hybrid Level 1 (predictive dominant) with a fully predictive approach
- Reality: Level 1 includes adaptive elements to reduce specific pain points while remaining primarily predictive
-
Trap: Believing adaptive is only for software and predictive is only for construction
- Reality: Hybrid approaches apply across industries; construction with IT integration is a classic hybrid example
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Development Life Cycle Selection | Input to determining approach | Hybrid is selected when project has both predictable and uncertain elements |
| Disciplined Agile® (DA®) Toolkit | Provides framework for hybrid levels | Three hybrid levels are defined by DA® |
| Adaptive Approach | Component of hybrid | Used for evolving scope, high uncertainty, early/incremental delivery needs |
| Predictive Approach | Component of hybrid | Used for well-defined, stable requirements with clear specifications |
| Project Deliverables | Determines approach per deliverable | Different deliverables can use different approaches within same project |
Quick Review Questions
-
A construction project involves building a smart building with complex IT systems. The building structure is well-defined, but the IT systems need flexibility during development. What approach should be used?
-
What are the three levels of hybrid approaches described in the PMI Disciplined Agile® toolkit?
-
In a hybrid approach, can different phases of the same project use different development life cycles?
-
A project needs to develop software (evolving requirements) and build a new data center (fixed specifications). Should the project use one approach or a hybrid approach?
-
What is the key reason that most projects benefit from a hybrid approach rather than exclusively adaptive or predictive methodologies?
PMBOK v8 Reference
Section 4.2.3 - Hybrid Approaches (PMBOK v8)