Capacity Calculation in Scrum: A Practical Guide

Capacity calculation in Scrum is the process of estimating how many hours or story points a team can commit to in an upcoming sprint, based on team availability, past velocity, and known time off. You typically calculate it by taking the team’s total available work hours (number of team members × working hours per day × sprint days) and subtracting time for meetings, ceremonies, and other non-development activities. This article explains the formula, how to use it, and common pitfalls.

Formula

The basic capacity formula is:

Capacity (hours) = Team size × Sprint length (days) × Working hours per day × Focus factor

Where:

• Team size – number of developers, testers, and other full-time members (unit: people)
• Sprint length – number of working days in the sprint (unit: days)
• Working hours per day – contracted or typical productive hours per person per day (unit: hours)
• Focus factor – percentage of time actually spent on sprint work, after accounting for meetings, admin, support, and context switching (unit: %, e.g., 70 means 0.70)

This gives a team-level capacity in hours. If you use story points instead, you would replace the focus factor with the team’s average velocity (points per sprint) and skip the hours calculation.

Worked Example

Using the defaults from the calculator above:

1. Team size = 5 people
2. Sprint length = 10 days
3. Working hours per day = 8 hours
4. Focus factor = 70%

Calculation:

Capacity = 5 × 10 × 8 × 0.70 = 280 hours

So the team can commit to roughly 280 hours of sprint work. This is the headline answer shown in the calculator.

Why Capacity Matters in Scrum

Capacity is the foundation of sprint planning. Without it, teams either overcommit (leading to unfinished work and burnout) or undercommit (leaving idle time and reducing productivity). Capacity helps the Product Owner and team select the right number of backlog items for the sprint. It also provides a baseline for measuring velocity over time, because velocity is typically expressed in story points, but capacity in hours gives a reality check on whether the points are realistic.

Capacity is not the same as velocity. Velocity is a historical measure of how much work the team completed in past sprints (in story points). Capacity is a forward-looking estimate based on availability and focus. Many teams use both: capacity (hours) to sanity-check the number of stories, and velocity (points) to actually select the stories.

How to Calculate Capacity Step by Step

Follow these steps to calculate your team’s sprint capacity:

1. List all team members who will contribute to the sprint (include developers, QA, UX, etc.).
2. Determine the sprint duration in working days (exclude weekends and holidays).
3. Estimate each person’s available hours per day (typically 7-8 for full-time, but adjust for part-time).
4. Subtract non-availability – planned time off, training, support duty, and other commitments.
5. Subtract ceremony time – sprint planning, daily standup, review, retrospective, and backlog refinement.
6. Apply a focus factor – typically 60-80% to account for unplanned interruptions, emails, and context switching.
7. Sum up the available hours across all members to get team capacity.

For example, a 5-person team with 10 working days and 8 hours/day has 400 gross hours. If they spend 10% of time in ceremonies (40 hours) and 20% on unplanned work (80 hours), the net capacity is 280 hours.

Common Mistakes and Misconceptions

Several pitfalls can skew capacity calculations:

• Using all 8 hours as productive – no one codes 8 hours straight; meetings, emails, and breaks eat time.
• Ignoring part-time members – a 50% member contributes half the hours.
• Forgetting holidays – a sprint that spans a public holiday has fewer working days.
• Confusing capacity with velocity – capacity is hours, velocity is points; they are not interchangeable.
• Not adjusting for support work – if the team handles production issues, that time must be subtracted.
• Using a fixed focus factor – the focus factor should be reviewed each sprint based on actual data.

A common misconception is that capacity must equal the sum of all individual commitments. In reality, team capacity is not just the sum of individual hours because of collaboration overhead (pairing, code reviews) – that’s why the focus factor is applied.

Capacity vs. Velocity: Which to Use?

Capacity and velocity serve different purposes:

• Capacity (hours) – useful for planning the number of hours available, especially when tasks are estimated in hours. Good for teams that are new or have variable availability.
• Velocity (story points) – useful for predicting how many story points the team can complete based on past performance. More stable and less affected by individual availability variations.

Many mature Scrum teams rely primarily on velocity for sprint planning and use capacity only as a check. For example, if velocity is 30 points and the team’s capacity drops from 280 to 200 hours due to a holiday, they might reduce the sprint goal to 25 points. The key is to use both metrics together, not in isolation.

Limitations of the Formula

The capacity formula is a simplified model. It assumes all team members have the same working hours and that the focus factor is uniform, which is rarely true. It doesn’t account for task complexity, dependencies, or the fact that some tasks (like research) may take longer than estimated. Also, the formula gives a team-level number, but individual capacity can vary significantly – a senior developer may produce more per hour than a junior, but the formula treats them equally.

Another limitation is that capacity in hours does not directly translate to story points. If your team uses story points, you should not convert points to hours (e.g., 1 point = 8 hours) because points are relative, not time-based. Instead, use velocity to select work and capacity to ensure the team isn’t overcommitting.

Frequently Asked Questions

What is a good focus factor for a Scrum team?

A focus factor between 60% and 80% is typical. New teams or teams with many interruptions might be at 50-60%, while mature teams with few disturbances can reach 80%. Track actual productive time over a few sprints to calibrate your own factor.

Should I include the Scrum Master and Product Owner in capacity?

Only if they are actively developing or testing. The Scrum Master and Product Owner usually have other responsibilities; include them only if they contribute to sprint work. Otherwise, exclude them and their time.

How do I handle part-time team members?

Calculate each person’s available hours individually and sum them. For a part-time member, multiply their daily hours by the number of days they work in the sprint. For example, a 50% member working 4 hours/day for 10 days contributes 40 hours.

What if my team uses story points instead of hours?

Then capacity is usually expressed in story points using velocity. You can still calculate hours as a sanity check, but don’t convert points to hours. Use velocity to select stories and capacity to ensure the total hours of those stories (if estimated) don’t exceed the team’s available hours.

How often should I recalculate capacity?

Every sprint, because availability, holidays, and team composition change. Recalculate at the start of each sprint planning session. Also, review the focus factor based on actual data from the previous sprint to improve accuracy.

Can capacity be negative?

No, capacity is always positive (or zero if the team has no available time). If you subtract too much, you may end up with a negative number, which indicates the team has more commitments than available time – that’s a sign to reduce scope or add resources.

Conclusion

Capacity calculation in Scrum is a practical tool to plan sprints realistically. By using the formula and adjusting for your team’s reality, you can avoid overcommitment and improve delivery predictability. Remember to combine capacity with velocity for best results, and revisit the numbers every sprint.

Related

• Rhetoric Shelves: Mirror of Life?
• How to Root Alcatel One Touch Venture
• Home Assistant Cost: What It Really Takes to Run It

in team | Team size | people | 5 | 0
in days | Sprint length | days | 10 | 0
in hours | Working hours per day | hours | 8 | 0
in focus | Focus factor | % | 70 | 0
out capacity | Team capacity | hours | team * days * hours * (focus / 100) | 0