What is a focus factor?

Focus factor (also called efficiency factor) is the percentage of time developers spend on productive sprint work after subtracting meetings, code reviews, standups, and other overhead. A typical range is 60–80%.

How do I convert hours to story points?

Enter your team's average hours per story point. The calculator divides total available hours by that figure. If you don't track hours per point, use your historical sprint velocity as a reference instead.

Should I include part-time team members?

Yes. Adjust the daily hours field to reflect each person's actual hours, or add fractional team members (e.g., 0.5 for a half-time contributor). Run the calculator once per cohort if hours vary significantly.

What counts as a time-off day?

Any working day a team member is unavailable: vacation, sick leave, or planned personal time. Count total person-days across the whole team, not unique calendar days.

How often should I recalculate capacity?

Run it before every sprint. Capacity changes with team composition, holidays, and planned absences, so a stale estimate leads to over-commitment.

Team Capacity Calculator

Name: Team Capacity Calculator
Availability: InStock
Author: Nham Vu

Enter your team size, sprint length, daily hours, holidays, time-off days, and focus factor to get available sprint capacity in hours and story points.

Sprint Parameters

Team members

Sprint length (working days)

10 days = 2-week sprint, 5 days = 1-week sprint

Daily hours per person

Public holidays in this sprint (days)

Calendar days the whole team is off

Team time-off (total person-days)

Sum of individual vacation/sick days across all members

Focus factor: 75%

10% (high overhead) 100% (pure coding)

Hours per story point

Typical range: 2–8 hours. Use your team's historical average.

Fill in the parameters on the left and click Calculate Capacity.

Summary

Enter your team size, sprint length, daily hours, holidays, time-off days, and focus factor to get available sprint capacity in hours and story points.

How it works

Available days = (team size × sprint days) minus public holidays and time-off days.
Gross hours = available days × daily hours per person.
Net hours = gross hours × (focus factor / 100).
Story point budget = net hours divided by hours per story point.

Use cases

Plan sprint commitments with realistic hour and story point budgets.
Adjust capacity when team members take vacation or observe public holidays.
Compare capacity across sprints to identify planning patterns.
Communicate bandwidth constraints to stakeholders before sprint kickoff.
Calibrate story point estimates when team composition changes.

Frequently Asked Questions

Last updated: 2026-07-01 · Reviewed by Nham Vu