Work out how many focus hours your Scrum Team really has this Sprint, after public holidays, leave, Scrum events, refinement and the time it takes to review AI agent output.
Pick the start date and length. Weekends and holidays show on the calendar below.
Holidays that apply to the whole team. Festival and state holidays change every year, so add the ones your organisation observes.
National holidays adds Republic Day, Independence Day and Gandhi Jayanti when they fall inside the Sprint.
Allocation is the share of each person's time that belongs to this team. Leave is the number of working days they are away this Sprint.
| Name | Allocation % | Leave days | Remove |
|---|
Event hours are prefilled with the Scrum Guide's maximum timeboxes, scaled to your Sprint length. Your team may use less. The Daily Scrum is counted at 15 minutes per person per working day.
Refinement is an ongoing activity, not a Scrum event, and the Scrum Guide sets no fixed amount for it. Enter the total hours your team has booked for refinement sessions this Sprint, for example two 2-hour sessions is 4 hours. Each Developer attending is counted, the same way as the events.
AI agents are not team members, so they add no hours here. What they add is output a person must check. Enter the agent tasks you expect and how long a human needs to review each one.
| Agent or tool | Tasks this Sprint | Review minutes per task | Remove |
|---|
Sprint capacity is the time the Developers can realistically spend on Sprint work. It is not the number of people multiplied by eight hours. Public holidays, leave, Scrum events, Product Backlog refinement and the review of AI-generated work all come out of the same pool of hours.
The Scrum Guide doesn't prescribe a capacity formula. It does say that Developers forecast with more confidence when they understand their past performance, their upcoming capacity and their Definition of Done. Capacity is one input to Sprint Planning. It helps the Developers decide how much to take on; it is never a quota for the Sprint.
Baseline = working days in the Sprint × focus hours per day × allocation
Available = Baseline − holiday hours − leave hours
Scrum events = (Planning + Review + Retrospective) × share of Sprint attended + 15 minutes × days present, each × allocation
Refinement = refinement hours booked × share of Sprint attended × allocation, for each Developer
AI review = agent tasks × review minutes ÷ 60
Team focus hours = Available − Scrum events − Refinement − AI review
Event hours start from the Scrum Guide's maximum timeboxes for a one-month Sprint: eight hours for Sprint Planning, four for the Sprint Review and three for the Sprint Retrospective. For shorter Sprints the calculator scales them down in proportion, so a two-week Sprint starts at half. Overwrite them with what your team actually uses.
Product Backlog refinement works differently. The Scrum Guide describes it as an ongoing activity and sets no time limit or percentage for it, so the calculator doesn't assume one. Enter the hours your team has actually booked for refinement in this Sprint.
An agent can produce code, tests or documentation, but it is not accountable for any of it. Accountability stays with people. That moves the constraint from writing work to verifying it, so the calculator treats agents as a demand on human time rather than as extra members. Leave this line out and your plan will look comfortable on paper and fall short in the Sprint.
A team of five Developers runs a two-week Sprint from Monday 28 September to Friday 9 October 2026. Gandhi Jayanti on Friday 2 October is a holiday. Everyone is fully allocated at six focus hours per day, one person takes two days of leave, the team has booked two 2-hour refinement sessions, and an AI coding assistant is expected to complete 20 tasks that each need 30 minutes of review.
| Step | Hours |
|---|---|
| Baseline: 10 weekdays × 6 hours × 5 people | 300.0 |
| Holiday: 1 day × 6 hours × 5 people | −30.0 |
| Leave: 2 days × 6 hours | −12.0 |
| Scrum events (scaled timeboxes plus Daily Scrums) | −46.6 |
| Refinement: 4 hours booked × 5 Developers (reduced for the person on leave) | −19.1 |
| AI review: 20 tasks × 30 minutes | −10.0 |
| Team focus hours | 182.3 |
About 61% of the headline 300 hours is left for Sprint work. That gap is why teams that plan against the headline number keep carrying work over.
Capacity informs the Developers' forecast. It never replaces it.
It is the time the Developers realistically have for Sprint work after holidays, leave, Scrum events and other commitments. It feeds Sprint Planning; it is not a target the team must fill.
No. The Scrum Guide mentions upcoming capacity as something that helps Developers forecast, but how a team estimates it is up to the team.
No. Agents add capacity to the work, but they are not accountable members. Their output needs human review, so this calculator subtracts that time from human capacity.
The Scrum Guide sets no fixed amount. Refinement is an ongoing activity, and each team decides how much it needs. Enter the hours your team has actually booked for refinement sessions in the Sprint.
Use the hours a person can spend on Sprint work on a normal day, after email, organisational meetings and other non-team work. Many teams start between five and six hours and adjust after a few Sprints.
You can scale a past result. The calculator multiplies last Sprint's completed work by the ratio of this Sprint's capacity to last Sprint's. Treat it as a starting point for the Developers' forecast, not a commitment.
No. Calculations run in your browser. If you tick "Remember my team on this device", the details are saved only in this browser, and Reset clears them.
More free tools for Scrum Teams working with AI.