Skip to content
Sumly

Sprint Capacity & Velocity Planner

Calculate engineering sprint capacity and recommended story point commitments.

Team & sprint availability
Standard: 10 days (2 weeks)
Cumulative vacation across team
Team point conversion benchmark
Standups, planning, retro, reviews
Productive coding vs context switching
Sprint commitment target
Recommended Commitment

33 Story Points

With 15% buffer against rollover
Max Capacity38 pts
Net Dev Hours230 hrs
Gross available time:384 total person-hours

How Sprint Capacity & Velocity Planner works

Calculates gross team hours from sprint days and headcount minus PTO holidays.

Deducts meeting overhead (standups, refinement, retros) and applies a focus factor.

Translates net productive hours into recommended story point commitment targets.

Worked example

A 5-engineer team in a 2-week sprint with 2 PTO days and 20% ceremonies has capacity for ~40 story points.

The tool above opens with these numbers. Change them to run your own scenario, or press Reset to come back to this example.

Frequently asked questions

A 25/5 focus timer that counts your pomodoros as you bank them.

What a recurring meeting really costs — per session and per year.

Count real working days between two dates — weekends and holidays out.

Turn estimated hours into a defensible project price.

Add working days, weeks or months to a kickoff date.

One time in one zone, translated to twelve cities at once.

  • scrum
  • sprint
  • capacity
  • agile
  • velocity
  • productivity