During sprint planning for the Aurora billing team, a manager states that the team's velocity of 30 points should be treated as a performance goal that each developer must be pushed to exceed every sprint. How should velocity actually be understood?
- AAs a target that management sets in advance, so the team is accountable for hitting a rising point figure sprint after sprint.
- BAs a productivity benchmark for comparing this team against other teams that estimate in their own points.
- CAs a quality metric that shows how many defects the team removed during the sprint just completed.
- DAs an empirical measure of how many story points the team has historically completed, used to forecast how much work fits in future sprints. Correct
Why A is wrong: This is the classic misuse; treating velocity as a target invites point inflation and gaming, which corrupts the very measure used to plan future sprints.
Why B is wrong: This is tempting but wrong because points are calibrated per team, so one team's velocity is meaningless when set beside another team's differently sized points.
Why C is wrong: This confuses velocity with a defect measure; velocity counts completed story points of delivered work and says nothing directly about defect counts.
Why D is correct: Correct. Velocity is an observed capacity figure derived from completed work, and its legitimate use is forecasting realistic sprint scope, not driving people to a quota.