Agile Capacity Planning: A Practical Guide

What is agile capacity planning?

Capacity planning is about answering one practical question before sprint planning begins: how much delivery time does the team actually have?

A team might look like it has 10 working days per person in a sprint. In reality, people are often away, in meetings and doing other work that reduces the time available for delivery.

A simple capacity flow

This is the heart of capacity planning. The goal is to turn theoretical team time into a realistic delivery estimate.

Step 1: Review team availability

Start by listing the people who should contribute to the sprint and the working days they are expected to have.

• Who will be available?
• How many working days do they have?
• Who is taking leave?
• How much time will be spent in meetings?
• Is anyone supporting another project?
• Are there known interruptions or operational responsibilities?

Do not assume every team member is equally available. Leave, holidays, support work and overlapping tasks all affect the real capacity of the sprint.

Step 2: Remove planned time away from delivery

After measuring the team's working time, subtract what will not be available for delivery work.

• Annual leave
• Public holidays
• Training
• Other planned work
• Personal commitments

This is where teams often become more realistic. The total working days in the sprint are not the same as the time available for meaningful sprint work.

Step 3: Account for meetings and planned work

Delivery time is also reduced by recurring activities that are not directly writing code or completing backlog items.

• Scrum ceremonies
• Backlog refinement
• Stakeholder meetings
• Support work
• Technical discussions
• Organisational activities

Once the team accounts for those activities, it has a more useful estimate for the sprint.

Example: realistic capacity

Imagine a team of four people in a 10-day sprint.

4 × 10 = 40 person-days

During the sprint:

• 2 days of leave for one developer
• 1 day of leave for another developer
• 1 day of leave for QA
• 4 person-days of planned support work and meetings

Estimated delivery capacity:

40 - 2 - 1 - 1 - 4 = 32 person-days

That gives the team a realistic starting point for deciding what work to plan.

Capacity planning and sprint planning

Capacity planning is not a promise that the team will deliver a specific amount of work. It is an input to the planning conversation.

The team still needs to consider priorities, dependencies, complexity and uncertainty before finalising the sprint plan.

A team with strong capacity can still struggle if the sprint includes high-risk work, unclear requirements or significant external dependencies.

Why it matters

Without capacity planning, teams often overestimate what they can complete. That creates overload, late delivery and unnecessary sprint pressure.

A simple estimate of actual available team time makes planning more honest and more useful.