I am planning a year-long infrastructure rollout. My management wants a high-confidence resource plan for the next 12 months. I feel that Waterfall’s upfront estimation is a lie, but Agile’s "Velocity" is too short-term for a yearly budget. How do I balance these two to give a realistic capacity plan?
3 answers
Use "Buffer Management." I always plan my capacity at 80%. That extra 20% acts as a shock absorber for the inevitable "Agile pivots" or emergency bugs.
In 2023, the industry is moving toward "Hybrid Capacity Planning." You use Waterfall for the Macro-level (Monthly buckets of hours based on historical averages) and Agile for the Micro-level (Bi-weekly sprint tasks). Don't try to promise who will be doing what in Month 9. Instead, promise a "Total Full-Time Equivalent" (FTE) count. This gives the budget-holders the cost certainty they need while giving you the flexibility to swap specialists in and out as the Agile sprints evolve.
How do you handle "Resource Contention" when three different project managers are all claiming the same Senior Engineer for their Macro-plans?
James, to answer that, you need a "Centralized Resource Heatmap." We hold a monthly "Resource Sync" where all PMs lay out their Macro-plans on one board. If the Senior Engineer is at 150% capacity, the PMO (Project Management Office) makes the call on which project takes priority. It stops the "he who shouts loudest" method of resource grabbing and forces a strategic decision based on the company's ROI goals.
80% is the magic number, Susan. Any PM who plans for 100% capacity is essentially planning for a project delay the moment someone gets a cold.