Sprint Velocity Calculator

Sprint velocity is the number of story points (or units of work) your team consistently completes in a sprint. It is a backward-looking measure used to forecast how much work you can realistically commit to in upcoming sprints.

Use the last 3–5 completed sprints. Fewer than 3 is too noisy; more than 5 starts to mask team or scope changes (new hires, new product area). Drop outlier sprints affected by major events like vacations or production incidents before averaging.

Real teams handle support tickets, code reviews, ad-hoc fire drills, and meetings during a sprint. Reserving 20% buffer keeps the team from over-committing and falling short. If your team consistently hits 100% of commitments, you can dial the buffer down — but most teams find the buffer accurate.

Use completed. Velocity is what you actually shipped, not what you planned to ship. The calculator also shows hit rate (completed / committed) so you can spot when commitments consistently outpace delivery.

Velocity should stabilize within ~20% across sprints once a team is established. Big swings usually indicate one of: estimation drift (story points keep getting bigger), large unplanned work, missing team members, or sprint length changes. Investigate the outlier sprints in retrospective.