Story Point To Hours Calculator

Work out story point to hours instantly with clear inputs, formula shown and shareable results.

About Story Point To Hours Calculator

Story points are deliberately unitless, but a conversion is sometimes needed for budgeting. Deriving hours per point from the team's own velocity and capacity — using six productive hours per person-day rather than eight — keeps the conversion grounded in observed reality.

Formulas

Sprint capacity

Capacity hours = Team size x Sprint days x 6 productive hours

Hours per point

Hours per point = Sprint capacity hours / Team velocity

Worked example

With the default values below, Story Point To Hours Calculator returns Estimated hours of 242.9. Change any input above and every figure here is recalculated in your browser.

Inputs used

Story points to convert: 34
Team velocity per sprint: 42
Sprint length: 10 days
Team members: 5

Results

Estimated hours: 242.9
Hours per story point: 7.14
Sprints required: 0.81
Sprint capacity in hours: 300

Step by step

1Values used
2Sprint capacity
3Hours per point
4Estimated hours= 242.9
5Hours per story point= 7.14
6Sprints required= 0.81
7Sprint capacity in hours= 300

Assumptions and limits

The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

Doesn't converting points to hours defeat the purpose?

For planning within the team, yes. For an external budget conversation it is often unavoidable — just never use the conversion to hold the team to hourly estimates.

Why six productive hours a day?

Because meetings, code review, support and context switching consume the rest. Teams that plan on eight consistently overcommit.