Sprint Capacity Planning Guide
A practical guide for calculating sprint capacity from team availability, focus time, meetings, and point conversion.
Capacity is not calendar time
A two-week sprint rarely contains two full weeks of delivery time. Time off, public holidays, ceremonies, support work, onboarding, reviews, and context switching all reduce practical capacity.
StoryPointLab calculates capacity from explicit inputs so the team can discuss the assumptions behind a commitment before the sprint begins.
Inputs that matter
- Team size and working days define the starting availability.
- Time off removes unavailable person-days from the plan.
- Meeting load reflects ceremonies, recurring coordination, and required collaboration.
- Focus factor accounts for realistic delivery time after interruptions and operational work.
- Point conversion helps teams that want a rough bridge from hours to story points.
How teams use the result
The capacity number should guide commitment, not become a target to maximize. If the calculation says the team has less room than expected, the healthy response is to reduce scope or clarify priorities.
Capacity planning becomes more useful over time when the team compares planned capacity with actual delivery and adjusts the focus factor honestly.
Common planning mistakes
- Ignoring partial availability from holidays or vacations.
- Counting every working hour as delivery time.
- Treating carry-over work as free because it was already started.
- Using capacity to pressure the team instead of protecting delivery focus.