Adaptive Approaches: Change-Driven and Agile Methods in Project Management

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 appears frequently in PMI exam questions about development approach selection, particularly in situations where requirements are uncertain or likely to change. You will encounter questions asking you to identify when an adaptive approach is appropriate versus predictive or hybrid approaches, and to distinguish between iterative and incremental delivery methods.

Key Points to Remember (for the exam)

• When to Use: Adaptive approaches are optimal when project requirements and technical solutions have high uncertainty and volatility, and are likely to change significantly throughout the project.
• Core Mechanism: Initial known requirements are progressively elaborated, changed, or replaced based on stakeholder feedback, environmental factors, or unexpected events.
• Iterative vs. Incremental: Iterative focuses on refining through repeated cycles (iterations); Incremental delivers the final product in small, usable segments (increments) that each provide value and build on one another.
• Typical Iteration Length: Agile iterations are generally 1 to 4 weeks in duration, with a demonstration of accomplishments at the end of each iteration.
• Common Confusion: Adaptive approaches are NOT the same as "no planning" – a clear vision is established at the start, and the approach is change-driven, not plan-driven.
• Key Differentiator: Unlike predictive approaches where scope is stabilized early, adaptive approaches embrace changing requirements as a natural part of the process.
• Applicable Projects: Software projects with evolving scope, high uncertainty, and need for early or incremental delivery; new product development where final features are refined based on market needs.

Typical PMI Exam Example

A software development team is building a new mobile app for a startup. The market demands are evolving rapidly, and the client cannot define all requirements upfront. The project manager recommends an adaptive approach because the requirements are subject to high uncertainty and volatility, and the product features will be refined based on stakeholder feedback and market needs throughout the project.

PMI Exam Traps

• Trap: Confusing adaptive approaches with "no planning" or "unstructured work"

  • Reality: Adaptive approaches establish a clear vision at the start and use progressive elaboration; they are structured but change-driven, not plan-driven.

• Trap: Thinking adaptive is only for software projects

  • Reality: While popular in software due to dynamic nature, adaptive approaches apply to any project with high uncertainty and evolving requirements, such as new product development.

• Trap: Confusing iterative with incremental delivery

  • Reality: Iterative = refining through repeated cycles; Incremental = delivering in small, usable segments that build on one another. They are distinct but can be combined.

• Trap: Assuming adaptive approaches cannot be used on large projects

  • Reality: Large projects with significant investment or regulatory oversight typically use predictive approaches, but adaptive can still be applied at component levels or in hybrid form.

Important PMI Connections

Quick Review Questions

1. In which project scenario is an adaptive approach most appropriate?
2. What is the difference between iterative and incremental delivery in adaptive approaches?
3. What is established at the start of a project using an adaptive approach before requirements are progressively elaborated?
4. How long are typical agile iterations, and what happens at the end of each iteration?
5. When would a predictive approach be preferred over an adaptive approach?

PMBOK v8 Reference

Section 4.2.2 – Adaptive Approaches