Sprint Capacity Planner
Turn team size, hours, focus factor and time off into realistic sprint capacity - in hours and story points, with the math on the table.
Your team & sprint
Editable estimates. Adjust to match your team.
Capacity
- Gross person-days (5 × 10)50
- After PTO of 3 person-days47
- Raw hours (× 6h/day)282h
- Focused hours (× 70%)197.4h
- Story points (÷ 6h)32.9 pts
How sprint capacity planning works
Sprint capacity is not your headcount times eight hours. Real capacity is what remains after meetings, code review, support, interviews, and time off - the difference between a plan that lands and a sprint that quietly slips. Starting from gross person-days, subtracting PTO, and then applying an honest focus factor gives you a number your team can actually commit to.
The focus factor does most of the work here. A team assuming 100% utilisation will over-commit every sprint; one that calibrates it from history plans with confidence. Converting the result into story points at your own hours-per-point ratio gives planning a shared unit - useful as a sanity check against what the backlog is asking for. For the ceremony itself, see our sprint planning guide and try the planning poker tool.
Estimates are a fine start, but the real win is grounding capacity in delivered work rather than optimism. Explore sprint planning tooling, dig into developer velocity, or browse the rest of our free tools.
Frequently asked questions
Plan from what you ship, not what you hope
FeatureFactory measures real throughput from delivered work, so your next sprint plan is grounded in evidence instead of a guessed focus factor.
Get early access