Scrum Team Velocity Points per Sprint

Scrum Velocity: forecasting sprint capacity

Velocity is how many story points a Scrum team actually finishes per sprint, averaged across the last handful of iterations. The usual formula is velocity = (pts_sprint1 + pts_sprint2 + ... + pts_sprintN) / N. N is normally the last 3 to 5 sprints, far back enough to smooth out the noise but recent enough that it still reflects the team and tech stack you have today.

Story points run on a modified Fibonacci scale (1, 2, 3, 5, 8, 13, 20), meant to capture relative effort and uncertainty rather than hours. That makes velocity a prediction, not a target. It gives the Product Owner a rough sense of how much scope fits into the next sprint or release. What it is not is a productivity KPI, and it is certainly not a stick to push the team harder. Mike Cohn goes into this at length in Agile Estimating and Planning (2005).

Applications

It shows up in sprint planning (how many backlog items fit), release forecasting (when the MVP will land), and capacity-versus-demand analysis. You can also use it to gauge what a refactor or a new hire did to throughput, or to feed Monte Carlo simulations that estimate release-date probabilities. Jira, Azure DevOps and Linear all compute velocity for you from the points on completed issues per sprint.

FAQ

Can I compare velocity between teams? No. Each team calibrates its own story points, so team A’s “5” has nothing to do with team B’s “5”. Put velocities side by side and you just push people to inflate their points, which guts the whole point of the estimate.

Should I count incomplete stories partially? No. A story is either done, and you count its full points, or it isn’t, and it counts for zero. Handing out partial credit breaks the binary “definition of done” that keeps velocity trustworthy in the first place.

What if my velocity is very unstable? Usually it traces back to sprints of different lengths, sprints that got interrupted, scope shifting mid-sprint, or stories that are simply too big. Break the stories down smaller and guard the sprint goal.