PMI-ACP · Question #52
When are acceptance tests typically written for a user story?
The correct answer is C. At the start of Product Backlog prioritization planning. The answer given is C - acceptance tests should be written at the start of Product Backlog prioritization planning, meaning when the story is first being defined and added to the backlog. Defining acceptance criteria this early ensures the team understands what 'done' looks like
Question
When are acceptance tests typically written for a user story?
Options
- AAfter coding the story, but before user acceptance testing begins
- BAfter writing the story, but before coding begins
- CAt the start of Product Backlog prioritization planning
- DAfter estimating the Product Backlog, but before Sprint planning begins
How the community answered
(48 responses)- A4% (2)
- C94% (45)
- D2% (1)
Explanation
The answer given is C - acceptance tests should be written at the start of Product Backlog prioritization planning, meaning when the story is first being defined and added to the backlog. Defining acceptance criteria this early ensures the team understands what 'done' looks like before any estimation or coding begins. Note that option B (after writing the story, before coding) is also a widely accepted Agile and ATDD/BDD practice and is arguably the more precise answer. Writing acceptance tests after coding (A) or after estimation (D) is too late to drive design or verify intent.
Topics
Community Discussion
No community discussion yet for this question.