Development Approach Selection: Predictive, Adaptive, and Hybrid Models

PMBOK v8 Definition

Development Approach Selection is the process of determining the most appropriate method for delivering project deliverables, choosing between predictive (waterfall), adaptive (agile), or hybrid approaches based on project characteristics, deliverables, and organizational factors. This selection directly influences how processes are tailored throughout the project lifecycle, as outlined in Section 3.4.1 "Select Initial Development Approach" and Section 4.3 "Considerations for a Development Approach Selection."

Why It Matters for the Exam

This concept appears frequently in situational questions where you must determine which development approach fits specific project constraints, such as uncertainty level, requirement stability, or deliverable complexity. PMI tests your ability to match development approaches to project characteristics, not just memorize definitions—expect 2-3 questions on tailoring and approach selection.

Key Points to Remember (for the exam)

• Three Primary Approaches: Predictive (waterfall), Adaptive (agile), and Hybrid (combination of both)
• Predictive is for: Stable requirements, well-understood deliverables, low uncertainty, sequential phases
• Adaptive is for: Evolving requirements, high uncertainty, incremental delivery, customer collaboration
• Hybrid is for: Projects needing structure with flexibility, combining predictive planning with adaptive execution
• Selection Factors: Deliverables (complexity, modularity), Project (risk, uncertainty, size), Organization (culture, capability, readiness)
• Tailoring Process: Select initial approach first, then tailor for the organization (Section 3.4.1 → 3.4.2)
• Common Confusion: Hybrid is NOT "bad agile"—it is a deliberate combination chosen for specific project needs

Typical PMI Exam Example

A project involves developing a medical device with regulatory requirements (stable scope) but also requires iterative user interface testing (evolving needs). The project manager should select a Hybrid approach: predictive for regulatory compliance deliverables, adaptive for UI components.

PMI Exam Traps

• Trap: Thinking predictive is always "old" and adaptive is always "better"
  • Reality: Each approach is valid; selection depends on project characteristics, not trends
• Trap: Confusing Hybrid with "using agile tools in a predictive project"
  • Reality: Hybrid is a deliberate combination of predictive and adaptive phases, not random tool usage
• Trap: Assuming adaptive means no planning
  • Reality: Adaptive approaches have planning, but planning is iterative and progressive
• Trap: Selecting adaptive for regulatory projects automatically
  • Reality: Regulatory projects often require predictive for documentation and compliance

Important PMI Connections

Quick Review Questions

1. A project has highly uncertain requirements and needs frequent customer feedback. Which development approach is most appropriate?

2. What are the three main categories of factors to consider when selecting a development approach?

3. A project requires regulatory approval documentation but also has evolving user experience features. Which approach should the project manager select?

4. What is the first step in the tailoring process according to PMBOK v8?

5. Why might a project with stable requirements and low uncertainty NOT be suitable for an adaptive approach?

PMBOK v8 Reference

Section 3.4 - The Tailoring Process (specifically 3.4.1 "Select Initial Development Approach") Section 4.3 - Considerations for a Development Approach Selection