Study guides / CAPM: Certified Associate in Project Management / When to use an adaptive approach
When to use an adaptive approach
CAPM: Certified Associate in Project Management · quick review
When iterative, incremental agile delivery fits, and the values and principles behind it.
The rules
- Adaptive fits high uncertainty: requirements that will emerge, fast-changing markets, the need for early and frequent feedback, and a customer who can engage often.
- The Agile Manifesto values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan (while still valuing the items on the right).
- Its principles include early and continuous delivery of value, welcoming changing requirements, delivering frequently, daily collaboration with the business, sustainable pace, simplicity and regular reflection.
- Adaptive work delivers in short iterations (timeboxes), producing a usable increment each time.
- Teams are small, cross-functional and self-managing; the leader serves rather than commands.
Common traps
- Agile still plans; it plans continuously in smaller pieces.
- "Over" in the Manifesto doesn't mean "instead of": documentation and plans still have value.
How it's tested
Choosing adaptive over predictive for a scenario, and recognizing the Manifesto's values and principles.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson