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
What distinguishes a 'task' from a 'user story' in most Agile frameworks?
Answer: A task is a technical step toward completing a story
Tasks are the implementation steps the team breaks a story into during sprint planning.
Which of these is a key sign a story is NOT 'Independent'?
Answer: It cannot be completed without another story finishing first
Independence means a story can be developed and delivered without tight dependencies.
What is the main risk of estimating user stories in precise hours rather than relative points?
Answer: It implies false precision and invites unrealistic commitments
Hour estimates suggest a precision that rarely holds, encouraging over-commitment.
In Planning Poker, what does it usually mean when an estimator plays the '?' card?
Answer: They lack enough information to estimate
The '?' card signals the story needs more clarity before it can be sized.
What is the benefit of keeping user stories small?
Answer: Faster feedback, easier estimation, and smoother flow
Small stories are easier to estimate, complete, and validate quickly.
A backlog item reads 'Make the app better.' Why is this a poor user story?
Answer: It is vague, not testable, and lacks clear value or criteria
The item lacks a defined user, goal, benefit, and any way to verify completion.
How should a Definition of Ready differ from acceptance criteria?
Answer: Definition of Ready gates whether a story can enter a sprint; acceptance criteria define when it is done
Definition of Ready ensures a story is well-formed before work starts; acceptance criteria confirm completion.