Story Points per Sprint Calculator

Measure sprint output with capacity and risk inputs. Review velocity trends before setting your commitment. Improve predictability, reduce overload, and align teams around evidence.

Calculator Inputs

The page uses a stacked layout, while the form fields switch to three, two, or one column by screen size.

Total points committed at sprint planning.
Use actual completed points from the sprint.
Unfinished work entering the sprint.
Active contributors included in delivery work.
Count only working days inside the sprint.
Public holidays or shared shutdown days.
Sum of all individual days off.
Available time left after meetings and interruptions.
Average delivery rate for focused work.
Support, bugs, incidents, and urgent requests.
Use lower values for higher uncertainty.
Oldest historical sprint in this model.
Use completed story points for consistency.
Recent values influence the recommendation more.
Latest completed sprint velocity.
Reset

Example Data Table

Sprint Planned Completed Carryover Unplanned Team Size Focus %
Sprint 21 76 64 9 12 6 66
Sprint 22 78 69 7 10 6 67
Sprint 23 80 71 6 9 6 69
Sprint 24 82 74 5 8 6 70

This sample shows how delivery improves when carryover falls and focus time rises.

Formula Used

  • Gross team days = team size × sprint days
  • Available team days = gross team days − (team holidays × team size) − total PTO days
  • Effective focus days = available team days × focus factor
  • Capacity-based points = effective focus days × points per person-day
  • Weighted historical velocity = V1×0.10 + V2×0.20 + V3×0.30 + V4×0.40
  • Safe baseline = lower of capacity-based points and weighted historical velocity
  • Recommended new commitment = (safe baseline − carryover − unplanned work) × confidence factor
  • Predictability = completed points ÷ planned points × 100
  • Carryover rate = carryover points ÷ planned points × 100
  • Capacity utilization = (planned + carryover + unplanned) ÷ capacity-based points × 100

The model combines team capacity and recent delivery history, then applies operational buffers before suggesting a safer commitment target.

How to Use This Calculator

  1. Enter your sprint commitment, actual delivery, and carryover points.
  2. Add team size, sprint length, holidays, and total PTO days.
  3. Set a focus factor that reflects meetings and interruptions.
  4. Enter the team’s normal points per person-day rate.
  5. Estimate expected unplanned work for support and urgent bugs.
  6. Choose a confidence factor based on uncertainty and risk tolerance.
  7. Add the last four sprint velocities to anchor the forecast.
  8. Click the button to see the recommendation, utilization, and graph.
  9. Download the CSV for records or export a PDF snapshot.

FAQs

1. What does this calculator estimate?

It estimates a safer story point commitment for the next sprint. It uses capacity, historical velocity, carryover, unplanned work, and confidence settings to show a practical planning target.

2. Why use weighted historical velocity?

Recent sprints usually reflect the current team better than older ones. Weighting newer data helps the recommendation react faster to staffing changes, process improvements, or rising interruption load.

3. What is a good focus factor?

Many teams start between 60% and 75%. Heavy meetings, support load, or cross-team dependencies usually push it lower. Stable product teams with fewer interruptions may use higher values.

4. Should carryover be included every sprint?

Yes. Carryover consumes capacity before new work begins. Ignoring it can make the team overcommit, inflate predictability problems, and hide recurring planning issues.

5. How should I choose the confidence factor?

Use higher percentages when work is well understood and interruptions are controlled. Use lower percentages when requirements are volatile, estimates are uncertain, or team availability may change.

6. What does capacity utilization show?

It compares total sprint load against estimated delivery capacity. A very high percentage often signals risk, while a healthier number usually indicates a more realistic sprint plan.

7. Can this replace team judgment?

No. It supports planning decisions, but it cannot capture every dependency, discovery task, or quality risk. Teams should still review scope, complexity, and release pressure before finalizing commitment.

8. When should I update the inputs?

Update them each sprint planning session. Refresh historical velocities, current PTO, holidays, expected support load, and focus factor so the recommendation reflects present delivery conditions.

Related Calculators

mean time to recoveryteam capacity calculatorlead time in weeks calculatorsuccess run theorem calculatorbuild-to-suit lease calculator

Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.