Sprint Capacity Calculator
Calculate the total available work hours for your Agile team in an upcoming sprint by entering team size, daily working hours, and sprint length. Use this during sprint planning to set realistic commitments and avoid overloading the team.
About this calculator
Sprint capacity is the maximum number of productive hours a team can contribute during a fixed sprint period. The formula is: Capacity (hours) = teamMembers × hoursPerDay × sprintDays. For instance, a team of 5 working 6 hours per day over a 10-day sprint has a capacity of 300 hours. This raw number should then be adjusted downward for planned absences, meetings, and a capacity buffer (typically 20%) to arrive at a realistic commitment figure. Knowing capacity in advance prevents the common pitfall of pulling in more story points than the team can actually deliver. In Scrum, this calculation is performed at the start of every sprint planning session and forms the ceiling against which the product backlog items are sized.
How to use
Suppose your team has 6 members (teamMembers = 6), each working 7 hours per day (hoursPerDay = 7) during a 2-week sprint of 10 working days (sprintDays = 10). The calculator computes: 6 × 7 × 10 = 420 hours of raw capacity. Applying a typical 20% buffer for meetings and overhead gives 420 × 0.8 = 336 committed hours. Use 336 hours as your ceiling when selecting backlog items for the sprint to maintain a sustainable pace.
Frequently asked questions
How do I account for team member absences when calculating sprint capacity?
Before running the full formula, subtract unavailable days per person from sprintDays for each individual. For example, if one team member is on leave for 2 days, treat their personal sprint days as 8 rather than 10. Sum each member's available hours separately, or simply reduce the effective team-member count proportionally. Many Scrum teams maintain a capacity spreadsheet that tracks individual availability and feeds an adjusted total into the sprint planning discussion.
What is a realistic hours-per-day figure to use in sprint capacity planning?
Although a workday is typically 8 hours, most Agile practitioners use 6–7 hours of productive time per developer after accounting for standups, code reviews, slack messages, and context switching. Using the full 8 hours as your input consistently leads to overcommitment and unfinished sprint goals. A conservative estimate improves predictability and team morale over time. Calibrate this number by reviewing your team's actual velocity over the previous three to five sprints.
How does sprint capacity differ from sprint velocity in Agile project management?
Capacity is a forward-looking measure of available hours before a sprint begins, while velocity is a backward-looking measure of story points actually completed in past sprints. Capacity helps you decide how many items to pull in; velocity helps you predict how many points you will deliver. Both metrics are needed for effective sprint planning: capacity sets the time ceiling and velocity translates that ceiling into story-point commitments. Teams often use velocity to validate whether their capacity calculation is realistic based on historical throughput.