Quickly size backlog items and roadmap features together. XS to XXL - fast, relative, and bias-free. No sign-up required.
Start a free roomNo account required. Share a code and you are in. Password-protected rooms supported.
T-shirt sizing is a relative estimation technique where items are sized using clothing sizes - XS, S, M, L, XL, XXL - rather than precise numbers. The focus is on rough effort buckets, not exact story points. It is ideal for roadmap planning, PI planning, and early-stage backlog grooming where you need directional estimates, not precise ones.
Unlike planning poker with its Fibonacci precision, T-shirt sizing acknowledges that early estimates are inherently rough. You are sorting items into buckets, not measuring them to the millimetre. That is a feature, not a limitation - it keeps conversations at the right level of detail.
When you are looking three months out, you do not need story-point precision. XS, M, and XL tell stakeholders everything they need to know about relative effort.
The goal is not to agree on a number - it is to agree on whether something is small or large. That simpler question often gets you to alignment faster.
Product managers and designers find T-shirt sizes more intuitive than Fibonacci numbers. Everyone can participate meaningfully, not just the technical team.
When you have 30 items to size in 60 minutes, fewer options means faster decisions. T-shirt sizing keeps the session moving.
Sizing epics and themes for the next quarter. You need a rough sense of scope to make capacity decisions, not sprint-level estimates.
In SAFe environments, T-shirt sizing helps teams quickly assess feature scope before committing to program increments.
When stories are still high-level and not ready for sprint planning. Get a rough size now, refine to story points later.
When business stakeholders need to understand relative effort between competing priorities without getting into technical detail.
Host creates a room and shares the 6-character code with the team.
Everyone joins by entering their name - no account needed.
Host sets the item to estimate. The Jira Chrome extension lets you push a ticket directly from Jira.
Each person privately selects a T-shirt size: XS, S, M, L, XL, XXL, or a question mark.
Host reveals all votes at once. The mode (most common size) and consensus level appear immediately.
If there is disagreement, the team discusses. Then everyone re-votes.
Host resets for the next item. Repeat until the backlog or roadmap is sized.
Both techniques use simultaneous reveal to prevent anchoring bias. The key difference is precision. Planning poker uses Fibonacci numbers (1, 2, 3, 5, 8, 13, 21) that give you more granularity - useful when you need to compute velocity or compare story points across sprints.
T-shirt sizing uses five or six buckets. That coarser scale is actually an advantage at the roadmap level, where false precision creates false confidence. A story that is clearly M does not need to be debated between 5 and 8.
A common pattern: use T-shirt sizing at the roadmap level, then re-estimate with planning poker when items move into sprint planning and the details are clearer.
Create a free room in seconds and invite your team with a code. No account, no setup.
Start a free T-Shirt Sizing room