Relative Estimation
Relative Estimation is an Agile technique which Scrum Teams often use, where teams assess the effort or complexity of work items by comparing them to each other, rather than assigning exact hours or days. It's less about numbers and more about building a shared understanding of the work.
Instead of asking "How long will this take?", the team asks "Is this more or less effort than that other item we already discussed?"
A simple example:
Imagine you're packing for two trips:
- A weekend getaway
- A two-week vacation
You don't know exactly how many items each trip needs, but you clearly understand one involves more effort than the other. If the weekend trip is a 1, the longer trip might be a 3 or a 5 based on the added complexity, not precise measurement.
Why it works
The true value of estimation lies not in the number itself, but in the conversation behind it. Estimation sessions help teams surface assumptions, uncover hidden knowledge, and align perspectives. These discussions are often more useful than the final estimate.
When estimates differ, it's not a problem---it's a signal. It shows that team members understand the task differently, and it opens up space to ask "What do you know that I don't?"
Benefits of Relative Estimation
- Promotes shared understanding and team alignment
- Helps identify risks and hidden complexity early
- Supports faster, more adaptive planning
- Avoids false precision by focusing on relative size
Relative Estimation isn't about being exact---it's about getting clear, together.