Engineering Capacity Planning Template

Every capacity planning template ranking for this query runs the same arithmetic: gross hours per person, minus PTO and holidays, minus a fixed non-project allowance, divided into the backlog for one committed date. A 1994 study on how people predict their own task completion times found predictions built this way, from a plan rather than a track record, are reliably too optimistic. None of these templates state how likely their one date actually is, which is exactly the number a stakeholder needs once that date starts to move.

This pack forecasts from the team's own trailing throughput instead. Broadcom's own documentation for the Rally Delivery Forecast Tool describes the same technique: sample a team's historical throughput thousands of times for a delivery date at a stated confidence level. At Osprey Robotics, a fictional robotics software company, a naive point estimate missed the promised date in 2 of the team's last 6 release commitments. The 85th-percentile forecast missed only once, a 16.7 percent miss rate against the roughly 15 percent an 85th percentile is supposed to miss.

The Capacity Model sheet still runs the roster math, on purpose: for Osprey's 5-person team it predicts 7.48 tickets a week, while the trailing 12-week measured throughput is 5.25, a 29.8 percent gap the roster arithmetic cannot see. The current, unresolved forecast reads P85: 11 weeks against that same window. Built for the engineer defending a date next to the technical program plan tracking the same commitments and the technical risk register covering what happens when one slips.