Sprint Capacity Calculator
Calculate team capacity and estimate story points for sprint planning
What is Sprint Capacity Calculator?
The Sprint Capacity Calculator is a free agile planning tool that works out how many hours your team can realistically commit to during a single sprint. You enter the sprint length, working hours per day, a focus factor, and an optional capacity buffer, then build a configurable team where each member has a role, an availability percentage, planned time off, and their own hours-per-day override. The tool subtracts time off, applies the focus factor and buffer, and returns a per-member and total breakdown in both hours and story points — using either a hours-per-point ratio or your historical velocity. A live commitment indicator then compares your planned work against available capacity so you never over-commit. It runs entirely in your browser and helps Scrum teams plan commitments they can actually deliver.
How to use Sprint Capacity Calculator?
Calculating realistic sprint capacity takes only a couple of minutes:
- 1 Configure the sprint by setting its length in working days, the productive hours per day, a focus factor, and an optional capacity buffer. The focus factor accounts for meetings, ceremonies, and context switching and typically falls between 60 and 75 percent; the buffer reserves an extra slice for unplanned work and interruptions.
- 2 Build your team. Add or remove members freely, and for each person choose a role, set their availability, record any planned time off such as holidays or part-time arrangements, and optionally override the hours-per-day if they differ from the team default.
- 3 Choose how story points are derived: enter an average hours-per-point ratio, or switch to velocity mode and provide a past sprint's points and capacity so the tool reverse-engineers the ratio from your real history.
- 4 Review the per-member and total breakdown, the buffer-adjusted capacity, and the estimated story points. Enter the hours you plan to commit to watch the commitment indicator confirm whether you are under, balanced, or over capacity, then refine the inputs after each sprint for ever-improving accuracy.
Why use this tool?
Teams that commit to more work than they can deliver miss sprint goals, erode trust with stakeholders, and burn out. The Sprint Capacity Calculator replaces optimistic guesswork with a grounded number that already accounts for time off, ceremonies, the focus factor, and a safety buffer. Because it separates raw hours from truly productive hours and breaks the figure down per member and per role, it sets honest expectations and makes commitments defensible to product owners. The committed-versus-available indicator turns those numbers into an instant traffic-light verdict, while the choice between a hours-per-point ratio and historical velocity means the story point estimate fits how your team actually works. Everything is calculated locally in your browser, so no data leaves your machine. Over several sprints the figures become a reliable baseline that improves your forecasting and protects your team from over-allocation.
Examples
A team of five sets a 10-day sprint at 6 productive hours per day, a 70 percent focus factor, and a 10 percent buffer. The tool returns roughly 210 net hours and a buffer-adjusted 189 hours, which it converts into a realistic story point commitment.
Rather than guessing a ratio, the team switches to velocity mode and enters last sprint's 30 points completed in 200 hours. The tool derives roughly 6.7 hours per point and applies it to the new capacity for a grounded forecast.
After adding members with mixed roles and a part-time contractor at 50 percent availability, the team enters the planned hours. The commitment indicator shows green below the buffer-adjusted capacity and turns red the moment it tips over.
Frequently Asked Questions
What is a focus factor and why does it matter?
The focus factor is the share of working hours a team actually spends on sprint work after meetings, ceremonies, support, and context switching. It usually sits between 60 and 75 percent, and applying it prevents you from planning against unrealistic raw hours.
How is the capacity buffer different from the focus factor?
The focus factor removes routine non-development time, while the capacity buffer reserves an extra percentage for genuinely unplanned work — incidents, urgent support, or scope discovered mid-sprint. The buffer-adjusted figure is the number you should commit against.
Should I use hours-per-point or velocity mode for story points?
Use hours-per-point when you have a stable average for how long a point takes. Switch to velocity mode when you have a recent sprint's points and capacity, and the tool will derive the ratio from that real data, which is usually more accurate than a fixed guess.
Can members have different working hours?
Yes. Each member can override the team's default hours-per-day, so part-timers, contractors, and people on reduced schedules are counted correctly. Leave the field blank to inherit the team default.
Should I include weekends and holidays?
No. Enter only working days for the sprint length, and record holidays and vacations as time off for each member so they are subtracted from the available capacity.
Is my team data stored anywhere?
No. All calculations happen entirely in your browser. No team names, roles, availability, or capacity figures are uploaded to or saved on any server.
Related Tools
Explore more free tools you might find useful