Relative Estimation

Relative Estimation is the practice of sizing a backlog item by comparing it against other items whose relative effort is already understood, rather than attempting to state its size in absolute units of time such as hours or days. Instead of asking how many hours an item will take, relative estimation asks how much bigger or smaller it is compared to a reference item, producing a size expressed in comparative terms that remains meaningful even though it deliberately avoids committing to a specific duration.

Why Compare Rather Than Measure Absolutely

Comparative Judgment Is Often More Reliable

People are generally better at judging whether one thing is roughly twice as large as another than at accurately predicting an absolute duration, since comparison relies on a more intuitive, less error-prone kind of reasoning than precise time forecasting.

Absolute Estimates Are Vulnerable to Individual Variation

A task's actual duration in hours depends heavily on who performs it, their familiarity with the relevant code, and countless situational factors, making absolute time estimates unstable across different team members, whereas relative size judgments about complexity and volume tend to hold steadier regardless of who is doing the comparing.

How Relative Estimation Works in Practice

Establishing a Reference Point

The team selects a previously completed item of well-understood size to serve as a baseline, against which new items are judged as larger, smaller, or roughly equivalent.

Assigning Comparative Values

Using a chosen scale — often a sequence of increasing values — the team assigns each new item a value reflecting its size relative to the reference point and to other already-sized items, building a consistent, internally coherent set of comparisons over time.

Translating Relative Values into Planning Usefulness

Although relative values do not directly state a duration, tracking how many total relative units the team completes per iteration allows those values to be translated into a practical planning tool once enough historical data accumulates.

Common Scales Used for Relative Estimation

Modified Fibonacci-Like Sequences

A sequence of increasing numbers with widening gaps at higher values reflects the reality that precision becomes less meaningful and less necessary as items grow larger, since exact distinctions between very large items matter less than between small ones.

T-Shirt Sizing

Using coarse labels such as small, medium, and large offers an even simpler relative comparison, particularly useful for early-stage or very high-level estimation where fine-grained precision is neither possible nor valuable.

Advantages Specific to Relative Estimation

Stability Across Individual Differences

Because the comparison focuses on relative size rather than a specific person's expected completion time, relative estimates tend to remain more consistent even as the mix of people working on similar items changes over time.

Faster Estimation Sessions

Comparing an item against known reference points is typically quicker than attempting to reason through a detailed absolute time calculation, since the comparison draws on intuitive pattern recognition rather than exhaustive analysis.

Visualizing Comparative Sizing

Each new item's box size and assigned value is judged relative to the established reference item, producing a consistent set of comparative sizes rather than independent absolute time estimates.

Common Pitfalls

Anchoring Too Rigidly to a Single Reference

Relying exclusively on one original reference item without periodically checking newer estimates against a broader, evolving set of comparisons can allow drift or inconsistency to creep into the relative scale over time.

Reverting to Time-Based Thinking Mid-Discussion

Team members sometimes slip back into estimating in hours during a relative sizing discussion, undermining the intended comparative approach and reintroducing the instability relative estimation is meant to avoid.

Treating Relative Values as Directly Convertible to Time

Assuming a fixed, precise conversion between relative size and actual hours, rather than allowing the relationship to emerge gradually from observed team throughput, misapplies the technique's underlying logic.

Benefits of Relative Estimation

Reduced Estimation Bias from Individual Speed

Because relative estimation focuses on comparative size rather than a specific individual's expected completion time, it produces steadier estimates even as team composition changes.

Faster, More Confident Estimation Sessions

Comparative judgments are generally quicker and less contentious to reach agreement on than detailed absolute time predictions, speeding up refinement and planning discussions.

A Durable Basis for Long-Term Planning

Once enough historical data accumulates, relative size values combined with observed team throughput provide a practical, empirically grounded basis for forecasting delivery timelines without requiring precise absolute estimates for every individual item.