T-Shirt Sizing
A lightweight relative estimation technique where backlog items are sized using T-shirt sizes (XS through XL) instead of story points or hours. It removes the false precision of numeric estimation, encourages discussion about relative effort, and works especially well for early-stage roadmap planning when details are unclear.
Copione di facilitazione
- 1
Open by stating what the sizes measure: relative effort and complexity, not hours or deadlines. Show the scale from XS to XL and agree whether XXL is allowed — anything that big usually needs splitting anyway.
5 min - 2
Calibrate anchors: ask the team to nominate one recently completed piece of work everyone agrees was a clear M and another that was a clear S. Write both where they stay visible all session — every estimate is relative to these two.
10 min - 3
Run a practice round on a throwaway item: silent pick, simultaneous reveal on a count of three, and a short outlier discussion — so the mechanics are settled before the real backlog starts.
5 min - 4
Size the real items one at a time: the item's owner explains it in under a minute, everyone picks silently and reveals together. On consensus, record the size and move on; on a spread, give the highest and lowest voters one minute each to explain their reasoning, then re-vote once.
30 min - 5
Park any item that still splits the room after a re-vote — repeated disagreement means it needs splitting or research, not a longer argument. Review the parking lot and assign a follow-up owner per item.
5 min - 6
Close by reading the full list back with its sizes, ask whether anything now looks wrong in context, and state what happens next — for example, L and XL items go to refinement for splitting before any planning.
5 min
Suggerimenti
Use T-Shirt Sizing for epics and features. Use Planning Poker for sprint-level stories.
Disagreement is signal — two people with very different sizes have different mental models. That's worth a 2-minute discussion.
Don't let the session become about hours. It's about relative complexity.
Keep a 'parking lot' for items that generate repeated disagreement — they need splitting.
Errori comuni
Skipping anchor calibration — without a shared reference M, every size comes from a private scale and the results are incomparable
Letting the discussion drift into hours — the moment someone says 'an M is about two weeks', the method collapses back into the false precision it was meant to avoid
Voting sequentially instead of simultaneously, so the first confident voice anchors everyone who follows
Debating an item past the second vote — persistent disagreement is a signal the item is misunderstood or too big, not a debate to be won
Variazioni
Bucket System: place items in buckets (XS, S, M, L, XL) rather than estimating one by one — much faster for large backlogs (50+ items). Animal Sizing: some teams use animals (mouse=XS, elephant=XL) to further remove numeric anchoring.
Casi d'uso
Quando usarlo
A roadmap of epics and features needs rough effort estimates before the detail required for story points exists
Refinement sessions keep stalling on whether an item is a 5 or an 8 — coarser buckets end the false-precision debate
Leadership wants a first-pass feasibility read on a quarter's worth of initiatives in a single sitting
A new team without an established velocity needs a shared language for effort before any numeric baseline exists
Quando non usarlo
Sprint-level stories feeding a velocity forecast — T-shirt sizes are too coarse to sum into a commitment; use Planning Poker there
Items differ mainly in value rather than effort — sizing measures effort and complexity; for value-based ordering reach for MoSCoW or an impact/effort matrix
Stakeholders will read the sizes as delivery dates — fix that expectation before the session, or don't hand over the output raw
One expert holds nearly all the knowledge about the items — a group ritual adds ceremony to what should be a short expert review the team then sanity-checks
Metodi correlati
Approfondimenti
Domande frequenti
How long does a t-shirt sizing session take?▾
Plan 30–90 minutes depending on backlog size: after anchor calibration, a well-run team sizes an item every two to three minutes. For very large backlogs of 50 or more items, switch to the Bucket System variation, which sorts items into size buckets much faster.
How many people do you need for t-shirt sizing?▾
It works with 3 to 12 people, ideally the whole team that will deliver the work. Beyond a dozen, outlier discussions slow to a crawl — split into two groups or use the Bucket System instead.
What is the difference between t-shirt sizing and Planning Poker?▾
T-shirt sizing uses coarse buckets suited to epics, features, and early roadmap planning where detail is thin; Planning Poker uses numeric points suited to sprint-level stories feeding a velocity forecast. Many teams use both: t-shirts for the roadmap, poker once items are refined.
Can you do t-shirt sizing remotely?▾
Yes — most planning-poker tools offer a t-shirt deck, or you can have everyone post their size in chat at the same moment. The one rule to protect is simultaneous reveal; sequential typing in a call anchors later voters just like it does in a room.
How do t-shirt sizes convert to story points?▾
A common mapping is XS=1, S=2, M=5, L=8, XL=13, applied after the session if a numeric roll-up is needed. Do the conversion afterwards rather than estimating in numbers directly — the whole point of the sizes is to keep the conversation about relative effort, not arithmetic.
Pianifica il tuo prossimo workshop con l'IA
Workshop Weaver ti aiuta a combinare metodi come T-Shirt Sizing in un'agenda completa e temporizzata in pochi minuti.
Prova gratisMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Workshop Weaver.