Story points vs hours

If you can convert points to hours, you're estimating hours.

Story points and hours are not different units of the same thing. Hours measure duration — how long something will take you. Points measure relative effort — how big this is compared to the reference story everyone already shipped. They're different axes. The moment you write "1 point = 4 hours" on the wiki, you've re-cast every estimation conversation as a duration argument, and you've thrown away the relative-effort property the technique exists to give you.

The reason teams reach for the conversion is real: someone outside the team needs a date, and points don't have units. The fix isn't a conversion table; it's velocity. Velocity already maps points to time at the team level — points-per-sprint × number-of-sprints gives you a date that respects the team's actual delivery rate, not a fictional rate.

Why points exist at all

The team that estimates in hours is two estimates: the estimate the senior person believes, and the estimate the junior person believes after rounding up to look responsible. Hidden cards plus relative effort dodges both. Points let the team agree on "this is bigger than that one we shipped" without agreeing on "this will take me four hours."

What good looks like

A team using points well doesn't talk about hours during the session. They talk about the reference story, the comparable work they've shipped, and the unknowns. The number that comes out is a relative-effort signal that the team — and only the team — can convert into a date through their own velocity.

Burn the conversion table. Project from velocity instead.

Adjacent: how many points per sprint for the velocity question; common mistakes covers the points-to-hours table as a recurring failure mode.