CAPM Practice: Explain when it is appropriate to use an adaptive approach
Question 5 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: Adaptive — develop iteratively, using user feedback from each iteration to refine the next
Explanation
When the product vision is known but specific requirements will emerge through user feedback and prototype testing, an adaptive approach is ideal. Each iteration delivers a working increment, gathers user feedback, and incorporates that learning into the next iteration. This deliberate discovery process is more effective than attempting to specify requirements upfront when the knowledge doesn't yet exist.
**Why not A:** Hiring a business analyst does not solve the underlying problem — the requirements cannot be fully known yet because the product manager expects to learn them as users interact with prototypes. No amount of upfront analysis can capture knowledge that will only emerge through user feedback.
**Why not B:** Cancelling the project is unnecessary. Uncertain requirements are not a reason to stop work; they are a signal to choose an approach designed for discovery. An adaptive approach allows the team to deliver value while the requirements are clarified.
**Why not D:** A comprehensive upfront specification assumes requirements are known and stable. Here the product manager expects to learn as users interact with prototypes, so a detailed specification would be based on guesses and would likely lead to significant rework.
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