PMI-ACP · Question #333
Suppose the current release will be complete after 6 two-week iterations. A team member is insisting that the Product Owner write the acceptance test cases for the entire release. How should the…
The correct answer is C. Explain that stories should only be discussed in detail prior to development. Elaborating stories. The Scrum Master should explain that stories should only be elaborated just-in-time, immediately prior to development. Writing detailed acceptance tests for all stories across 12 weeks violates the Agile principle of responding to change over following a plan - requirements…
Question
Suppose the current release will be complete after 6 two-week iterations. A team member is insisting that the Product Owner write the acceptance test cases for the entire release. How should the Scrum Master respond?
Options
- ASince the release duration is not very long, agree with the idea and explain the advantage of
- BIt's up to the team and Product Owner to determine if it is a good idea.
- CExplain that stories should only be discussed in detail prior to development. Elaborating stories
- DDecide to dedicate first Sprint to elaborating all the stories
How the community answered
(49 responses)- A10% (5)
- B6% (3)
- C80% (39)
- D4% (2)
Explanation
The Scrum Master should explain that stories should only be elaborated just-in-time, immediately prior to development. Writing detailed acceptance tests for all stories across 12 weeks violates the Agile principle of responding to change over following a plan - requirements discovered later may make early test cases obsolete or misleading. This is also known as 'last responsible moment' planning. Agreeing upfront (A) creates waste, deferring to the team alone (B) avoids the Scrum Master's coaching role, and dedicating a full sprint to elaboration (D) is a classic 'Sprint 0' anti-pattern.
Topics
Community Discussion
No community discussion yet for this question.