Agile T-Shirt Sizing:
Estimation Without the Chaos
Stop arguing about whether something is 5 or 8 story points. T-shirt sizing gives your team a faster, lighter way to estimate relative effort — especially early in planning.
What Is T-Shirt Sizing?
T-shirt sizing is a lightweight relative estimation technique where backlog items are sized using clothing sizes — XS, S, M, L, XL — instead of story points or hours.
The key insight is that estimation is a comparison problem, not a measurement problem. Nobody knows how long an M story will take in hours. But everyone can agree that an M is roughly twice as complex as an S, and half as complex as an L.
T-shirt sizing removes false precision from estimation. It works especially well for roadmap planning, early discovery, and any situation where requirements are still evolving and story-point-level accuracy would be misleading anyway.
T-Shirt Size Reference
How to Run a T-Shirt Sizing Session
Six steps for a fast, bias-free estimation session.
Establish anchor items
Find one item the whole team agrees is 'Medium' and one that is clearly 'Small'. Use these as calibration points for all subsequent estimates.
Present items one at a time
Read out each backlog item briefly. The goal isn't full understanding — it's a relative sense of effort compared to the anchors.
Simultaneous silent reveal
Everyone picks a T-shirt size privately, then reveals at the same time. This prevents anchoring — the first person to speak shouldn't set the bar for everyone else.
Discuss outliers, not consensus
When everyone agrees, move on. When there's a spread (e.g. one S and three Ls), only the outliers explain their reasoning. The divergence is the signal.
Record and move on
Record the agreed size. Don't gold-plate — you're not committing to exact hours. Keep the pace high: a well-run session sizes 15–20 items per hour.
Map to story points (optional)
After the session, map sizes to numbers if your tool requires it: XS=1, S=2, M=5, L=8, XL=13. This mapping is a conversion, not an estimate.
Tips for Better T-Shirt Sizing
- Never ask 'how many hours' — you're estimating relative effort, not time.
- Split anything that gets an XL — it's too risky to estimate accurately at that size.
- Reveal simultaneously, every time. The moment one person speaks first, you've anchored the group.
- Don't size more than 2–3 Sprints ahead — items will change.
- Use the same anchors across sessions for consistency in your velocity.
How Workshop Weaver Helps
Workshop Weaver helps agile teams structure estimation sessions with the right methods at the right time. Plan your T-shirt sizing session with a timed agenda, pick supporting methods (like anchor-setting activities), and avoid the common pitfalls that turn estimation into guesswork.
Plan your estimation sessionFrequently Asked Questions
What is agile T-shirt sizing?
T-shirt sizing is a relative estimation technique where backlog items are sized using clothing sizes (XS, S, M, L, XL) instead of story points or hours. It removes false precision from estimation, encourages discussion about relative complexity, and works especially well for roadmap planning when requirements are still fuzzy.
When should you use T-shirt sizing vs Planning Poker?
Use T-shirt sizing when you need a quick, low-stakes relative comparison — especially for roadmaps, early discovery, or when a team is new to estimation and story points feel abstract. Use Planning Poker when you need more granular estimates for Sprint Planning and have well-defined stories ready for commitment.
How do you convert T-shirt sizes to story points?
A common mapping is: XS=1, S=2, M=5, L=8, XL=13. This aligns with the Fibonacci sequence used in Planning Poker. The exact numbers matter less than consistent application — what's important is that the team uses the same mapping across sessions so velocity figures remain comparable.
How many items can you size in one T-shirt sizing session?
A focused team can size 15–20 items per hour. Sessions typically run 30–90 minutes. If you're regularly going longer, your items are too vague or too large — address that in refinement before the sizing session.
Run Better Estimation Sessions
Workshop Weaver helps agile teams plan structured, bias-free estimation sessions. Build your agenda, pick the right methods, and walk in prepared.
Try Workshop Weaver free