
Choosing the Right Development Approach: Predictive, Adaptive, or Hybrid
PMBOK v8 Definition
The development approach is the method used to create and evolve the project's product, service, or result throughout the project life cycle. According to PMBOK v8, project variables that influence the choice of development approach include stakeholders, schedule constraints, financing uncertainty, project size and complexity, team experience and skills, ease of change, delivery options, risk, and safety requirements. A predictive approach (waterfall, plan-driven) may be optimal when scope can be stabilized early, while adaptive approaches are suitable when requirements evolve and flexibility is needed.
Why It Matters for the Exam
This concept appears frequently in situational questions where you must recommend the best development approach based on project characteristics. Expect 2-4 questions testing your ability to match project conditions (fixed end date, evolving requirements, regulatory oversight) with the correct approach. These questions often appear in the Planning domain and require distinguishing between predictive, adaptive, and hybrid approaches.
Key Points to Remember (for the exam)
-
Predictive Approach: Optimal when scope stabilizes early, fixed end date must be met, significant investment or regulatory oversight exists, safety requirements are rigorous, and changes are difficult or costly to incorporate.
-
Adaptive Approach: Optimal when stakeholders require significant involvement throughout, early delivery of partial value is beneficial, financing uncertainty exists, project is large and complex with evolving requirements, and risk needs active management.
-
Hybrid Approach: Most projects today require a hybrid approach combining elements of both predictive and adaptive. Relying solely on one approach is no longer sufficient for modern project complexities.
-
Project Variables Influencing Choice: Stakeholders, schedule constraints, financing uncertainty, project size and complexity, team experience and skills, ease of change, delivery options, risk, safety requirements, and interdependencies.
-
Team Skills for Adaptive: Projects using adaptive or agile approaches benefit from teams with strong communication, collaboration, and problem-solving skills.
-
Common Confusion: Confusing "adaptive" with "no planning" – adaptive approaches still require planning, but planning is iterative and progressive rather than front-loaded.
Typical PMI Exam Example
A project manager is assigned to a large infrastructure project with rigorous safety regulations and a fixed government-mandated completion date. The scope is well-defined from the start. Which development approach is most appropriate?
Answer: Predictive approach, because the conditions include stable scope, fixed end date, regulatory oversight, and rigorous safety requirements.
PMI Exam Traps
-
Trap: Assuming adaptive approaches are always better for complex projects.
Reality: Complex projects with stable scope and regulatory requirements often need predictive approaches. -
Trap: Thinking hybrid means 50% predictive and 50% adaptive.
Reality: Hybrid exists on a spectrum (Levels 1-3), where one approach may be dominant while the other addresses specific pain points. -
Trap: Confusing "iterative" with "adaptive" as interchangeable terms.
Reality: Iterative is one type of adaptive approach; adaptive also includes incremental and agile methods. -
Trap: Believing adaptive approaches require less stakeholder involvement.
Reality: Adaptive methods typically call for significant stakeholder involvement throughout the process.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Life Cycle | Determines approach | Predictive uses sequential phases; adaptive uses iterative cycles |
| Stakeholder Engagement | Influences approach | Adaptive requires high stakeholder involvement |
| Risk Management | Approach selection factor | Adaptive helps manage uncertainty and risk |
| Scope Management | Approach determines method | Predictive: stable scope; Adaptive: evolving scope |
Quick Review Questions
-
A project has rigorous safety requirements and significant regulatory oversight. Which development approach is most appropriate?
-
A project team has strong communication and collaboration skills, but the scope is uncertain. Which approach would likely generate more value?
-
When should a hybrid approach be selected over a purely predictive or purely adaptive approach?
-
What project variable makes a predictive approach optimal when a fixed end date must be met?
-
A project involves financing uncertainty. According to PMBOK v8, which approach may generate more value in this environment?
PMBOK v8 Reference
Section 4.2 – Development Approaches and Project Life Cycle
Section 4.3.2 – Project Variables Influencing Development Approach