In Scrum, capacity represents the total amount of available work time a team has for an upcoming sprint, while load is the actual amount of work the team pulls into that sprint.
& Capacity in Scrum
Understanding Capacity
Capacity acts as your ceiling. It is a forward-looking calculation performed right before sprint planning. It accounts for the reality of the upcoming calendar cycle.
- To find a team’s capacity, you multiply total working days by the number of team members.
- You then subtract non-productive time like public holidays, planned vacation days, and standard company meetings.
- Finally, you apply a focus factor (typically around 70% to 80%) to account for daily distractions and context switching.
Understanding Load
Load represents the weight of the commitments made by the developers. It is the cumulative volume of user stories and tasks that the team intends to deliver during the sprint.
- Load is entirely determined by how the team estimates the product backlog items pulled into the sprint.
- Unlike capacity (which is restricted by time), load can theoretically be pushed to any level, though overloading creates major delivery risks.
Balancing the Relationship
The ultimate goal of a Scrum Master is to help the team balance load against capacity to maintain a sustainable pace.
- The Safe Zone: Best practices dictate keeping your load at 10% to 20% below your absolute capacity. This visual buffer creates room for unexpected blockers or minor illness.
- The Danger Zone (Overcommitment): An exact match where load equals capacity is considered an anti-pattern in Agile frameworks. It strips the team of flexibility, spikes burnout, encourages poor-quality code, and almost always leads to missed sprint goals.
Comparison Between Load & Capacity in Agile Scrum
PROject Templates 