Engineering capacity planning template

Engineering capacity planning compares the engineering time you actually have with the time the roadmap needs. Start with engineers times working weeks in the period, subtract time off, holidays, on-call, support, meetings and planned maintenance, and you get the capacity available for roadmap work, often much less than headcount suggests. Then estimate the roadmap in engineer-weeks by skill. The difference is your gap, which you close by cutting scope, moving dates, moving people or adding engineers. The template below does the math.

Engineering capacity planning template

1. Available capacity (per team, per quarter)

2. Roadmap demand

3. Gap and decision

How to use this capacity planning template

1. Count engineers per team for the quarter, including planned joiners from their productive date and planned leavers until their last day.
2. Calculate gross engineer-weeks, then subtract each line using last quarter's real numbers for on-call, support and interrupts. If you have no data, track it this quarter.
3. Agree the maintenance and tech debt allocation with product leadership before planning, so it is not the first thing cut.
4. Estimate roadmap initiatives in engineer-weeks with a low and high range, and note the skills each needs.
5. Compare available capacity with the high estimate per team and per skill. A team can have enough engineer-weeks and still lack the one skill an initiative needs.
6. Close each gap with an explicit decision: cut scope, move the date, move people between teams, or add engineers. Record the owner of each decision.
7. Re-run the numbers mid-quarter with actual time off and interrupts.

Example: one team, one quarter

In this illustration, a team that looks like 72 engineer-weeks has 36 for the roadmap. The percentages are examples; use your own.

Capacity by skill, not just by team

Total engineer-weeks hide the real constraint in many teams: one skill. If three initiatives each need a data engineer and you have one, the team is over capacity even when the totals look fine. Add a short skills view to the plan: list the skills the roadmap needs (backend, frontend, data, mobile, infrastructure, AI), the engineer-weeks each initiative needs per skill, and the engineer-weeks available per skill after overheads. Gaps in a single skill are often the cheapest to close, because one added specialist can unblock several initiatives at once.

Common capacity planning mistakes

• Planning with headcount. Six engineers do not give you six engineers' worth of roadmap time. Subtract the real overheads.
• Single-point estimates. Use low and high estimates and plan against the high one for commitments.
• Ignoring skills. Total capacity can look fine while one specialist is booked at twice their time.
• Counting new hires from their start date. Count them from when they are productive, and subtract buddy time.
• Hidden maintenance. If tech debt has no explicit allocation, it happens anyway, unplanned, and the roadmap slips.

Closing the gap with added engineers

When the gap is real and the dates cannot move, Ryz adds senior engineers to your team, reporting to your leads, on US business hours including New York hours. They count as roadmap capacity once they are onboarded, and you can size the team to the gap, by skill. Only the top 1% of the tens of thousands of engineers we interview make it, and typical cost is $7,000 to $15,000 per engineer per month, so the cost of closing a gap is easy to put next to the cost of slipping. Talk to us to scope your team, or read about staff augmentation.

Related

• Engineering hiring plan template
• Software development team structure template
• Build vs buy vs staff decision matrix
• Staff augmentation for scaling engineering teams
• Engineer rates by role

FAQ

How do you calculate engineering capacity?

Multiply engineers by working weeks in the period to get gross engineer-weeks, then subtract time off, on-call, support and interrupts, meetings, planned maintenance and onboarding. What remains is the capacity available for roadmap work.

What percentage of engineering time goes to roadmap work?

It varies widely by team. Teams with heavy on-call, support load or legacy systems have much less roadmap time than headcount suggests. Measure your own overheads for a quarter rather than relying on a rule of thumb.

How should engineering teams estimate roadmap demand?

Estimate each initiative in engineer-weeks with a low and high range, note the skills required and the dependencies, and plan commitments against the high estimate. Re-estimate as initiatives are broken down.

How often should engineering capacity be planned?

Quarterly, aligned with roadmap planning, with a mid-quarter check against actual time off and interrupts. Teams in fast-changing environments may also re-plan monthly.

What do you do when demand exceeds capacity?

Make an explicit decision per gap: cut or simplify scope, move the date, move engineers from lower-priority work, or add engineers. Record the decision and its owner so the gap does not silently become a missed date.

Questions we didn't answer? Email info@ryzlabs.com.