Velocity Calculator
Calculate and analyze your Scrum team's velocity with story points. Predict backlog completion and improve sprint planning accuracy.
Last updated:
How to Use
Expand how to useCollapse how to use
- 1
Enter sprint results
Click 'Add Sprint' and enter the completed story points for each sprint
- 2
Check velocity
Analyze your team's performance through average velocity, trend, and charts
- 3
Predict backlog completion
Enter remaining backlog SP to predict the number of sprints until completion
Sprint Results
Velocity Statistics
Average Velocity
31.7 SP
Trend
Stable
Min
28
Max
35
Std Dev
2.9
Velocity Trend
| Sprint Name | Completed SP |
|---|---|
| Sprint 1 | 32 |
| Sprint 2 | 28 |
| Sprint 3 | 35 |
Backlog Completion Prediction
Please enter remaining backlog SP
What is Velocity Calculator?
Velocity Calculator is an online tool that calculates and analyzes a Scrum team's velocity (completed story points per sprint). It calculates average velocity, trends, and standard deviation from past sprint results, and predicts the number of sprints needed to complete remaining backlog. Useful for understanding team performance and improving sprint planning accuracy.
Key Features
- Enter sprint results to automatically calculate velocity
- Switch calculation scope between all sprints, last 3, or last 5
- Display statistics including average, min, max, and standard deviation
- Trend analysis showing increasing, decreasing, or stable patterns
- Predict sprint count from remaining backlog SP
Use Cases
- Estimating how many story points the team can commit to in the next sprint
- Predicting how many sprints remain to clear the backlog for a release date
- Sharing delivery forecasts with stakeholders or the Product Owner
- Visualizing velocity trends to spot improvements or regressions over time
- Evaluating team stability with standard deviation — high variance signals planning issues
- Calibrating sprint commitment after team size changes or onboarding new members
Frequently Asked Questions
What is velocity?
Velocity is a metric that represents the amount of story points a Scrum team can complete in one sprint. It's used as a measure of team productivity and for future sprint planning and predictions.
Why is the last 3 sprints the default?
The average of the last 3 sprints is considered to have the highest prediction accuracy as it reflects the team's latest performance. It has the advantage of quickly reflecting changes in team composition and environment.
How accurate are the predictions?
Predictions are estimates based on past velocity. They may vary depending on team stability and external factors. Use prediction values as guidelines and regularly compare with actual results to adjust.
How are trends ('Increasing', 'Decreasing', 'Stable') determined?
By comparing recent sprint results, if velocity is continuously increasing it's 'Increasing', if decreasing it's 'Decreasing', and if variation is low it's determined as 'Stable'.
Where is the data stored?
Data is only kept during your browser session. It resets on page reload, so please save your data using the CSV export feature.
What should I do if my velocity fluctuates significantly?
Velocity fluctuations are often caused by scope changes, team member absences, or technical blockers. Accumulate data from 3-5 sprints and check the standard deviation to understand stability. This tool automatically calculates standard deviation and visualizes the degree of variation.
How do I use velocity in sprint planning?
Use the average velocity from past sprints as a baseline for how many story points your team can complete in the next sprint. For example, if your average velocity is 20 SP, plan approximately 20 SP worth of backlog items.
What is the difference between velocity and capacity?
Velocity is a historical metric (actual completed SP), while capacity is a planning metric calculated from available team hours. Velocity shows team capability; capacity shows resource constraints. Ideally, consider both when planning sprints.
Should I reset velocity when team members change?
Yes, for significant changes, resetting is recommended. Velocity is team-specific, and past data becomes unreliable when composition changes substantially. Collect about 3 sprints of data with the new team before recalculating.
What is a good velocity number?
There is no universally good or bad velocity. Since story point scales differ between teams, cross-team comparisons are meaningless. What matters is whether your team's velocity is stable and predictable over time.