What is Sprint Velocity?
The average number of story points a development team completes per sprint, used for capacity planning and release date forecasting in agile delivery.
Sprint Velocity is the average number of story points a development team completes per sprint. It is the primary metric used in Agile delivery for capacity planning, release date forecasting, and sprint commitment decisions. Velocity is not a measure of productivity or code quality - it is a forecasting tool that improves in accuracy as the team accumulates historical sprint data.
Formula
Velocity = Total Story Points Completed / Number of SprintsCalculate the average over the last 3-5 sprints for planning purposes. Example: Sprint 1 = 34 pts, Sprint 2 = 38 pts, Sprint 3 = 32 pts, Sprint 4 = 36 pts. Average Velocity = (34+38+32+36) / 4 = 35 points per sprint. Use this to forecast: if the backlog has 140 points, expect 4 sprints (8 weeks for 2-week sprints) to complete it.
Industry Benchmarks
- Velocity is team-specific and not comparable across different teams
- Stable velocity (within 10-15% variance) indicates predictable delivery
- Velocity declining over 3+ sprints signals a systemic impediment requiring investigation
- Teams typically need 4-6 sprints to establish a reliable baseline velocity
- Sprint commitment accuracy above 80% is a sign of good estimation calibration
When to Use Sprint Velocity
- Committing to a sprint backlog with confidence based on historical capacity
- Forecasting release dates for roadmap milestones based on remaining story points
- Identifying capacity changes when team members join, leave, or take planned time off
- Communicating delivery timeline uncertainty to stakeholders using velocity-based date ranges
- Using velocity as a performance benchmark to compare teams or pressure individuals to increase their numbers
- Including partial or incomplete stories in velocity calculations, which overstates actual throughput
- Setting velocity targets rather than letting it emerge naturally from consistent team composition and working practices
- Track velocity trend alongside story point distribution - a team that consistently completes many small stories but struggles with large ones may need to improve story refinement
- Use a velocity range (e.g. 30-40 points) rather than a single number when forecasting to communicate inherent uncertainty
- Re-baseline velocity deliberately after significant team changes rather than averaging historical data that no longer reflects current team composition
Related Terms
Free Sprint Velocity Calculator
Skip the spreadsheet. Enter your numbers in the free Velocity Calculator and get a benchmarked Sprint Velocity result in seconds.