Adaptive Approaches: Iterative and Incremental 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: the iterative approach focuses on refining and improving the project through repeated cycles (iterations), while the incremental approach delivers the final product in small, usable segments (increments), where each increment provides value and builds on one another until the complete product is delivered.
Why It Matters for the Exam
This concept appears frequently in situational questions where the PMI exam tests your ability to distinguish between development approaches and select the correct life cycle for a given project scenario. Expect questions that ask you to identify when an adaptive approach is appropriate, differentiate between iterative and incremental methods, or recognize how adaptive approaches interact with Focus Areas across the project life cycle.
Key Points to Remember (for the exam)
- Primary Trigger: Adaptive approaches are selected when requirements and technical solutions have high uncertainty and volatility throughout the project
- Core Mechanism: Initial known requirements are progressively elaborated, changed, or replaced based on stakeholder feedback, environment, or unexpected events
- Iterative vs. Incremental: Iterative = refining through repeated cycles (improving quality); Incremental = delivering in small usable segments (building functionality)
- Iteration Duration: Agile iterations are generally 1 to 4 weeks in duration, with a demonstration of accomplishments at the end of each iteration
- Focus Areas Interaction: In adaptive approaches, Focus Areas (Initiating, Planning, Executing, Monitoring and Controlling, Closing) are not linear or sequential—they interact within short iterations in a flexible, overlapping manner
- Scheduling Characteristic: In adaptive projects, schedules are more flexible; the project is divided into sprints or iterations with short-term planning horizons
- Single Team vs. Larger Scale: PMBOK v8 distinguishes between agile methods designed for a single team versus those designed for larger-scale purposes
Typical PMI Exam Example
A software development project faces rapidly changing customer requirements and emerging technologies. The project manager establishes a clear product vision but expects requirements to evolve. The team delivers working features every two weeks and demonstrates accomplishments at each iteration's end. Which development approach is being used? → Adaptive approach, specifically iterative and incremental, with 2-week iterations.
PMI Exam Traps
-
Trap: Confusing "adaptive approach" with "no planning at all"
- Reality: Adaptive approaches establish a clear vision at the start; planning is continuous and occurs within each iteration, not absent
-
Trap: Thinking iterative and incremental are the same concept
- Reality: Iterative = refinement through repeated cycles (improving what exists); Incremental = delivering small usable pieces that build on each other (adding new functionality)
-
Trap: Assuming adaptive approaches follow a linear sequence of Focus Areas
- Reality: In adaptive development, Focus Areas interact within short iterations in a flexible and overlapping manner, revisited regularly throughout the project
-
Trap: Believing adaptive methods are only for software projects
- Reality: PMBOK v8 describes adaptive approaches as applicable to any project with high uncertainty and volatility, not limited to software development
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Predictive Approach | Opposes | Adaptive = flexible scope, flexible schedule; Predictive = fixed scope, fixed schedule. Know when each is appropriate based on uncertainty level |
| Hybrid Life Cycle | Complements | Hybrid combines adaptive flexibility with predictive structured planning. High-level milestones use predictive techniques; subordinate streams can use adaptive or predictive methods |
| Tailoring | Applied to | In adaptive projects, tailoring involves creating timeboxed schedules that can adapt to changes in project scope and priorities |
| Focus Areas (Initiating, Planning, Executing, Monitoring & Controlling, Closing) | Interaction Pattern | In adaptive approaches, these are not performed all at once but interact within iterations for continuous refinement based on real-time data and feedback |
Quick Review Questions
-
What are the two key characteristics that make a project suitable for an adaptive approach according to PMBOK v8?
-
A project team delivers a complete login feature in the first iteration, then adds payment processing in the second iteration. Is this iterative, incremental, or both? Explain.
-
How do Focus Areas (Initiating, Planning, Executing, Monitoring and Controlling, Closing) differ in their interaction pattern between adaptive and predictive approaches?
-
What is the typical duration range for iterations in agile methods, and what event occurs at the end of each iteration?
-
A project has high-level milestones planned predictively, but subordinate streams use adaptive methods. What development approach is this?
PMBOK v8 Reference
Section 4.2.2 – Adaptive Approaches (The Standard for Project Management)