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
In the INVEST mnemonic for good user stories, what does the 'N' stand for?
Answer: Negotiable
INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable.
A team estimates a story they have never done before and has no comparable past work. Which technique best handles this uncertainty?
Answer: A spike to gather information first
A spike is a time-boxed research task used to reduce uncertainty before estimating.
What is the primary purpose of relative estimation with story points rather than absolute time?
Answer: It compares sizes without forcing precise time commitments
Relative estimation focuses on comparative effort and complexity, avoiding false precision of time estimates.
During Planning Poker, two team members reveal very different estimates. What should happen next?
Answer: The high and low estimators explain their reasoning, then re-vote
Discussion of differing views surfaces hidden assumptions before re-estimating.
Which item is typically NOT written as a user story?
Answer: A technical infrastructure or non-functional requirement
Purely technical or non-functional work is often captured as enablers or technical tasks rather than user stories.
What does a story being 'Estimable' (the E in INVEST) require?
Answer: The team understands it well enough to size it
Estimable means there is enough clarity for the team to assign a reasonable size.
Why are Fibonacci-like sequences (1, 2, 3, 5, 8, 13) commonly used for story points?
Answer: Larger items carry more uncertainty, so gaps widen
The widening gaps reflect growing uncertainty as items get bigger.