Adaptive Approaches: Evolving Scope, High Uncertainty, and Incremental Delivery

PMBOK v8 Definition

Adaptive approaches, also referred to as change-driven or agile approaches, are useful when a project's requirements and technical solution are subject to a high level of uncertainty and volatility and are likely to change significantly throughout the project. A clear vision is established at the start of the project, and the initial known requirements are progressively elaborated, changed, or replaced in accordance with stakeholder feedback, the environment, or unexpected events. Adaptive approaches can be both iterative and incremental.

Why It Matters for the Exam

This concept frequently appears in PMI exam questions about development approach selection, particularly in situational questions where you must determine whether a predictive, adaptive, or hybrid approach is appropriate. Expect scenario-based questions describing project characteristics (evolving scope, high uncertainty, need for early delivery) where you must identify adaptive approaches as the optimal choice.

Key Points to Remember (for the exam)

• Primary Trigger: Adaptive approaches are optimal when requirements and technical solutions have high uncertainty and volatility
• Core Characteristics: Evolving scope, progressive elaboration, stakeholder feedback integration, change-driven
• Delivery Pattern: Both iterative AND incremental delivery of value
• Key Differentiator: Requirements are expected to change, NOT remain stable
• Common Confusion: Adaptive does NOT mean "no planning" – it means planning is continuous and responsive
• Typical Candidates: Software projects (new mobile apps, web services), digital projects, innovative products
• Selection Criteria: High degree of innovation + low requirements certainty + unstable scope = adaptive approach

Typical PMI Exam Example

A project manager is assigned to develop a new mobile application for a startup. The market requirements are expected to change rapidly based on user feedback, and the client needs an early working version within three months. The team is uncertain about several technical features. Which development approach is most appropriate? → Adaptive approach, because the project has evolving scope, high uncertainty, and need for incremental delivery.

PMI Exam Traps

• Trap: Confusing adaptive with "no documentation" or "unstructured work"

  • Reality: Adaptive approaches have clear vision, defined processes, and continuous planning

• Trap: Thinking all software projects require adaptive approaches

  • Reality: PMBOK v8 explicitly states "not all software development projects require an adaptive approach" – only those with evolving scope, high uncertainty, and need for incremental delivery

• Trap: Believing adaptive and predictive are mutually exclusive

  • Reality: Most projects today use hybrid approaches combining elements of both

• Trap: Assuming adaptive means no change control

  • Reality: Adaptive approaches embrace change through continuous stakeholder feedback and progressive elaboration

Important PMI Connections

Quick Review Questions

1. A project has well-known requirements, stable scope, and significant regulatory oversight. Which development approach is optimal?

2. What are the three project characteristics that make a software project a strong candidate for adaptive approaches?

3. Can adaptive approaches be used for non-software projects? (Hint: Consider the "digital projects" reference)

4. What is the relationship between adaptive approaches and progressive elaboration?

5. A project requires early delivery of a basic version, with features added based on user feedback. Is this iterative, incremental, or both?

PMBOK v8 Reference

Section 4.2.2 - Adaptive Approaches Section 4.2.1 - Predictive Approaches (for contrast) Section 4.3.1 - Deliverables (for selection variables)