HKSM
Sprint Velocity
The typical amount of work a team finishes in a sprint, expressed in the same units used for estimation, such as story points or ideal time.
Key Points
- Velocity counts only work that meets the Definition of Done at the end of the sprint.
- It is measured in consistent estimation units (e.g., story points or ideal time) and often averaged across recent sprints for forecasting.
- Velocity is not a productivity KPI and should not be used to compare different teams.
- Capacity changes, scope clarity, and team stability influence velocity; adjust forecasts for holidays, new members, or disruptions.
Example
Across the last three sprints the team completed 24, 20, and 22 story points. Their average velocity is about 22 points per sprint. With a backlog of 110 points, the release is forecast to take roughly 5 sprints (110 / 22).
PMP Example Question
A Scrum team has an average velocity of 30 story points. The product backlog for the next release totals 150 story points. What is the best forecast for the number of sprints needed, assuming stable capacity?
- 5 sprints, based on the current average velocity
- 4 sprints, if the team works overtime
- 3 sprints, because velocity should increase each sprint
- Cannot estimate until tasks are broken into hours
Correct Answer: A — 5 sprints, based on the current average velocity
Explanation: Velocity is used for empirical forecasting. Dividing 150 by the average velocity of 30 yields an estimate of 5 sprints, assuming conditions remain similar.
