Velocity calculator
Average your recent sprints and forecast the backlog. Velocity is a forecast input — not a score, not a target.
Velocity answers one question: how many sprints until the backlog is done? Use it for that — nothing else.
Average velocity: 20.8 points per sprint
Over 4 sprints, ranging 18–24.
At that rate, 180 points is about 9 sprints — somewhere between 8 and 10, depending on whether the next few sprints run like your best or your worst.
How it works
Average the points your team completed over the last three to five sprints — that's your velocity. Divide the points remaining by that average and you have a forecast in sprints. The range uses your best and worst recent sprint, because the next one lands somewhere in that spread. That's the whole calculation; the simpler it stays, the harder it is to game.
What not to do with it
Don't set it as a target — tell a team to raise velocity 20% and they'll size the same work bigger, not ship more. Don't compare teams — two teams calibrate against different reference stories, so the numbers aren't the same unit. The full set of failure modes lives in the velocity write-up; this page is just the arithmetic.
Forecast with it. Never grade a team on it — the number inflates the moment you do.
Adjacent: velocity, in full for what it's for and how it breaks; how many story points per sprint for sizing the next sprint; story points vs hours for why you forecast from velocity instead of converting to time.