Why is our team struggling to move from Story Points to actual hours for task estimation?

All answers to this question.

If you use Story Points, how do you handle the situation where two developers have different experience levels and would take different times for the same task?

   Answered 2024-03-10 by Mark Taylor

• Mark, that is exactly why points are better! The "complexity" of the task remains the same regardless of who does it. A senior might do a 5-point story in 2 hours and a junior in 8 hours, but the "5 points" helps the team understand the total volume of work they can handle collectively, regardless of the individual assignment.

     Commented 2024-03-15 by Robert Evans

We stopped showing hours to leadership entirely and only reported on "Value Delivered" and "Sprint Burn-down" trends. Eventually, they stopped asking for hours.

   Answered 2024-03-20 by Jennifer Harris

• Jennifer’s approach is bold but effective. Shifting the conversation to "Outcome" instead of "Output" (hours) is the ultimate goal of a mature Agile organization.

     Commented 2024-03-22 by Brian Collins

Relative estimation is designed to account for the "known unknowns." When you estimate in hours, humans are notoriously bad at accounting for interruptions, meetings, and cognitive load. I always use the "Travel Analogy" with my stakeholders: it’s easier to agree that a trip to the moon is a "Size XL" and a trip to the grocery store is a "Size S" than it is to estimate the exact minutes each will take. Story Points allow the team to build a consistent velocity over time, which actually provides better long-term predictability than hourly estimates that are almost always wrong.

   Answered 2025-03-05 by Patricia Moore