Delivery Capacity Planning
Complete Guide to Capacity Planning for Delivery Teams
Introduction to Capacity Planning
Capacity planning is the process of determining how much work a team can complete.
Available capacity equals total time minus non-project time. Non-project time includes meetings, administrative tasks, support duties, training sessions, holidays, and sick leave.
Team velocity is a historical measure of the team’s throughput – it incorporates average story points completed, features delivered, or work done per sprint. Velocity helps predict future capacity.
Velocity-based planning relies on historical velocity. This includes:
Time-based planning uses available time to calculate how much work can be done, estimating work hours, allocating tasks, and managing buffers. Time-based planning provides detailed planning.
Story point planning utilizes relative sizing, estimating story points, using velocity, planning capacity, and tracking progress. Story point planning offers flexible planning.
Frequently asked questions
What is constraint management?
Constraint Management
How does constraint management ensure efficiency?
Constraint management ensures identification of bottlenecks. This includes identifying constraints, managing bottlenecks, optimizing flow, and removing blockers, ultimately enhancing efficiency.
Does historical data guarantee accuracy in planning?
Historical data guarantees accuracy by tracking velocity, analyzing trends, learning from experience, and adjusting estimates. This results in realistic planning.
What is the purpose of accounting for non-project work?
Accounting for non-project work ensures a more accurate assessment of available capacity by factoring in time spent on tasks outside core project activities.
▶ Try it live
Everything above runs in your browser — open Hash Function Avalanche Visualizer and change the parameters while it is running. Nothing is installed, nothing is uploaded, the whole model lives in one tab.