Practice vocabulary for estimation calibration including velocity tracking, over-optimism, comparing estimates to actuals, and retrospective analysis of accuracy.
0 / 5 completed
1 / 5
When a team's sprint velocity closely matches its committed capacity sprint after sprint, we say the velocity _____.
Velocity tracking capacity closely indicates a well-calibrated team — their estimates match their actual throughput, making planning reliable.
2 / 5
A team that consistently commits to 40 points but only completes 32 is said to be _____.
Over-optimism in estimation means the team systematically commits to more work than they can deliver, often due to not accounting for interruptions, bugs, or complexity.
3 / 5
If historical data shows that estimates are consistently 30% lower than actual time spent, the team should _____.
A systematic bias of 30% off means estimates need a calibration correction. Teams should also investigate causes (underestimated complexity, interruptions) to improve future accuracy.
4 / 5
'Calibration' in the context of software estimation means _____.
Calibration is the practice of comparing estimates to actual outcomes, then adjusting estimation habits or correction factors to reduce systematic bias over time.
5 / 5
Which agile ceremony is the most appropriate place to discuss estimation accuracy and calibrate future estimates?
The retrospective is the dedicated ceremony for reflecting on process, including estimation accuracy — teams can discuss why estimates were off and agree on improvements.