Definition
T-Shirt Sizing
T-shirt sizing is a relative estimation technique that classifies work into rough buckets — XS, S, M, L, XL — instead of precise numbers. The coarse scale is fast and intuitive, ideal for early, high-level estimation of epics or roadmap items where detailed point estimates would be false precision. It compares relative size rather than predicting exact effort.
Key takeaways
- T-shirt sizing classifies work into coarse buckets (XS–XL) instead of precise numbers, trading precision for speed.
- It is ideal for early, high-level estimation of epics and roadmap items where point precision would be false confidence.
- Its non-numeric scale resists summing and averaging, which keeps estimates as relative comparisons, not a budget.
- Teams often size in t-shirts up front, then re-estimate the small refined items in story points later.
T-shirt sizing trades precision for speed. By dropping numbers in favor of a handful of size labels, it lets a team estimate a large set of items quickly without getting trapped in debates over whether something is a 5 or an 8. The question becomes the much easier one a team can answer at a glance: is this roughly small, medium, or large relative to the others?
Its natural home is early and coarse-grained estimation. When sizing epics, initiatives, or a roadmap's worth of bets, the inputs are too uncertain to justify story-point precision. A bucket like 'L' honestly conveys 'big, needs breaking down later' without pretending to a confidence the team doesn't have. As items mature and get refined, teams often re-estimate the small ones in points.
Because the scale is non-numeric, t-shirt sizes resist being summed or averaged — which is a feature, not a bug. It discourages treating estimates as a budget and keeps them as what they are: relative comparisons. Teams that want roughly numeric forecasting sometimes map sizes to point ranges, but the labels stay the unit of conversation.
Planoda's estimate field accepts whatever scale a team prefers, so a roadmap can be sized in t-shirts up front and refined into points as items move toward a cycle.
Related terms
- Relative EstimationRelative 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.
- 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.
- Planning PokerPlanning poker is a consensus-based estimation technique where team members privately pick a card representing a story's effort, then reveal simultaneously. Divergent estimates spark discussion, and the team re-votes until it converges. Revealing at once prevents anchoring — no one is swayed by the first or loudest number — so estimates capture the whole team's understanding.
- EpicAn epic is a large unit of work too big to finish in a single cycle, broken down into smaller related issues that ship incrementally. It groups those child issues under one theme and tracks their combined progress. Epics sit between individual issues and broader projects or initiatives in the planning hierarchy.
- RoadmapA roadmap is a high-level, time-oriented view of what a team or product plans to build and roughly when. It communicates direction and sequencing across initiatives and projects, aligning stakeholders on priorities. Unlike a backlog of granular tasks, a roadmap operates at the altitude of themes, outcomes, and quarters rather than individual issues.