Story Point Estimate Calculator
Story points measure relative effort, not time, so they only become a schedule when combined with your team's velocity. This calculator takes a total point count, your velocity per sprint, your sprint length, your average hours per point, and a blended hourly rate, then projects the sprints, calendar weeks, total hours, and rough labour cost to deliver. Every input is editable so the forecast reflects your team, not generic assumptions.
Story point formula
sprints needed = ceil( total points / velocity )
calendar weeks = sprints needed * sprint length
total hours = total points * hours per point
labour cost = total hours * hourly rate
Sprints are rounded up because you cannot finish a partial sprint. Total hours and cost come from your hours-per-point figure, which should reflect your team's actual experience.
Worked example
For 80 points, a velocity of 20, 2-week sprints, 6 hours per point, and a 90 dollar rate: sprints = ceil(80 / 20) = 4. Calendar weeks = 4 * 2 = 8. Total hours = 80 * 6 = 480. Labour cost = 480 * 90 = 43,200.00 dollars.
Story points: frequently asked questions
What is a story point?
A story point is a unit of relative effort used in agile estimation. Rather than estimating hours, teams compare items to each other and assign points, often on a scale like 1, 2, 3, 5, 8. Points capture effort, complexity, and uncertainty together. They become a schedule only when combined with the team's velocity.
How do I turn story points into time?
Divide the total points by your velocity, the points completed per sprint, to get the number of sprints. Multiply by sprint length for weeks. If you also know your average hours per point, multiply total points by that to estimate total hours of effort. Velocity should come from your own past sprints.
Why not just estimate in hours?
People are poor at estimating absolute durations but better at judging whether one task is bigger than another. Story points lean on that relative judgement and absorb uncertainty. Over several sprints, a stable velocity translates points into reliable delivery forecasts without re-estimating every item in hours.
How is the labour cost estimated?
Total hours (points times hours per point) multiplied by a blended hourly rate gives a rough labour cost. It is a planning figure only and ignores overhead, tooling, and non-development costs. All inputs are editable so you can model your own team's numbers.
Sources and method
- Story points and velocity are standard agile concepts; velocity and hours per point should come from your own sprints, so both are editable inputs.
- The projection is direct arithmetic on your inputs and is computed exactly by this tool.
Reviewed by the CalculatorHub team, edited by James Graham, 19 June 2026. See our methodology.