Team Velocity Tracker
Track and analyze team velocity across multiple sprints
Velocity normalized per available team-day, useful when days off vary between sprints.
Add sprints and a backlog size to forecast.
What is Team Velocity Tracker?
The Team Velocity Tracker is a free agile tool that measures how many story points your team completes per sprint and turns that history into a forecast. You enter the completed points for each recent sprint, and the tool charts the trend while calculating your average velocity along with the median, minimum, and maximum. It also derives a rolling three-sprint average and a stability rating, so you can see whether the team is speeding up, slowing down, or holding steady — and how predictable it really is. Add the remaining backlog and your sprint length and the built-in backlog forecast projects how many sprints and which calendar date the work should finish, with an optimistic-to-pessimistic range drawn from your best and worst sprints. An optional days-off field per sprint produces a capacity-adjusted velocity in points per available team-day. Everything is computed instantly in your browser, with no signup and no data leaving your device.
How to use Team Velocity Tracker?
Tracking and forecasting velocity takes only a moment:
- 1 Enter the sprint data by adding the story points your team actually completed in each past sprint. Add at least three to five sprints, because a single data point cannot reveal a meaningful trend, and optionally record planned days off for each sprint.
- 2 Read the metrics: average, median, minimum, maximum, the rolling three-sprint average, and a stability rating that flags whether your velocity is stable, variable, or erratic based on its spread.
- 3 Investigate any large swings. A sudden drop may point to holidays, scope changes, or blockers, while a spike might reflect carried-over work, so understanding the cause keeps your forecast honest.
- 4 Forecast the backlog by entering the remaining story points and your sprint length in days. The tool estimates the likely number of sprints and completion date, plus an optimistic and pessimistic range, so you can commit to a realistic release window.
Why use this tool?
Velocity is one of the most practical metrics in Scrum because it grounds planning in evidence rather than optimism. A team that consistently completes around 30 points should not commit to 45 just because stakeholders want more — velocity makes that reality visible and negotiable. Tracking the trend also surfaces problems early: a steady decline can signal growing technical debt or team fatigue long before a deadline slips. The median guards against a single outlier sprint distorting the picture, while the stability rating tells you how much to trust the forecast at all — an erratic team needs a wider safety margin than a stable one. The optimistic-to-pessimistic forecast range converts that uncertainty into concrete dates stakeholders can plan around, and the capacity adjustment keeps velocity fair when holidays shrink a sprint. Because the tracker runs locally in your browser, your sprint history stays private.
Examples
A team logs five sprints of 28, 32, 30, 26, and 34 points. The tool shows an average and median velocity of 30 with a stable rating, giving a sensible target for the next sprint instead of an optimistic guess.
Velocity slips from 35 to 32 to 27. The rolling three-sprint average drops below the overall average, the trend arrow points down, and the team investigates blockers before delivery suffers.
With an average velocity of 30 (best 34, worst 26) and 120 points remaining, the forecast shows a likely 4 sprints, an optimistic 4 and a pessimistic 5, then projects the completion date for a 14-day sprint.
Frequently Asked Questions
How many sprints should I track for an accurate average?
Track at least three to five sprints. Fewer than three makes the average and stability rating unreliable, while five or more smooths out one-off anomalies and produces a forecast you can trust.
What does the stability rating mean?
It measures how spread out your velocity is relative to its average (the coefficient of variation). A tight spread is rated stable, moderate spread variable, and a wide spread erratic — the more erratic, the wider a safety margin your forecast needs.
How does the backlog forecast calculate dates?
It divides the remaining points by your average velocity to get the likely number of sprints, uses your best and worst sprints for an optimistic and pessimistic range, then multiplies sprints by sprint length to project calendar dates.
What is capacity-adjusted velocity for?
When days off vary between sprints, raw velocity can mislead. Entering planned days off lets the tool report points per available team-day, a fairer measure for sprints shortened by holidays or leave.
Is my sprint data stored anywhere?
No. The tracker calculates everything in your browser, so your sprint history, velocity figures, and forecast are never uploaded to or saved on a server.
Related Tools
Explore more free tools you might find useful