Definition
Relative Estimation
Relative estimation sizes work by comparing items to each other rather than guessing absolute hours. Teams use techniques like story points, t-shirt sizing (S/M/L), and planning poker to ask 'is this bigger than that?' — a question humans answer more reliably than 'how long will this take?' The sized values then feed velocity and forecasting.
Key takeaways
- Relative estimation sizes work by comparing items to each other rather than guessing absolute hours. Teams use techniques like story points, t-shirt sizing (S/M/L), and planning poker to ask 'is this bigger than that?' — a question humans answer more reliably than 'how long will this take?' The sized values then feed velocity and forecasting.
- The premise behind relative estimation is a well-documented quirk of human judgment: people are poor at estimating absolute durations but reasonably good at comparison.
- Planoda supports an estimate field on every issue and rolls it into velocity and burndown, so teams can size in points, t-shirt buckets, or simply count issues — whichever calibration they trust.
The premise behind relative estimation is a well-documented quirk of human judgment: people are poor at estimating absolute durations but reasonably good at comparison. Asked how many hours a task will take, estimates scatter wildly; asked whether it is bigger or smaller than a task they just finished, people are far more consistent. Relative estimation leans entirely on that comparative strength.
Several techniques put it into practice. Story points assign a relative number — often a Fibonacci-like 1, 2, 3, 5, 8, 13 — that bundles effort, complexity, and risk into one figure. T-shirt sizing uses coarse buckets (XS through XL) when even numbers feel too precise, useful for early, fuzzy planning. Planning poker is the social ritual: team members privately pick a size, reveal simultaneously, and discuss the outliers, which surfaces hidden assumptions and converges the team's shared sense of scale.
The coarseness is deliberate. Gaps between values widen as size grows because uncertainty compounds for larger work — a 13 is not a precise quantity but a signal to split the item before committing. And because the scale is calibrated to one team's shared sense of size, the numbers feed that team's velocity and mean nothing transplanted to another team.
Planoda supports an estimate field on every issue and rolls it into velocity and burndown, so teams can size in points, t-shirt buckets, or simply count issues — whichever calibration they trust.
Related terms
- Story Points (Estimation)Story points are a relative, unitless measure of how much effort an issue will take, accounting for complexity and uncertainty rather than raw hours. Teams estimate in points — often using a Fibonacci-like scale — to compare items against each other quickly. Summed across a cycle, points feed velocity and burndown without false precision about clock time.
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- Sprint PlanningSprint planning is the meeting that opens a sprint, where the team reviews the prioritized backlog and decides what it will commit to in the coming iteration. The team agrees on a sprint goal, pulls a realistic amount of work it believes it can finish, and clarifies scope. The output is a concrete, achievable plan for the time-box ahead.
- BurndownA burndown chart tracks remaining work against time over a cycle, sloping from the total scope down toward zero as items are completed. It shows whether a team is on pace to finish what it committed to, making slippage visible early. The ideal line falls steadily; a flat line warns that work is stalling.