Battlecard: We Should Just Estimate in Hours
Use a short response that preserves relative estimation while still giving stakeholders a forecast answer.
Story points feel vague. If we estimated every story in hours, stakeholders would finally know what the sprint really costs and the team would stop hiding behind points. I get why hours sound clearer, but they create a false sense of certainty before the work is fully understood. We estimate in story points so the team can compare effort, complexity, and uncertainty consistently. Then we turn that into a planning forecast using recent throughput and the current sprint capacity. That gives stakeholders the answer they actually need, which is the likely sprint slice, without pretending every story already has an…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in