Capacity-based Planning
Unlike velocity-based planning, which uses the average of points completed in previous sprints as a direct reference, capacity-based planning first calculates how many hours of effective work are available in the sprint and then allocates work until that capacity is filled without exceeding it.
When to use it

- In sprints with significant variations in availability: vacations, public holidays, training sessions, or new team members joining.
- In teams with high variability in historical velocity, where averages are not representative.
- At the start of a project, when there is no team velocity history.
- In small teams where the absence of one person significantly changes the total capacity.
How to apply it
- Estimate available capacity: Calculate the number of workdays or hours available for each team member during the sprint, accounting for holidays, vacations, recurring meetings, and any other commitments that reduce productive time.
- Break down stories into tasks: Break down the user stories selected for the sprint into individual tasks, each with a time estimate—ideally expressed in hours.
- Assign tasks up to capacity: Assign tasks to each person until their available capacity is reached, without exceeding it. The goal is to align the sprint commitment with what the team can realistically accomplish, rather than what they might wish to achieve.
- Adjust during the sprint: If a task takes longer than estimated, reassign other tasks to compensate; if necessary, negotiate with the product owner to determine which items should be removed from the sprint.
Relationship with velocity
Capacity-based planning and velocity-based planning are not mutually exclusive. Many mature teams combine them: they use historical velocity as a high-level benchmark and available capacity to fine-tune the plan for each specific sprint. Capacity always takes precedence over velocity; for instance, if a team only has 60% of its usual capacity during a given sprint, it cannot commit to 100% of its typical point total.
Common pitfall
Failing to account for non-productive time. It is common to estimate sprint capacity simply by adding up each person’s working days and multiplying by their daily hours. However, meetings, interruptions, refinement work, and administrative tasks significantly reduce the time available for actual development. A realistic capacity estimate accounts for this; an overly optimistic one leads to commitments the team cannot meet.
Resources
📄 Agile Estimation Techniques: Three StrategiesScrum Manager Blog · Jul 2023
🎙️ Ep. 1: Fibonacci Sequence and Agile EstimationScrum Manager Podcast · Spotify
See also
Want to grow in agility? You can search for course and exam calls, or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.