T-Shirt Sizing
What is T-Shirt Sizing?
T-shirt sizing is a relative estimation technique in which teams sort work into sizes such as XS, S, M, L and XL. It is fast, avoids false precision and suits early, uncertain planning.
Updated November 2026 · 2 min read
How t-shirt sizing works
The team looks at a set of items, such as features, epics or projects, and puts each into a size bucket by comparing it with the others. Nobody estimates in days. The question is simply "is this bigger or smaller than that one?" Once the team agrees what each size means, the buckets can be turned into rough ranges for planning.
| Size | Relative effort | Example range (one team) |
| XS | Trivial; a few days at most | Under 1 week |
| S | Small, well understood | 1 to 2 weeks |
| M | Moderate, some unknowns | 2 to 6 weeks |
| L | Large, several unknowns | 1 to 3 months |
| XL | Very large; should probably be split | More than a quarter |
The ranges are examples. Each organization sets its own, and they should be written down so sizes mean the same thing across teams and over time.
When to use it
T-shirt sizing works best early, when there is too little detail for precise estimates and precision would be false anyway. Typical uses include roadmap planning, sizing a backlog of epics before PI Planning, comparing project ideas in project intake, and giving a quick feasibility read on a request. Closer to delivery, teams usually switch to story points or other finer-grained methods, such as planning poker.
An example
A product team has 30 epic ideas for next year and needs to know roughly what fits. In a two-hour session, the team sorts them on a wall from smallest to largest, then draws lines between sizes. They end with 4 XS, 8 S, 10 M, 6 L and 2 XL. The two XLs are split into smaller pieces. Using the team's agreed ranges, the leadership group sees that the full list would take about 18 months of capacity, and cuts it to the most valuable 12 months' worth using WSJF.
T-shirt sizing vs other estimation methods
| Method | Precision | Speed | Best for |
| T-shirt sizing | Low | Very fast | Roadmaps, portfolios, early ideas |
| Story points | Medium | Moderate | Sprint and release planning |
| Hours or days | High (in theory) | Slow | Small, well-understood tasks |
| ROM estimate | Low, with cost range | Fast | Early budget decisions |
Tips for doing it well
- Agree what each size means in time or effort, and revisit after a few cycles using actuals
- Compare items with each other, not with an abstract scale
- Split anything sized XL before committing to it
- Size as a group, so different perspectives surface hidden work
- Do not add sizes together as if they were numbers; convert to ranges first
Common pitfalls
The most common mistake is treating sizes as commitments. An M is a rough category, not a promise of four weeks. Another is converting sizes to single numbers and summing them, which hides the uncertainty that made t-shirt sizing the right choice. Finally, sizes drift: if teams never compare their sizes with what actually happened, an M slowly comes to mean something different. A short look back at each sprint retrospective or quarterly review keeps the scale honest.
Frequently asked questions
What do the sizes in t-shirt sizing mean?
Each size is a relative bucket of effort, usually XS, S, M, L and XL, sometimes with XXL. Their exact meaning is set by each team or organization. A common approach is to map each size to a time range, such as S for one to two weeks and L for one to three months, and review the ranges using actual results.
Is t-shirt sizing better than story points?
Neither is better in general; they suit different stages. T-shirt sizing is faster and better for early, uncertain work such as roadmaps and portfolio planning. Story points are more precise and better for planning sprints. Many teams use t-shirt sizes for epics and story points once work is broken into smaller items.
Can you convert t-shirt sizes to story points?
Some teams do, mapping each size to a point range, but it should be done with care. Converting sizes into single numbers and summing them gives a false sense of precision. It is usually better to convert sizes into time or cost ranges for planning, and estimate in story points only when items are broken down.
Related terms
PI Planning
The event where every team on a release train plans the next quarter together.
Story Points
A relative measure of the size of work, used instead of hours.
Weighted Shortest Job First (WSJF)
Ranking work by cost of delay divided by size, so high value ships first.
Sprint Retrospective
The end-of-Sprint meeting where the team agrees how to work better.