User Stories and Estimation Flashcards
7 cards from real Agile Project Management 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 Stories and Estimation flashcards as text
A user story has acceptance criteria but no clear value to the user. Which INVEST trait is most violated?
Answer: Valuable
Every user story should deliver clear value to a user or customer.
What is the recommended response when a single user story is too large to complete in one sprint?
Answer: Split it into smaller vertical slices
Large stories (epics) should be split into smaller, independently valuable slices.
In the standard user story template, what is the typical format?
Answer: As a [role], I want [goal], so that [benefit]
The 'As a... I want... so that...' format captures role, goal, and benefit.
What is the main role of acceptance criteria attached to a user story?
Answer: Define the conditions that make the story complete and testable
Acceptance criteria specify the boundaries and pass/fail conditions for the story.
A team's velocity has been 30, 32, and 28 points over three sprints. What is the most reasonable forecast for the next sprint?
Answer: Around 30 points based on the average
Average historical velocity gives a reasonable, sustainable forecast.
What does the 'so that' clause in a user story primarily communicate?
Answer: The benefit or reason behind the request
The 'so that' clause expresses the value or motivation for the story.
Which approach helps a new team estimate when they have no velocity history yet?
Answer: Pick a reference story as a baseline and estimate others relative to it
Anchoring to a known reference story enables consistent relative estimation from the start.