We’re on the Atlassian Marketplace — planning poker inside Jira.

Get the Jira app →
PP Online Planning Poker
Free Agile Tool

Sprint Capacity Calculator

Calculate your team's real available capacity for the sprint. Factor in PTO, availability, and focus time to plan accurately.

Sprint Settings

30
Total person-days
240h
Available hours
168h
Effective hours
After 70% focus factor

Team Members

Name
Avail. %
PTO Days

Per-member Breakdown

Team Member 1 56h
10d available
Team Member 2 56h
10d available
Team Member 3 56h
10d available

Team Velocity (optional)

Enter your team's average velocity to get a recommended story point target for this sprint.

Estimate sprint work with your team

Use planning poker to agree on story points together.

What is Sprint Capacity Planning?

Sprint capacity planning is the process of determining how much work a development team can realistically complete during a sprint. Rather than assuming everyone is available 100% of the time, capacity planning accounts for holidays, PTO, part-time availability, and the reality that not every working hour is spent on sprint tasks.

The focus factor (also called the capacity factor) represents the percentage of work hours that go toward sprint deliverables. A typical team operates at 70–80%, with the remaining time absorbed by meetings, code reviews, Slack, and unplanned work. Adjusting this keeps your sprint commitments grounded in reality.

Accurate capacity planning helps teams avoid overcommitting, reduces end-of-sprint stress, and produces more reliable velocity data over time — making future planning even more precise.

Frequently Asked Questions

What focus factor should I use?
Most agile coaches recommend starting with 70% as a safe default. Teams with lots of cross-functional work, support rotations, or frequent meetings may run closer to 60%. High-focus teams (e.g. dedicated feature squads with minimal interruptions) may reach 80–85%. Track your actual velocity over a few sprints and adjust your focus factor to match reality.
How does this differ from velocity-based planning?
Velocity-based planning uses your team's historical story point throughput to forecast how much you can deliver. Capacity-based planning is hour-driven and more useful when the team composition or availability changes between sprints. The two approaches complement each other — this tool bridges them by scaling your velocity estimate up or down based on the current sprint's actual capacity relative to a full sprint.
Should I include holidays as PTO days?
Yes — the simplest approach is to set the sprint duration to only include working days (excluding weekends and public holidays), then use each member's PTO days field for any personal time off within the sprint. Alternatively, you can reduce the sprint duration by the number of company-wide holidays and leave PTO days for individual absences.

Plan the Sprint Together

Once you know your team's capacity, use planning poker to size the backlog items as a group — it's free and takes seconds to start.

We use cookies to improve your experience. By continuing to use this site, you agree to our Privacy Policy.