Don't like ads? Go Ad-Free Today 

Sprint Velocity & Capacity Calculator

DataDeveloperMath

ADVERTISEMENT · REMOVE?

INPUT

Auto Process

Team & Sprint

Team Size *

Sprint Length (working days) *

Working days in one sprint (e.g. 10 for a 2-week sprint)

Productive Hours / Person / Day *

Net working hours per person per day (excluding breaks, meetings)

Velocity History

Completed Story Points (last N sprints) *

Comma or space-separated story points from recent sprints

Adjustments

Team Time-Off Days

Total person-days lost to PTO, holidays, sickness across the team this sprint

Focus Factor (%) *

Share of working time spent on sprint work (typical range 60-85%)

Hours per Story Point

Used to convert story points to hours in the results

OUTPUT

Client Side

Capacity Summary

Metric	Value
Average Velocity	-
Median Velocity	-
Velocity Range (min - max)	-
Recommended Commitment (conservative - stretch)	-
Adjusted Capacity (after availability & focus)	-

Hours Breakdown

Item	Hours
Nominal team hours (size × days × hrs)	-
Less: time-off hours	-
Available hours	-
Less: non-focus time	-
Net focused hours	-
Equivalent story points (hours ÷ hrs per point)	-

ADVERTISEMENT · REMOVE?

Guide

Sprint Velocity & Capacity Calculator

Plan your next sprint with math, not guesswork. Feed in your velocity history, team size, PTO, and focus factor, and get an evidence-based commitment range in story points and hours.

How to Use

Enter your team size and sprint length in working days.
Set productive hours per person per day (typically 5-6 to account for meetings and context switching).
Paste recent completed story points, separated by commas or spaces.
Add team time-off days for the upcoming sprint (PTO, holidays, expected sick days).
Tune the focus factor and hours-per-point ratio, then read the adjusted capacity and commitment range.

Features

Velocity history – Averages, medians, and ranges across the last N sprints.
Availability adjustment – Scales capacity down for PTO, holidays, and sick days.
Focus factor – Accounts for meetings, support work, and context switching.
Story points ↔ hours – Converts capacity between both units so engineers and PMs stay aligned.
Recommended commitment range – Conservative to stretch, bounded by historical max.
Client-side only – Your team data never leaves the browser.

 FAQ

What is sprint velocity?

Sprint velocity is the amount of work a team completes in one sprint, usually measured in story points. It is a trailing indicator of how much scope a team can realistically deliver given their current process, skills, and environment. Velocity is only meaningful when compared against the same team over multiple sprints — it cannot be used to compare one team against another.
Why use a focus factor?

A focus factor represents the share of working time a team actually spends on sprint work. The rest goes to meetings, code review, production support, interviews, and context switching. Typical focus factors land between 60% and 85%. Without a focus factor, capacity planning assumes 100% of paid time is available for sprint scope — which rarely matches reality.
How is recommended commitment different from average velocity?

Average velocity is backwards-looking and ignores changes in team availability. Recommended commitment adjusts that number for the upcoming sprint using PTO, holidays, and focus factor. The low end is conservative enough that the team can finish every committed item; the high end is a stretch target bounded by the team's historical maximum.
What is a healthy team velocity variance?

A coefficient of variation under roughly 20% suggests the team is estimating and delivering consistently. Large swings usually indicate inconsistent estimation, sprint goals that change mid-sprint, or under-staffing. Velocity data from the first three sprints of a new team is almost never reliable — wait until the team has stabilized before using averages for commitment.
Should story points represent time?

Story points are a relative measure of effort, complexity, and risk — not a direct time unit. Teams that anchor story points to hours often end up estimating in disguised hours, which loses the benefit of relative sizing. The hours-per-point conversion in this calculator is a sanity check for capacity planning, not a pricing formula for individual tickets.