Seasonal Capacity Planner

I'll just say it: constant-capacity planning is a fiction that causes real damage. Teams don't operate at the same level year-round. They just don't. Vacations pull capacity down to maybe 60% in August. December holidays chop off another chunk. A new hire in Q2 adds headcount but subtracts productivity for weeks while they ramp up. And yet — I see this constantly — roadmaps commit the same scope every quarter as if none of this is happening. The result is predictable: teams over-commit in low-capacity periods, miss deadlines, burn out trying to catch up, and then stakeholders lose trust. The next quarter, people pad estimates defensively while stakeholders discount them preemptively, and now nobody trusts anybody's numbers. It's a doom loop. Seasonal capacity planning breaks it by making the variation visible. When you can show a chart that says "our effective capacity in Q3 is 37 items, not 50," the conversation changes. Stakeholders stop asking "why can't you do more?" and start asking "which 37 items should we prioritize?" That's a much healthier conversation. And the team starts making commitments they can actually keep — which rebuilds trust faster than any agile transformation initiative ever could.

Three things multiply together to give you adjusted capacity. First: base throughput. This is what your team delivers in a normal period — no holidays, no disruptions, standard staffing. Calculate it from historical data by averaging several stable periods. Don't include the sprint where half the team had COVID or the one where you shipped that massive feature — use boring, representative sprints. Second: team size ratio. If your baseline was established with 5 people and you now have 6, the ratio is 1.2. But here's the thing people miss — capacity doesn't scale linearly. Adding a person adds communication overhead, onboarding costs, and context-switching. A team of 6 isn't 20% more productive than a team of 5. It's more like 10-15% more, depending on the work. Third: seasonal factor. This is where you account for reality. August with summer vacations? Maybe 0.75. A sprint with a company all-hands eating 2 days? Maybe 0.85. A focused delivery sprint with no meetings? Maybe 1.1 (yes, this is possible — I've seen it exactly once). Multiply all three and you get adjusted capacity. A team that normally does 50 items with 5 people, now at 6 people, in August? That's roughly 50 times 1.2 times 0.75 — about 45 items. Not 60.

Perfect balance between capacity and demand is impossible and not even worth pursuing. There will always be gaps. The goal is to see them coming and manage them deliberately instead of discovering them mid-sprint. For deficit periods — where demand exceeds what you can deliver — you've got a few options, roughly in order of preference. First: shift work to adjacent periods. If Q3 is a deficit and Q2 has surplus, front-load some Q3 deliverables into June. This is free, requires no hiring, and works surprisingly well if you plan it early enough. Second: negotiate scope with stakeholders. Show them the capacity chart. Let them choose what to defer. This feels awkward but it's actually empowering — stakeholders prefer making informed trade-offs to receiving surprise delays. Third: add temporary capacity. Contractors, borrowed engineers from another team, focused overtime. Use this sparingly — it's expensive and creates sustainability risks. For surplus periods — and yes, those exist — don't just coast. Invest the extra capacity in things that improve future periods: pay down technical debt that's been slowing you down, run cross-training sessions, experiment with process improvements, or pull forward work from upcoming high-demand months. The worst thing you can do with a surplus is waste it on low-value busywork just to look busy.

Do a big-picture capacity review quarterly, looking 2 to 4 quarters ahead. This is where you catch the macro stuff — the summer slowdown, the Q4 hiring ramp-up, the holiday crunch. Present it to stakeholders so they're not blindsided when you tell them Q3 scope needs to shrink. Then update monthly as reality unfolds. Actual throughput data comes in, the forecast sharpens, and you can adjust before things go sideways. Compare plan versus actuals every month — if you consistently overestimate August capacity, lower the seasonal factor next year. Learn from your own data. Before each quarter starts, do a final review with stakeholders to confirm scope, priorities, and any active capacity-demand gaps. This is your last chance to negotiate before the quarter begins. Much better than renegotiating mid-sprint, which everyone hates. After each quarter, spend 15 minutes doing a capacity retro. How accurate was the plan? Where were the biggest surprises? Were seasonal factors right, or do they need tuning? This iterative loop — plan, execute, compare, adjust — gets more accurate every cycle. I've seen teams go from 30% forecast error to under 10% within a year just by consistently following this cadence (this matters more than you think). The transparency also builds stakeholder trust, because they can see the methodology and the historical accuracy, not just a number someone made up in a planning meeting.