7.1 When to Use an Adaptive (Agile) Approach
Key Takeaways
- Adaptive approaches work best when requirements are uncertain, evolving, or poorly understood at the start of the project
- Agile is rooted in the Agile Manifesto which values individuals and interactions, working software, customer collaboration, and responding to change
- The 12 Agile Principles guide agile practices including early and continuous delivery, welcoming changing requirements, and frequent delivery of working product
- Hybrid approaches combine predictive and adaptive elements — for example, using waterfall planning at the phase level with agile execution within sprints
- Key indicators for agile include high uncertainty, volatile requirements, need for frequent feedback, and empowered self-organizing teams
Last updated: March 2026
When to Use an Adaptive (Agile) Approach
The CAPM exam dedicates 20% of questions to Agile Frameworks/Methodologies. This section covers Domain 3, Task 1: knowing when to use an adaptive approach.
The Agile Manifesto
The Agile Manifesto (2001) defines four core values that underpin all agile methodologies:
| We Value... | Over... |
|---|---|
| Individuals and interactions | Processes and tools |
| Working software | Comprehensive documentation |
| Customer collaboration | Contract negotiation |
| Responding to change | Following a plan |
Key Nuance: "While there is value in the items on the right, we value the items on the left more." This does NOT mean documentation, processes, contracts, and plans have no value — they are simply less valued than the items on the left.
The 12 Agile Principles
- Satisfy the customer through early and continuous delivery of valuable product
- Welcome changing requirements, even late in development
- Deliver working product frequently (weeks rather than months)
- Business people and developers must work together daily
- Build projects around motivated individuals — give them the environment and support they need
- Face-to-face conversation is the most efficient communication method
- Working product is the primary measure of progress
- Agile processes promote sustainable development at a constant pace
- Continuous attention to technical excellence and good design
- Simplicity — the art of maximizing the amount of work not done
- The best architectures, requirements, and designs emerge from self-organizing teams
- Regular reflection and adjustment on how to become more effective
When Agile Is Appropriate
| Factor | Agile Is Appropriate When... |
|---|---|
| Requirements | Uncertain, evolving, or poorly defined at the start |
| Customer involvement | Customer/stakeholder is available for frequent feedback |
| Team | Small, cross-functional, collocated (or able to collaborate closely) |
| Organizational culture | Supports empowerment, experimentation, and learning from failure |
| Product | Can be delivered incrementally to provide early value |
| Market | Rapidly changing, requiring quick adaptation |
| Technology | New or uncertain, requiring experimentation |
Comparing Predictive and Adaptive Approaches
| Aspect | Predictive | Adaptive |
|---|---|---|
| Requirements | Fixed upfront | Evolving throughout |
| Delivery | Single delivery at end | Incremental/iterative |
| Planning | Comprehensive upfront | Just-in-time, progressive |
| Change | Controlled, expensive | Welcomed, expected |
| Feedback | At phase gates | Continuous (every iteration) |
| Documentation | Extensive | Minimal but sufficient |
| Team structure | Hierarchical, specialized | Self-organizing, cross-functional |
| Customer role | Defines requirements upfront | Active collaborator throughout |
| Success measure | Plan conformance | Value delivered |
Hybrid Approaches
Hybrid approaches combine elements of predictive and adaptive methodologies:
Common Hybrid Patterns
- Water-Scrum-Fall: Predictive planning and closing with agile execution
- Phase-based hybrid: Some phases are predictive, others are agile
- Feature-based hybrid: Well-understood features use predictive; uncertain features use agile
- Selective hybrid: Different teams use different approaches based on their work
When to Use Hybrid
- Parts of the project have stable requirements, other parts have evolving requirements
- The organization is transitioning from predictive to agile
- Regulatory requirements demand documentation while development benefits from agility
- Different teams have different levels of agile maturity
Organizational Considerations for Agile
| Enabler | Why It Matters |
|---|---|
| Executive support | Agile requires organizational commitment, not just team-level adoption |
| Empowered teams | Teams must have authority to make decisions about their work |
| Dedicated product owner | Someone must be available to prioritize and provide feedback |
| Cross-functional capability | Team needs all skills to deliver without external dependencies |
| Psychological safety | Team must feel safe to experiment, fail, and learn |
| Co-location or tools | Close collaboration is essential (physical or virtual) |
Test Your Knowledge
Which of the four Agile Manifesto values prioritizes working software over comprehensive documentation?
A
B
C
D
Test Your Knowledge
According to the Agile Principles, what is the PRIMARY measure of progress?
A
B
C
D
Test Your Knowledge
A project combines waterfall planning for the overall project phases with agile sprints for execution. This is an example of:
A
B
C
D
Test Your KnowledgeMulti-Select
Which of the following are values from the Agile Manifesto? (Select TWO)
Select all that apply
Comprehensive documentation over working software
Individuals and interactions over processes and tools
Following a plan over responding to change
Customer collaboration over contract negotiation
Processes and tools over individuals and interactions