CAPM Practice: Explain when it is appropriate to use an adaptive approach
Question 10 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: Capture the feedback and incorporate it into the product backlog for prioritization in upcoming iterations
Explanation
In adaptive approaches, stakeholder feedback from sprint reviews is valuable information, not a problem. The feedback should be captured as backlog items, prioritized by the product owner, and incorporated into upcoming iterations. This is the intended feedback loop of adaptive methods — the review meeting specifically exists to gather this type of input.
**Why not A:** Treating sprint review feedback as formal change requests applies predictive change control to an adaptive process. The feedback belongs in the product backlog, where the product owner prioritizes it against other work — it is not automatically committed to the next sprint.
**Why not B:** Rejecting feedback because the work matched the original plan defeats the purpose of the sprint review. Adaptive approaches expect requirements to evolve as stakeholders see working software.
**Why not C:** Restarting the project is a drastic overreaction. The stakeholders said the increment is close, and the requested changes can be handled incrementally through the backlog in upcoming iterations.
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