Capacity Planner
Forecasting & workload planning
Scrum Master Guide: Capacity Planning
The Capacity Planner predicts workload capacity by analyzing historical allocation data, ongoing projects, planned work, upcoming priorities, and team size. It helps you set realistic sprint commitments and avoid overloading teams. When circumstances change, make dynamic adjustments by refining project scopes, reallocating resources, and recalibrating delivery plans — maintaining momentum without team burnout.
Team Capacity (FTE)
| Team | Available FTE | Planned FTE | Gap | Status |
|---|---|---|---|---|
| Platform | 8.2 | 9.1 | -0.9 | Over |
| Mobile | 6.1 | 5.8 | +0.3 | OK |
| Data | 5.4 | 5.2 | +0.2 | OK |
| Frontend | 5.3 | 5.5 | -0.2 | Tight |
Capacity Utilization
Platform9.1 / 8.2 FTE
Mobile5.8 / 6.1 FTE
Data5.2 / 5.4 FTE
Frontend5.5 / 5.3 FTE
API Explorer
MockMock
Using Capacity Data in Ceremonies
- Sprint Planning: Pull
allocations_by_teambefore planning to see actual available FTE. If planned work exceeds capacity, negotiate scope before committing — not after the sprint starts. - Quarter Planning: Compare capacity across the next 3 sprints. If a team is overcommitted in Sprint 27, start rebalancing now rather than discovering it mid-sprint.
- Stakeholder Communication: Use the gap data to explain delivery risks factually: 'Platform team is 0.9 FTE over capacity — either scope must decrease or timeline must extend.'