ACP Agile Estimation and Sizing 1 — Questions and Answers
Question 1: Which estimation technique uses a modified Fibonacci sequence (1, 2, 3, 5, 8, 13, 20...) to size user stories?
- Bucket System
- Planning Poker (Correct answer)
- T-Shirt Sizing
- Affinity Mapping
Correct answer: Planning Poker
Planning Poker uses a modified Fibonacci sequence on cards so that larger numbers reflect greater uncertainty in large estimates.
Question 2: In agile estimation, what does a 'story point' primarily represent?
- Hours of work required
- Relative effort, complexity, and uncertainty (Correct answer)
- Number of tasks in a story
- Business value of the feature
Correct answer: Relative effort, complexity, and uncertainty
Story points are a relative measure of effort, complexity, and risk rather than an absolute time unit, allowing teams to estimate without time-boxing individuals.
Question 3: What is the primary benefit of using relative estimation over time-based estimation in agile?
- It provides exact delivery dates
- It eliminates the need for a product backlog
- It reduces anchoring bias and leverages team consensus (Correct answer)
- It requires no calibration with a baseline story
Correct answer: It reduces anchoring bias and leverages team consensus
Relative estimation reduces individual anchoring bias because team members compare stories to each other rather than estimating in hours, and consensus is reached collaboratively.
Question 4: A team uses a 'reference story' when doing story point estimation. What is the purpose of the reference story?
- To set the sprint goal
- To serve as a calibration baseline for sizing other stories (Correct answer)
- To document acceptance criteria
- To identify dependencies between stories
Correct answer: To serve as a calibration baseline for sizing other stories
A reference story is a previously completed story the team agrees represents a known size, used as an anchor to calibrate estimates for new stories.
Question 5: Which of the following best describes 'velocity' in an agile context?
- The number of defects fixed per sprint
- The average story points completed per iteration (Correct answer)
- The maximum story points a team can commit to
- The time taken to deliver a single story
Correct answer: The average story points completed per iteration
Velocity is the average number of story points a team completes per sprint, calculated over several sprints to enable reliable release forecasting.
Question 6: When a team discovers during sprint planning that a user story is too large to complete in one iteration, what is the recommended agile approach?
- Carry it over to the next sprint without changes
- Split it into smaller stories that each deliver value (Correct answer)
- Remove it from the backlog entirely
- Assign it to the most experienced developer
Correct answer: Split it into smaller stories that each deliver value
Stories too large for a single iteration (often called 'epics') should be split into smaller, independently deliverable stories that can each be completed within a sprint.
Question 7: In the Bucket System estimation technique, items are placed into buckets labeled 0, 1, 2, 3, 5, 8, 13, 20, 40, and 100. What makes this technique faster than Planning Poker for large backlogs?
- It uses exact hour estimates for each bucket
- Items are placed silently without discussion until outliers emerge (Correct answer)
- Only the product owner assigns bucket values
- It requires no calibration story
Correct answer: Items are placed silently without discussion until outliers emerge
The Bucket System speeds up large-backlog estimation by having participants silently place items into buckets and only discussing items where there is significant disagreement.
ACP Agile Estimation and Sizing 1
Which estimation technique uses a modified Fibonacci sequence (1, 2, 3, 5, 8, 13, 20...) to size user stories?