A damaging mistake during Sprint Planning is committing to story point volumes based solely on historical average velocity, ignoring actual team availability over the coming iteration. Vacations, public holidays, technical training, and tier-3 production support fluctuate every sprint. Systematic Agile Capacity Planning provides the mathematical framework needed to prevent chronic over-commitment.
Theoretical vs Actual Capacity: Key Distinction
Effective sprint planning requires distinguishing between two core concepts:
- Historical Velocity: The average story point volume delivered across recent sprints.
- Net Available Capacity: The actual engineering person-days available for the upcoming sprint.
Agile Planning Golden Rule: Historical velocity establishes baseline expectations, but net available capacity defines the hard ceiling for upcoming sprint commitments.
Step-by-Step Capacity Calculation Guide
Calculate net capacity in person-days (or hours) across three steps:
Step 1: Compute Baseline Gross Person-Days
For a 5-person engineering squad executing a 10-day sprint, theoretical gross capacity equals:
5 engineers x 10 working days = 50 person-days
Step 2: Deduct Scheduled Absences and Time-Off
- One engineer takes 3 days vacation: -3 days.
- One regional public holiday impacts the team: -5 days.
- One team member attends a 2-day security workshop: -2 days.
Gross Available Capacity = 50 - 3 - 5 - 2 = 40 person-days.
Step 3: Apply the Team Focus Factor
No engineering team codes 8 full hours a day without operational overhead. Ceremonies, email, ad-hoc architectural discussions, and production support consume time. A mature Scrum team's Focus Factor typically ranges between 0.65 and 0.80 (meaning 65% to 80% of working hours directly advance sprint stories).
Net Working Capacity = 40 available days x 0.70 Focus Factor = 28 net person-days.
Converting Net Capacity into Story Point Commitments
| Planning Metric | Historical Baseline | Upcoming Sprint Forecast |
|---|---|---|
| Net Capacity | 35 person-days | 28 person-days (Reduced availability) |
| Average Delivered Velocity | 40 Story Points | --- |
| Points / Person-Day Ratio | 40 / 35 = 1.14 pts/day | --- |
| Target Commitment | --- | 28 x 1.14 = 32 Story Points |
Using capacity-adjusted forecasting, the squad commits to 32 story points rather than their standard 40 points, successfully preventing sprint goal failure caused by planned outages.
4 Best Practices for Sustained Capacity Balance
- Never schedule to 100% of net capacity: Retain a 10% to 15% emergency buffer to absorb urgent production bugs without failing sprint commitments.
- Re-evaluate Focus Factors during retrospectives: If non-sprint interruptions increase, temporarily reduce your focus factor multiplier down to 0.60 while addressing process friction.
- Keep story point estimates constant: Story point values reflect effort complexity and remain fixed. You adjust total sprint point capacity downward to match reduced team availability.
- Sync member schedules centrally: With Manifst Team Management, member availability and capacity limits sync natively with sprint planning boards.
Try Manifst for free: integrated capacity tracking and sprint planning →