CAPM Practice: Explain when it is appropriate to use an adaptive approach
Question 34 of 61 in Explain when it is appropriate to use an adaptive approach
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Deliver value in frequent, small increments throughout the project rather than only at the end
Explanation
A key differentiator of adaptive approaches is continuous value delivery. Stakeholders receive working, usable increments throughout the project — not just at the final delivery. This early value delivery allows for earlier return on investment and reduces the risk of late-discovered misalignment with requirements.
**Why not A:** Adaptive projects still produce documentation, such as product backlogs, user stories, and definitions of done. Adaptive approaches favor just-enough documentation that supports delivering value, but they do not eliminate documentation altogether.
**Why not C:** Adaptive approaches are not guaranteed to cost less than predictive approaches for the same scope. Cost depends on the project context, and frequent iteration and feedback can add effort. The benefit of an adaptive approach is earlier value delivery and lower risk of misalignment, not a guaranteed lower cost.
**Why not D:** Adaptive projects can and often do have defined end dates and release milestones. Many adaptive projects fix time and cost through timeboxes and let scope vary. Having no defined end is not what distinguishes adaptive approaches from predictive ones.
Key Concept
This question covers Explain when it is appropriate to use an adaptive approach under Explain when it is appropriate to use an adaptive approach (Agile Frameworks/Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free