User Story Development & Refinement Flashcards
7 cards from real CAE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 User Story Development & Refinement flashcards as text
Which story-splitting technique divides a story based on the type of data being processed?
Answer: Split by data variations
Splitting by data variations creates separate stories for different data types or inputs, such as handling domestic vs. international addresses.
A product owner wants to write acceptance criteria using Given-When-Then format. What is the 'When' clause used for?
Answer: Specifying the action or event that triggers the behavior
In Given-When-Then, the 'When' clause captures the specific action, event, or trigger that the acceptance criterion is testing.
A scrum team repeatedly discovers new acceptance criteria for stories during the sprint. What refinement practice would reduce this?
Answer: Invest more time in pre-sprint backlog refinement sessions
Thorough pre-sprint refinement reduces mid-sprint surprises by flushing out hidden requirements before the team commits to a story.
Which of the following is an example of a non-functional requirement that should be captured in a user story's acceptance criteria?
Answer: The page must load within two seconds on a 4G connection
Performance constraints like load time are non-functional requirements (quality attributes) that must appear in acceptance criteria to be testable.
What is the recommended frequency for backlog refinement in Scrum?
Answer: Continuously throughout the sprint, totaling no more than 10% of the team's capacity
Scrum recommends ongoing refinement throughout the sprint with a guideline of spending no more than 10% of team capacity on it.
A story passes all acceptance criteria in a demo but the product owner is dissatisfied. What most likely went wrong?
Answer: The acceptance criteria did not fully capture the product owner's intent
Acceptance criteria that pass mechanically yet fail to satisfy intent indicate a gap between what was written and the product owner's underlying expectation.
When using the '5 Whys' technique during story refinement, what is the team trying to uncover?
Answer: The root cause or true business need behind a requested feature
The 5 Whys helps teams dig past surface-level feature requests to discover the genuine business problem or goal the story should solve.