Quick, rough estimates for roadmap planning. Skip the Fibonacci precision and just answer the question: is this small, medium, or large?
Start a free roomNo account required. Share a code and you are in. Password-protected rooms supported.
T-shirt sizing is an agile estimation technique that uses clothing sizes (XS, S, M, L, XL, XXL) instead of numbers. It trades precision for speed - the goal is not to nail down exactly how many hours something takes, but to quickly agree on relative effort so you can plan at a higher level.
Like planning poker, everyone votes simultaneously to prevent anchoring bias. When the team disagrees - say, one person thinks a feature is S and another thinks it is XL - that gap signals a conversation worth having before anything gets scheduled.
When you have 30 epics to size in an afternoon, Fibonacci numbers slow you down. T-shirt sizes get the team to consensus faster.
Estimating months-away work in story points is guesswork. T-shirt sizes are honest - they say "this is roughly large" without pretending to know more.
Non-technical stakeholders, designers, and new team members can contribute meaningfully without knowing what a "5" means.
Long backlog refinement sessions drain teams. T-shirt sizing moves faster and keeps energy up when the list is long.
When sizing a full quarter of work, Fibonacci precision is overkill. T-shirt sizing lets the team move through a long list quickly and still produce a useful, honest forecast.
Items that are months away from being worked on are too fuzzy for story points. T-shirt sizing gives you a useful relative ordering without the false confidence of a number.
When product managers, designers, and engineers need to size work together, T-shirt sizes are a shared language that doesn't require engineering context to use.
Some teams spend too long debating whether something is a 3 or a 5. T-shirt sizing reduces that to "is this small or medium?" and keeps planning sessions moving.
Host creates a room and shares the 6-character code with the team.
Everyone joins by entering their name - no account needed.
Host can claim the room to make it permanent and optionally set a password.
Host presents an item - a feature, epic, or story.
Each person picks a size: XS, S, M, L, XL, XXL, or ? for uncertainty.
Host reveals all votes at once. The result shows the most common size and whether the team reached consensus.
If votes are spread, the team discusses briefly and re-votes. If consensus is reached, move to the next item.
Both techniques use simultaneous voting to avoid anchoring bias. The difference is precision vs speed.
Planning poker works best for sprint-level estimation where you need to know if a story fits in a sprint. T-shirt sizing works best when you need to size a large backlog quickly, or when items are too far out to estimate precisely.
Many teams use both: T-shirt sizing at the roadmap and quarterly planning level, and planning poker during sprint refinement when items are ready to be worked on.
Create a free room in seconds and invite your team with a code. No account, no setup.
Start a free T-Shirt Sizing room