Many teams struggle with estimation because they approach it as a conversation about time. The moment a team starts asking whether something will take eight hours, three days, or two weeks, the discussion often becomes slow, frustrating, and filled with uncertainty. People begin defending opinions, debating details, and trying to predict every possible challenge before work even begins.
Relative estimation creates a much healthier conversation because it shifts the focus away from exact hours and toward comparing work against other work the team already understands. Instead of asking, “How long will this take?” teams ask, “Is this bigger, smaller, or about the same as something we have done before?” That is a much easier question for people to answer.
The reason relative estimation works so well is because humans are naturally better at comparing than predicting. Most people cannot accurately tell you how many hours a piece of work will take, especially when there are unknowns involved. However, they can usually tell you whether one item feels twice as large as another or whether one story is much more complex than something the team has completed in the past.
Relative estimation also creates stronger team conversations. When a team is discussing story points, T shirt sizes, or another relative model, they are forced to talk about complexity, uncertainty, risk, dependencies, and effort. Those are the factors that really matter. The purpose of estimation is not to produce a perfect number. The purpose is to create a shared understanding of the work.
One of the most effective estimation activities is to use a reference story approach. Teams first identify a small, well understood piece of work and agree that it is a certain size. For example, they may decide that a simple enhancement is a 2. Once that reference point exists, future work becomes easier to compare. Teams can then ask whether a new item feels like another 2, something closer to a 5, or perhaps a much larger 8.
Another great approach is an estimation wall activity. Teams place work items on a wall or virtual board from smallest to largest without assigning numbers at first. This creates a more visual conversation and helps people think about work in relative terms rather than immediately jumping into debates over exact sizing. Once the work is arranged, the team can apply story point values or T shirt sizes to the items.
Relative estimation is also valuable because it supports predictability over time. Teams that estimate consistently begin to understand how much work they can realistically complete in a sprint or iteration. Velocity becomes more meaningful because it is based on the team’s own relative sizing model rather than arbitrary hour estimates that often change.
This does not mean estimation becomes perfect. No estimation method can eliminate uncertainty. Unexpected issues, changing priorities, and hidden complexity will always exist. However, relative estimation gives teams a faster, healthier, and more effective way to understand work and plan realistically.
At The Agilist, we often encourage teams to treat estimation as a conversation tool rather than a commitment tool. The goal is not to create pressure around exact numbers. The goal is to help teams build a shared understanding of work, uncover risk early, and make better planning decisions together.
