Project Time CalculatorProject Time Calculator

How to Convert Story Points to Hours

A local hours-per-point ratio measured from completed sprints, used only when someone actually needs hours.

Quick answer

Story points are relative size, not hours. If you must convert, pick one ratio from your own recent sprints (hours per point) and multiply. 40 points at 6 hours/point is 240 hours. Do not use someone else’s “industry standard” ratio. Velocity still forecasts sprints; hours are a second view for staffing.

Sprints needed

Sprints = ⌈ backlog points ÷ velocity ⌉.

When a point-to-hour conversion is defensible

Points exist so a team can compare items without pretending they know hours. Converting back to hours is a lossy step. Do it only when a finance or staffing conversation needs hours, and use a ratio you measured: completed hours in a sprint divided by points finished in that sprint, averaged over a few sprints.

Sprints needed still come from velocity, not from hours. The sprint time calculator can show an optional hours view. Count sprints in how to calculate sprint count. Velocity is the definition.

A local ratio, not a universal constant

hours ≈ points × (hours per point)

hours per point ≈ hours completed last sprints ÷ points completed last sprints

Sprints needed remains ⌈ points ÷ velocity ⌉, even after you have hours.

Worked examples

Each example uses numbers you can load into the calculator above; the results match the tool exactly.

Example 1: 80 points, 20 points per sprint, 6 hours per point

Sprints = ⌈80 ÷ 20⌉ = 4. Hours ≈ 80 × 6 = 480 hours. Those hours are a staffing view, not a fourth sprint. Mini-calculator default is 80 points at 20 velocity (4 sprints).

Load this example

Example 2: measuring the ratio

Three sprints finished 18, 22 and 20 points. Recorded project hours were 110, 130 and 120. Hours per point = (110+130+120) ÷ (18+22+20) = 360 ÷ 60 = 6 hours/point. Next sprint’s 21-point forecast is about 126 hours of that team’s time, not 21 × some blog’s “ideal day”.

Load this example

Why borrowed ratios fail

Another team’s “one point = half a day” includes their meetings, their skill mix and their definition of done. Applying it to your backlog silently imports their calendar. Measure yours, or stay in points.

Hours for a finish date

Once you have hours, the task time estimator or the project time calculator can turn them into working days. Mapping sprints onto a calendar is still sprint length × sprints, which the sprint tool already does.

A measured ratio, not a standard

Take the last three to five completed sprints. Sum the hours the team actually spent on finished stories (from the timesheet or the sprint tool, not from the original hour guesses). Sum the points of those same stories. Hours ÷ points is the only ratio worth typing. Example: 240 hours and 80 points → 3 hours per point. A remaining backlog of 50 points is then 150 hours of forecast effort. That effort still has to go through availability and a calendar; it does not replace velocity. Sprints needed remain ceil(remaining points ÷ velocity). If velocity is 20, you still need 3 sprints even if the hour forecast looks like 2.5 weeks of focus time. The hour figure is for a finance or staffing conversation. The sprint figure is for the release conversation. Keep both; do not average them.

When to refuse the conversion

Refuse when the team is new, when point sizes just changed, or when two squads share a backlog with different definitions of a point. In those cases hours-per-point is noise. Estimate remaining work in hours directly, or stay in points. The sprint count guide never needs hours. Optional hours-per-point on the sprint time calculator is a display convenience after you measured a ratio, not a reason to invent one. If a stakeholder insists “industry standard is eight hours per point”, that is a planning fiction; say so and show your measured number or none.

How to convert story points to hours

  1. Do you need hours at all? If not, stop; use velocity.
  2. Sum hours and points from recent completed sprints.
  3. Ratio = hours ÷ points.
  4. Forecast hours = remaining points × ratio.
  5. Keep the sprint count from velocity, not from those hours.

Assumptions, limits and common mistakes

Assumptions and limits

  • The ratio drifts when the team or the type of work changes.
  • Points are not additive across teams.

Common mistakes

  • Using 1 point = 8 hours because a slide said so.
  • Changing point sizes so that hours “add up”. That destroys velocity history.
  • Forecasting sprints from hours instead of from velocity.

Frequently asked questions

How do you convert story points to hours?

Multiply by a ratio you measured from your own completed sprints: hours finished divided by points finished.

Is there a standard hours per story point?

No. Any number you did not measure from this team is fiction.

Should I estimate in hours instead of points?

If the organisation only accepts hours, estimate hours. Do not fake points on top of hours.

How do story points relate to sprints?

Sprints needed = ceil(points ÷ velocity). Hours are optional after that.

Can I put hours on the sprint calculator?

Yes: it has an optional hours-per-point field. Velocity still drives the sprint count.

Where is velocity defined?

On the velocity term page and the sprint-count guide.

Written by . Formulas checked against the site's test suite on 11 November 2026. Last updated 10 November 2026. Formulas and tests: methodology. Report a calculation error.