Sprint Velocity Tracker
Track completed story points, see your average and rolling velocity, spot the trend, and forecast the next sprint - right in your browser.
Completed story points per sprint
Sample data below is an editable estimate - replace it with your own.
Velocity chart
Results
- Average velocity
- 25.6 pts
- Rolling 3-sprint avg
- 27 pts
- Trend
- ↑ Rising
- Next-sprint forecast
- 22.3-28.9 pts
Forecast = average ± one standard deviation. A wider band means less predictable velocity.
Copy summary
Paste the results into a retro doc, sprint plan, or Slack thread.
Velocity is a planning aid, not a target to game. It helps you size the next sprint and watch for drift - it is not a productivity score. When it becomes a goal, points inflate and the number stops meaning anything.
Understanding sprint velocity
Velocity is one of the oldest planning signals in agile teams: sum the story points completed each sprint and watch the average over time. Used well, it answers a practical question - "roughly how much can we commit to next sprint?" - without pretending to be a measure of individual effort or code quality.
The trend matters more than any single number. A steadily rising or flat velocity usually signals a healthy, predictable team. A declining line is worth a conversation - but the cause could be scope creep, unplanned incidents, or estimation drift rather than a slowdown. Pair velocity with flow metrics like cycle time and the broader DORA metrics to see the whole picture.
Because points are estimates, velocity is directional, not exact - which is exactly why forecasting with a range (average ± standard deviation) beats a single hardcoded target. If you want to go deeper on measuring output honestly, see our guide on how to measure developer productivity.