Team Capacity Planner
Calculate your team's actual coding capacity. Account for meetings, holidays, and other overhead to plan sprints realistically.
Team Configuration
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.
Want to track this automatically?
CodePulse connects to your GitHub and calculates these metrics in real-time. No more manual data entry or spreadsheets.
Free tier available. No credit card required.
Related Tools
Meeting Cost Calculator
See the true cost of meetings for your engineering team. Calculate how much engineering time and money is spent in meetings.
Cycle Time Calculator
Calculate your PR cycle time breakdown. See where time is spent between coding, waiting for review, in review, and merging.
Code Review Time Estimator
Estimate how long code reviews should take based on PR size and complexity. Set realistic review SLAs for your team.