---
title: "Why are story points preferred over time-based estimates by Developers?"
description: When Developers estimate with time (hours/days), they often encounter variance due to individual skill levels. Story points, by being relative, can absorb some of this variance, making them a more effective tool for estimation. This method recognises that different Developers…
url: "https://www.thescrummaster.co.uk/docs/why-are-story-points-preferred-over-time-based-estimates-by-developers/"
updated: "2024-12-19"
category: Good Practices / Story Points
---

# Why are story points preferred over time-based estimates by Developers?

When Developers estimate with time (hours/days), they often encounter variance due to individual skill levels. Story points, by being relative, can absorb some of this variance, making them a more effective tool for estimation. This method recognises that different Developers might complete the same [Task](https://www.thescrummaster.co.uk/glossary/task/) in varying amounts of time, but the relative complexity and effort required remain consistent.

Using story points encourages group consensus. Because the estimation is not tied to a specific time frame, team members are likelier to converge on a shared understanding of what each story point [Value](https://www.thescrummaster.co.uk/glossary/value/) signifies. This consensus helps streamline future estimation efforts and fosters a more cohesive team environment, as everyone works from a common understanding of the workload and expectations.