Velocity
Agile metric measuring the amount of work a team can complete during a sprint, essential for planning and predictability.
Updated on February 21, 2026
Velocity is a fundamental metric in Agile project management that quantifies a team's productive capacity during a sprint. It represents the sum of effort points (story points) or completed tasks during an iteration, enabling teams to forecast their future capacity and improve planning. This measurement becomes a strategic indicator for establishing realistic commitments and optimizing value delivery.
Fundamentals of Velocity
- Empirical measure based on the team's actual past performance
- Calculated only on fully completed user stories (Definition of Done met)
- Expressed in story points, ideal hours, or number of features depending on the estimation system chosen
- Team-specific and not comparable between different teams
Benefits of Velocity
- Increased predictability: enables accurate estimation of future feature delivery timelines
- Realistic planning: helps Product Owners prioritize the backlog based on actual capacity
- Early problem detection: significant variations signal impediments or team changes
- Transparent communication: facilitates discussions with stakeholders about capabilities and commitments
- Continuous improvement: provides concrete data for retrospectives and process optimization
Practical Calculation Example
Consider a Scrum team over three consecutive two-week sprints:
- Sprint 1: 23 story points completed
- Sprint 2: 27 story points completed
- Sprint 3: 25 story points completed
- Average velocity: (23 + 27 + 25) / 3 = 25 points per sprint
With this average velocity of 25 points, if the prioritized backlog contains 150 points of remaining features, the team can estimate needing approximately 6 sprints (12 weeks) to deliver them, enabling reliable release planning.
Implementation Steps
- Establish a consistent estimation system (story points, T-shirt sizing, etc.) during backlog refinement
- Count only fully completed user stories according to Definition of Done during sprint review
- Record velocity at the end of each sprint in a dashboard or management tool
- Calculate average velocity over the last 3-5 sprints to smooth variations
- Use this average to plan upcoming sprint content during sprint planning
- Analyze significant deviations in retrospectives to identify causes and improvement opportunities
- Adjust forecasts for major changes (new member, departure, technological shift)
Professional Tip
Never turn velocity into an individual performance indicator or comparison tool between teams. This metric must remain a planning guide, not a goal to maximize. Artificially inflating estimates to 'improve' velocity destroys all its predictive value. Focus instead on stability and consistency in your estimations.
Related Tools and Practices
- Jira, Azure DevOps: automatic velocity calculation and evolution charts (velocity charts)
- Planning Poker: collaborative estimation technique for assigning story points
- Burndown/Burnup charts: complementary visualizations using velocity to project progress
- Monte Carlo simulations: advanced probabilistic methods based on velocity history
- Cumulative Flow Diagrams: workflow analysis related to delivery capacity
Velocity constitutes much more than a simple metric: it transforms the uncertainty inherent in software development into actionable predictability. By anchoring planning in the measured reality of past performance rather than theoretical estimates, it enables organizations to establish reliable roadmaps, optimize resource allocation, and strengthen stakeholder trust. A well-understood and properly used velocity becomes the foundation of mature agility and continuous value delivery.
