Sprint Capacity Calculator
Enter your team's availability and velocity to get a realistic sprint commitment in story points. No login required.
Sprint Length
Team Members
| Name | Days available(of 10) | Velocity(pts/day) | Capacity | |
|---|---|---|---|---|
| 16 pts | ||||
| 16 pts |
Max Capacity
32
story points
Recommended (80%)
26
story points
Team Availability
80%
16/20 days available
How to use these numbers
Max capacity is the theoretical ceiling if everything goes perfectly. It never does.
Recommended (80%) accounts for code reviews, unplanned meetings, small bugs, and the work that always appears mid-sprint. Commit to this number, not the max.
Velocity (pts/day)varies by role and seniority. A reasonable default is 2 pts/day for a developer. Adjust based on your team's historical sprint data.
How should we improve Sprint Capacity Calculator?
Quick votes help decide what to build next. Detailed requests can send your written note to the backlog.
Frequently Asked Questions
What is sprint capacity?
Sprint capacity is the total number of story points a team can realistically complete in a sprint, based on team size, availability, and individual velocity. It sets the upper bound for what to commit to in sprint planning.
Why plan to 80% of capacity?
Planning to 100% assumes no interruptions, no code reviews, no unplanned bugs, and no meetings overrunning. None of those assumptions are true. The 80% buffer accounts for the inevitable reality of a sprint. Teams that plan to 100% consistently carry work over.
What should I set as velocity per day?
A common default for a developer is 2 story points per day. However, the most accurate number comes from your own team's history: take the total points completed in your last 3 sprints, divide by total developer-days available, and use that as your per-person velocity.
How do I account for meetings and ceremonies?
Reduce the 'days available' for each person by the time ceremonies consume. For a 2-week sprint, sprint planning, review, retro, and daily standups typically consume 1–1.5 days per person. So a 10-day sprint might have 8.5 effective development days per person.
Is this tool free?
Yes, completely free. No account or login required. All calculations happen in your browser.