How much work can my team complete in a sprint?

The most accurate answer comes from your own historical velocity, not a formula. Track completed story points over 3-5 sprints and use the average as your baseline. New teams without history should start conservative (60% of calculated capacity) and adjust after each sprint. Remember that velocity naturally varies—a range (e.g., 40-50 points) is more realistic than a single number.

Why is my team consistently missing sprint commitments?

The most common cause is underestimating overhead. Teams often plan for 100% coding capacity when reality is closer to 50-60%. Other culprits include: not accounting for unplanned work (typically 15-25% of capacity), ignoring context-switching costs between tasks, and optimistic estimation bias. Track where time actually goes for 2-3 sprints before adjusting your capacity calculations.

All Free Tools

For Engineering Managers3 min

Team Capacity Planner

Calculate your team's actual coding capacity. Account for meetings, holidays, and other overhead to plan sprints realistically.

Over 70% of engineering teams consistently miss sprint commitments—not because they're slow, but because they plan for 100% capacity that doesn't exist. This calculator helps you determine realistic capacity based on actual overhead factors.

Our Take

Sprint planning that ignores maintenance load and unplanned work is planning to fail. Elite teams account for 20-30% capacity loss to operational work.

The teams that consistently deliver aren't the fastest coders—they're the best estimators. They know exactly how much capacity meetings, code reviews, support escalations, and context switching consume. Most teams underestimate overhead by 30-40%, leading to chronic over-commitment and burnout.

"Teams that track actual vs. planned capacity improve estimation accuracy by 35% within 3 sprints."
— Software Engineering Management Research, 2023

Team Configuration

Number of EngineersHow many people on your team?

Sprint Length (days)Duration of your sprint or iteration

Working Hours per DayStandard work day length

Meeting Overhead (%)Standups, planning, retros, 1:1s, etc.

PTO/Holidays During SprintTotal days off across the entire team

days

Other Overhead (%)Code reviews, on-call, support tickets, context switching

Team Velocity RatingUsed for story point estimation

Enter the number of engineers above to calculate your team's capacity.

Capacity Planning Tips

Common Capacity Planning Mistakes

- Over-committing by ignoring meeting time (the "100% capacity" trap)
- Not accounting for context switching costs between tasks
- Forgetting about unplanned work (bugs, support escalations)
- Using the same capacity for all sprint types (planning sprints need more time)
- Not adjusting for holidays or team members ramping up

Tips for Protecting Maker Time

- Designate "no meeting" blocks or days for deep work
- Batch meetings together to minimize context switching
- Set realistic on-call rotations that don't fragment everyone's week
- Build in buffer time (10-15%) for unexpected work
- Track actual vs. planned capacity over multiple sprints to calibrate

Low Velocity

8-10 hours per story point. Use for new teams, unfamiliar codebases, or high-uncertainty work.

Medium Velocity

5-7 hours per story point. Use for established teams with familiar patterns and processes.

High Velocity

3-5 hours per story point. Use for experienced teams with well-defined, routine work.

Frequently Asked Questions

Sprint capacity is calculated by multiplying the number of engineers by available work days by hours per day, then subtracting overhead. A typical formula: (Engineers x Days x Hours) - Meetings - PTO - Other Overhead = Effective Capacity. Most teams end up with 50-65% of theoretical capacity available for coding. Use your actual historical data from 3-5 sprints to calibrate estimates rather than relying on industry averages.

Want to track this automatically?

CodePulse connects to your GitHub and calculates these metrics in real-time. No more manual data entry or spreadsheets.

Try CodePulse Free View Pricing

Free tier available. No credit card required.

Related Tools

2 min

For Engineering Managers

Meeting Cost Calculator

See the true cost of meetings for your engineering team. Calculate how much engineering time and money is spent in meetings.

Try it free

3 min

For Engineering Managers

Cycle Time Calculator

Calculate your PR cycle time breakdown. See where time is spent between coding, waiting for review, in review, and merging.

Try it free

2 min

For Engineering Managers

Code Review Time Estimator

Estimate how long code reviews should take based on PR size and complexity. Set realistic review SLAs for your team.

Try it free