T-Shirt Sizing for Agile Teams
T-shirt sizing swaps numbers for XS–XL labels to size work quickly when precision would be false. This guide covers what each size means, how it maps to points, and when to reach for it.
T-shirt sizing estimates work using clothing sizes — XS, S, M, L, XL — instead of numbers. It is deliberately coarse. When you are sizing epics on a roadmap or triaging a fresh backlog, arguing over whether something is a 5 or an 8 is wasted breath; “this is a Large” is all the precision the moment deserves.
What each size means
| Size | Rough meaning | Typical response |
|---|---|---|
| XS | Tiny, obvious, do it anytime. | Just schedule it. |
| S | Small and well understood. | Fits comfortably in a sprint. |
| M | Medium; a real chunk of work. | Plan it deliberately. |
| L | Large; likely spans a sprint. | Break down before committing. |
| XL | Epic-sized; too big to plan as one item. | Must split into stories. |
When T-shirt sizing beats Fibonacci
- Roadmap and quarterly planning — sizing epics you will not touch for months, where numeric precision is fiction.
- Initial backlog triage — quickly separating the small from the enormous before deeper refinement.
- Non-technical stakeholders — sizes are intuitive for people who find story points abstract.
- Speed over granularity — you can size dozens of items in the time detailed pointing takes for a handful.
For sprint-level stories the team is about to commit to, the extra resolution of a Fibonacci deck is worth it — you need to tell a 3 from a 5 to forecast a sprint.
Mapping sizes to story points
Many teams size epics with T-shirts, then convert to points as items are refined into stories. A common mapping:
| T-shirt size | Approx. story points |
|---|---|
| XS | 1 |
| S | 2–3 |
| M | 5 |
| L | 8–13 |
| XL | 20+ (split it) |
Treat the mapping as a bridge, not a formula. The point of T-shirt sizing is to avoid false precision; converting an XL straight to “21 points” and committing to it throws that benefit away. Refine XLs into real stories first.
A quick worked example
A product team sizes four roadmap epics in ten minutes with planning poker using a T-shirt deck:
- Dark mode → M
- Single sign-on (SSO) → XL (split into 4 stories later)
- CSV export → S
- In-app notifications → L
That is enough to sequence a quarter. The SSO epic gets refined and re-estimated with Fibonacci points only when it approaches a sprint.
Frequently asked questions
Can we run T-shirt sizing as planning poker?
Yes. Everyone picks a size card privately and reveals together — the same anti-anchoring flow as numeric planning poker. PlanITPoker includes a T-shirt deck for exactly this.
Should we add XXL?
You can, but anything past L is already a signal to split. Extra large sizes mostly tell you the item is not ready to plan.
Is T-shirt sizing less accurate?
It is less precise on purpose. For early, uncertain work, coarse and honest beats precise and wrong.
Try a T-shirt deck now
PlanITPoker lets you pick a T-shirt or Fibonacci deck when you create a room, so you can size epics coarsely and stories precisely with the same free tool. Compare approaches in our estimation techniques guide.
Ready to estimate with your team?
Start a free planning poker session in seconds — no signup required.
Create a Room