Sprint Capacity Calculator: Agile Team Velocity Planner

Agile team capacity per sprint: hours and story points

Sprint capacity is computed member by member: (working days − leave) × (daily hours − meeting hours), multiplied by the focus factor, then divided by the average number of hours a story point has taken. With five people over two weeks, 75% focus and 6 hours per point, the tool finds 214 productive hours, i.e. 35.7 points.

Formula

• Active days = sprint working days − leave days.
• Gross hours = active days × daily hours; meeting hours = active days × daily ceremony and meeting hours.
• Productive hours = (gross − meetings) × focus factor (40 to 100%).
• Capacity in points = total productive hours ÷ hours per story point (team history).
• Commitment rate = planned points ÷ capacity. Above 105% the tool flags over-commitment; below 80%, unused capacity.

Example

Two-week sprint, 5 people at 7.5 h a day. The lead dev has 1 day off and 2 h of meetings a day, the backend developer 2 days off, the others none, with 1.2 to 1.5 h of meetings. Total: 352.5 gross hours (shown as 353), 66.6 meeting hours, 285.9 net hours, then 214.4 productive hours at 75% focus. At 6 h per point, capacity is 35.7 points. Planning 45 points means 126%: the team is over-committed by about 9 points.

Assumptions and limits

• The focus factor covers interruptions, support and reviews; measure it on past sprints rather than keeping 75%.
• Hours per point only make sense for your own team; points cannot be compared across teams.
• Changing the sprint length does not update the working days of members already entered (only those added afterwards): fix the days column by hand.
• Public holidays are not deducted automatically: remove them from working days.

Velocity actually delivered over the last three sprints remains the best check on this estimate.

Frequently Asked Questions

What is a Scrum team's focus factor?

It is the share of net hours, after meetings, actually spent on sprint tasks; the rest goes on interruptions, support, reviews and context switching. The tool sets it between 40% and 100%, 75% by default. To measure it, divide the hours spent on the sprint backlog by the net hours available over your last sprints.

How do I convert hours into story points?

Divide productive hours by the average number of hours a point has taken your team in previous sprints. With 214.4 hours and 6 hours per point, capacity is 35.7 points. This ratio is specific to each team: do not borrow another team's.

When is a sprint over-committed?

The tool compares planned points with calculated capacity. Above 105% it flags over-commitment; below 80%, unused capacity; in between, a healthy commitment. In the example, 45 points against 35.7 of capacity gives 126%, about 9 points to move out.

How many meeting hours per day should a sprint include?

The tool suggests 1.2 hours a day per developer and 2 hours for a lead, including Scrum ceremonies and company meetings. Over a 10-day sprint, 1.2 hours a day adds up to 12 hours, 16% of a 7.5-hour day. Check real calendars to refine the figure for each member.

Is this tool really free?

Yes, all tools on Kristools are 100% free and accessible without registration.

Is my data protected?

Yes. All processing is performed directly and securely inside your browser. No personal data is sent to our servers.