Velocity
Velocity is the amount of work a Scrum team completes in a Sprint, typically measured in story points, used to forecast how much work the team can handle in future sprints.
Explanation
Velocity is calculated by summing the story points of all Product Backlog items that meet the Definition of Done at the end of a Sprint. It is a trailing indicator, meaning it reflects past performance. Over several sprints, velocity stabilizes and becomes a useful planning tool for forecasting how much work the team can take on.
Velocity is unique to each team and should never be used to compare teams or as a performance metric for individual team members. Its sole purpose is to help the team and Product Owner plan sprints and releases. Using velocity as a performance measure creates perverse incentives, such as inflating estimates.
A team's average velocity over the last three to five sprints is typically used for release planning. By dividing the total remaining story points in the backlog by the average velocity, the team can forecast how many sprints are needed to complete the remaining work.
Key Points
- •Measured in story points completed per Sprint
- •Based on work that meets the Definition of Done
- •Used for forecasting, not for comparing teams or measuring individual performance
- •Average of three to five sprints provides the most reliable forecast
Exam Tip
Velocity is a planning tool, not a performance measure. Exam answers that use velocity to compare teams or pressure individuals are incorrect.
Frequently Asked Questions
Related Topics
Story Points
Story points are a unit of measure for expressing the overall effort, complexity, and uncertainty involved in completing a Product Backlog item, used for relative estimation rather than measuring time.
Sprint Planning
Sprint Planning is the Scrum event that initiates each Sprint by defining the Sprint Goal, selecting Product Backlog items to work on, and creating an actionable plan for delivering the Increment.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Release Planning
Release Planning is an agile practice where the team and Product Owner determine the scope, timing, and goals for the next product release by mapping backlog items across future iterations based on team velocity.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.