Sprint Capacity Calculator

Sprint capacity is the realistic amount of work your team can complete in a sprint, accounting for PTO, holidays, meetings, support work, and other interruptions. It is different from velocity — velocity measures past delivery, capacity measures available time for the upcoming sprint.

Velocity is what you historically delivered (a backward-looking average). Capacity is what you can theoretically deliver this specific sprint (a forward-looking estimate). Use capacity to adjust commitment when teammates are out, on-call, or working on a new product area.

Most healthy teams operate at 60–80% focus once you account for daily standups, code reviews, support rotation, and ad-hoc meetings. Pure focus over 80% is rare; under 50% suggests too many recurring commitments. Look at calendar load and historical hit rate to calibrate.

Divide your past sprint velocity by total focused days in those sprints. Most teams land between 1.5 and 2.5 points per focused day. If your number is wildly different, your story-point estimates may not be calibrated — anchor against a few reference stories first.

Yes — use 0.5 day for half-days. People often forget half-day meetings, all-hands, or company offsites that legitimately reduce capacity. Being honest about partial-day overhead prevents the "we always finish 70% of what we commit" pattern.