T-Shirt Sizing for Agile Estimation
Learn how to use T-shirt sizes (XS, S, M, L, XL, XXL) for agile estimation. Understand when T-shirt sizing is preferable to numeric scales and how to convert sizes to points.
Fundamentals
Detailed Explanation
T-Shirt Sizing for Estimation
T-shirt sizing maps user stories to familiar clothing sizes: XS, S, M, L, XL, XXL. It is one of the fastest ways to get a rough sense of effort across a large backlog.
When to Use T-Shirt Sizes
- Roadmap planning -- Sizing 50+ items in a single session.
- Stakeholder workshops -- Non-technical people find "Medium" more intuitive than "5 points."
- Epic-level estimation -- Before stories are refined enough for Fibonacci.
- New teams -- Reduces anxiety about picking the "right" number.
How It Works
- Present the first story. The team agrees it is a Medium (reference).
- For each subsequent story, ask: "Is this bigger or smaller than our Medium?"
- Place each story in its bucket.
XS -- Trivial change, well-understood, < 1 hour
S -- Small but non-trivial, clear path, ~ half a day
M -- Moderate effort, some unknowns, ~ 1-2 days
L -- Significant work, multiple components, ~ 3-5 days
XL -- Large feature, cross-cutting concerns, ~ 1 week+
XXL -- Epic-sized, should probably be split
Converting to Numeric Values
For sprint planning, teams often map sizes to Fibonacci numbers:
| Size | Points | Rationale |
|---|---|---|
| XS | 1 | Minimal effort |
| S | 2 | Small but real |
| M | 3 | Baseline reference |
| L | 5 | Substantial work |
| XL | 8 | Major effort |
| XXL | 13 | Should be split if possible |
This conversion lets you compute velocity and forecasts while keeping the simplicity of T-shirt estimation.
Use Case
Use this guide when your team is doing high-level backlog grooming or roadmap sizing and wants a faster alternative to Fibonacci estimation.