#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
🏃 FREE · CAPACITY + FORECAST

Sprint Velocity Calculator: Plan Sprints on Real Data

Enter completed points from recent sprints and your team's availability to plan the next sprint and forecast the release.

  • 📊 Rolling average
  • 🏖️ Leave-adjusted capacity
  • 📅 Release forecast

How to use the Sprint Velocity Calculator

  1. 1. Enter past sprintsStory points completed in each recent sprint, oldest first.
  2. 2. Describe next sprintSprint length, team size and person-days of leave or holidays.
  3. 3. CalculateSee velocity, a suggested commitment, and when the remaining backlog should be finished.

How velocity is used

Velocity is the number of story points a team finishes in a sprint, counting only work that meets the Definition of Done. The calculator averages the last three sprints, which reacts to change but smooths out one-off spikes, and shows the range. It then scales that by next sprint's capacity: if 4 of 60 person-days are lost to leave, the team plans for 93% of its usual output. Variation between sprints tells you how far to trust forecasts. Everything runs in your browser; nothing you enter is uploaded.

For a release, dividing the remaining points by the average, the best and the worst recent sprints gives a likely date and a range, counting working days only.

Worked example

A team of 6 completed 32, 28, 35, 30, 34 and 31 points in two-week sprints. Its velocity over the last three sprints is 31.7 points (range 30–34), and sprints vary by about 8%, which is very stable. Next sprint has 4 days of leave, so capacity is 56 of 60 person-days (93%) and the suggested commitment is 30 points. With 180 points left, the backlog needs 6 sprints; starting on 11 January 2027, the forecast finish is 2 April 2027.

Pitfalls

  • Don't count partly done stories; carry them over and count them when finished.
  • Don't use velocity to rank people or teams, or estimates will quietly inflate.
  • After a big team change, give the average three sprints to settle.

Frequently asked questions

How many past sprints should I enter?

At least three; six or more makes the variation figure meaningful.

Does it handle public holidays?

Enter them as leave (holidays × team size). The forecast date counts Monday to Friday only.

Is the sprint velocity calculator free?

Yes. You can open the sprint velocity calculator and fill in everything without signing up. When you calculate velocity for the first time, we ask once for your name and WhatsApp number; after that it, and every other Uncodemy tool, opens straight away.

More free tools

See all free tools