CAPM Practice: Explain when it is appropriate to use an adaptive approach
Question 31 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: Conflicts with the fundamental adaptive principle of responding to change, though sprint-level stability is normal
Explanation
Sprint-level stability (not changing the sprint goal or sprint backlog during an active sprint) IS an adaptive best practice — it protects the team's focus. But management saying 'no requirements can change ever' misunderstands adaptive principles. Between sprints, requirements CAN and SHOULD change based on feedback. The sprint provides a short window of stability while the overall product direction remains adaptable.
**Why not B:** The Agile Manifesto does not require freezing requirements. It values responding to change over following a plan and welcomes changing requirements, even late in development.
**Why not C:** The directive reflects a management misunderstanding that should be corrected, not a reason to abandon the adaptive approach. Switching to a predictive approach would discard the feedback-driven change the project needs.
**Why not D:** Honoring sprint commitments is normal, but this directive freezes requirements for the rest of the project, not just within a single sprint. That prevents the backlog from evolving between sprints based on feedback.
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