Leadership Intelligence
Capacity Planning Spreadsheet Template
Model realistic engineering capacity by accounting for incidents, toil, support, and meetings before you commit roadmap features. Copy this structure into Sheets/Excel and plug in your team data.
How to use: Fill the inputs table with your team size, working hours, and observed percentages for incidents/toil/support/meetings. The template calculates true feature capacity and creates a buffer for surprises. Commit roadmap only up to the commitment capacity.
1) Inputs (edit these for your team)
| Input | Value | Notes |
|---|---|---|
| Team Size | 6 engineers | Include engineers contributing to the roadmap |
| Hours per Engineer (quarter) | 300 hours | Adjust for vacations/holidays (e.g., 10 weeks x 30 hrs focus) |
| Incident Time % | 18% | Average of last 2-3 quarters |
| Toil & Maintenance % | 22% | Upgrades, patching, tech debt |
| Support & Troubleshooting % | 15% | Product team questions, pairing, unblockers |
| Meetings & Overhead % | 12% | Planning, ceremonies, stakeholder reviews |
| Feature Work Target % | 33% | 1 - (incident + toil + support + meetings) |
| Commitment Capacity % | 35% | Add small buffer if data is noisy; avoid over-commit |
2) Calculations (copy these formulas)
Total Capacity (hours): =Team_Size * Hours_per_Engineer → Example: 6 * 300 = 1,800
Feature Capacity (hours): =Total_Capacity * Feature_Work_Target_% → 1,800 * 33% = 594
Commitment Capacity (hours): =Total_Capacity * Commitment_Capacity_% → 1,800 * 35% = 630
Hours Already Promised: Sum of all features with estimates
Remaining Buffer: =Commitment_Capacity - Hours_Already_Promised
3) Feature Stack (prioritize to fit capacity)
| Feature | Priority | Estimate (hrs) | Conf. % | Owner | Status |
|---|---|---|---|---|---|
| Service Mesh Integration | P0 | 240 | 70% | Alex | At Risk |
| Multi-Region Deployments | P0 | 210 | 75% | Priya | At Risk |
| Cost Attribution by Service | P1 | 140 | 80% | Diego | On Track |
| DR Automation | P2 | 120 | 65% | Sam | At Risk |
Total Estimated: 710 hours (exceeds commitment capacity of 630) → Re-scope or de-prioritize.
4) Outputs to Share
- Capacity Summary: Show feature capacity vs. total capacity so leaders see constraints.
- What We Can Commit: List features that fit within commitment capacity.
- What We Cannot Commit: Stretch goals separated; communicate clearly.
- Assumptions: Note incident/toil/support percentages and when you will re-baseline.
Tip: Re-baseline percentages each quarter from actuals. If incidents drop from 18% to 12%, your feature capacity rises—celebrate that and reinvest intentionally (not by surprise over-commitments).
← Back to Platform SLA Template