T-Shirt Sizing in Agile: When (and How) to Use It Instead of Story Points

Your Quarterly Planning Meeting Is Taking Forever

The product team has 60 items on the roadmap for next quarter. Leadership wants rough effort estimates so they can set realistic expectations. And someone suggests using story points to estimate all 60 items.

Three hours later, the team is on item 22, everyone is exhausted, and the estimates are getting less reliable by the minute. Story points are great for sprint-level work, but they’re too granular and too slow for roadmap-level planning. You need a different tool for this job.

That tool is T-shirt sizing.

What T-Shirt Sizing Actually Is

T-shirt sizing replaces numbers with familiar size categories: XS, S, M, L, XL, and sometimes XXL. Each size represents a relative band of effort, complexity, and uncertainty. There’s no mathematical precision. That’s the point.

When someone says an item is “Large,” the team understands it’s a significant chunk of work, probably taking a full sprint or more for a small team. When something is “Small,” everyone knows it’s a couple of days of effort at most. The categories are deliberately broad because, at the roadmap level, false precision wastes more time than it saves.

The power of T-shirt sizing is that it removes the numerical arguments. Nobody debates whether something is a 5 or an 8. They simply agree it’s “Medium” or “Large,” and the conversation moves forward.

When T-Shirt Sizing Works Better Than Story Points

T-shirt sizing isn’t always the right choice. But in several common situations, it outperforms numerical estimation:

Roadmap and quarterly planning. When you need rough sizing on 30-100+ items to inform priority decisions, T-shirt sizing gets the job done in a fraction of the time. The precision loss is acceptable because the items will be re-estimated with story points closer to execution anyway.

Cross-functional conversations. When product managers, designers, and executives are in the room, T-shirt sizes communicate effort in a way everyone understands. Nobody needs to ask “what does 13 story points mean?” A Large is a Large.

Early-stage features. When a feature is still a concept, trying to assign story points is guesswork dressed up as precision. T-shirt sizing acknowledges the uncertainty honestly. “This feels Large” is more truthful than “this is exactly 13 points” when the requirements are still vague.

Teams new to estimation. For teams that haven’t built a shared understanding of what story points mean, T-shirt sizing is a low-pressure starting point. It builds the muscle of relative comparison without the anxiety of numbers.

Portfolio-level prioritization. When leadership needs to compare effort across multiple teams or projects, T-shirt sizes provide enough signal to make decisions without requiring every team to use the same numerical scale.

How to Run a T-Shirt Sizing Session

Step 1: Define Your Sizes

Before the session, agree on what each size roughly represents. This doesn’t need to be exact, but the team should have a shared mental model. Here’s a common starting point:

• XS: A few hours of work. Trivial effort, minimal complexity.
• S: A day or two. Straightforward, well-understood work.
• M: Several days to a week. Moderate complexity, some unknowns.
• L: One to two weeks. Significant complexity or multiple components involved.
• XL: Multiple weeks. High complexity, many unknowns. Probably needs to be broken down before execution.
• XXL: Too big to estimate meaningfully. Needs to be split into smaller pieces.

Anchor these definitions with real examples from your team’s history. “Remember the payment integration last quarter? That was an XL. The login page redesign was a Medium.” Concrete references work better than abstract descriptions.

Step 2: Present the Items

The product owner briefly describes each item. Keep descriptions concise. At this stage, the team needs enough context to understand what the work involves, not a full spec. Aim for 1-2 minutes per item on the description.

Step 3: Size Simultaneously

Just like Planning Poker, everyone reveals their size at the same time. You can use physical cards labeled with sizes, a simple hand signal (hold up 1-5 fingers), or a digital tool. The simultaneous reveal prevents anchoring.

Step 4: Discuss Divergence

If everyone says Medium, record it and move on. If one person says Small and another says XL, pause for a quick discussion. Usually, someone knows something the others don’t. A two-minute conversation resolves most disagreements.

Step 5: Record and Move On

Don’t overthink it. If the team is split between Medium and Large, go with Large and move to the next item. You can refine later. The goal is to get rough sizing on everything, not to achieve perfect accuracy on each item.

A well-run session can size 40-60 items in an hour. Compare that to Planning Poker, where you’d estimate maybe 15-25 items in the same time.

Converting T-Shirt Sizes to Numbers

Some organizations need numerical estimates for budgeting, capacity planning, or forecasting. If that’s your situation, you can map T-shirt sizes to numbers after the sizing session.

A common mapping:

• XS = 1 story point
• S = 3 story points
• M = 5 story points
• L = 13 story points
• XL = 21 story points
• XXL = 40+ (needs decomposition)

Use these conversions cautiously. The whole point of T-shirt sizing is to avoid false precision. If you convert every item to a number and then add them up to calculate a “total effort,” you’ve recreated the precision problem you were trying to avoid. Use the numbers as rough inputs for capacity modeling, not as commitments.

Common Mistakes to Avoid

Using T-Shirt Sizing for Sprint Planning

T-shirt sizes don’t have enough granularity for sprint-level work. If your team needs to figure out how many items fit in a two-week sprint, you need the precision that story points or a similar technique provides. T-shirt sizing is for roadmap-level decisions, not sprint commitments.

Not Anchoring the Sizes

Without concrete examples, “Medium” means something different to every person on the team. Always establish reference items before starting. Pick 3-4 well-known past items and assign them sizes. Everything else gets compared to those anchors.

Everything Is a Medium

If 70% of your items end up as “Medium,” the sizing isn’t providing useful differentiation. This usually means the size definitions are too broad or the team is defaulting to the middle to avoid discussion. Tighten the definitions and encourage the team to commit to a direction when they’re uncertain.

Treating Sizes as Time Commitments

A “Large” is not a promise that the work will take exactly 1-2 weeks. It’s a rough indicator of relative effort. If leadership starts holding teams accountable to T-shirt size estimates as if they were deadlines, the team will stop estimating honestly. Make the purpose clear: these are inputs for planning, not contracts.

Skipping the Conversation

Even though T-shirt sizing is faster than Planning Poker, the divergence discussions still matter. When one person says Small and another says XL, there’s a misunderstanding that needs resolving. Those conversations are where the real value lives. Don’t skip them just to save five minutes.

Putting It All Together

T-shirt sizing works best as part of a multi-technique estimation approach. Use it for roadmap planning and early-stage sizing. Use story points or Planning Poker when work gets closer to execution. The two techniques complement each other well.

If your team hasn’t tried it, the next quarterly planning session is a good opportunity. Prepare a backlog of items, spend 10 minutes calibrating your size definitions with reference examples, and then start sizing. You’ll be surprised how much ground you cover in an hour.

Frequently Asked Questions

Is T-shirt sizing better than story points?

Neither is universally better. They serve different purposes. T-shirt sizing excels at roadmap-level, rough estimation where speed matters more than precision. Story points are better for sprint-level planning where you need granular estimates for capacity decisions. Most teams benefit from using both at different stages of their planning process.

How many T-shirt sizes should we use?

Five sizes (S, M, L, XL, XXL) work well for most teams. Adding XS gives you a sixth option for truly trivial items. Going beyond six sizes starts to recreate the granularity problems of numerical estimation. If you need that much precision, you’re probably better off switching to story points.

Can T-shirt sizes be used for sprint planning?

They can, but they’re not the best fit. Sprint planning requires enough precision to determine how much work fits in a sprint. T-shirt sizes are too coarse for that. If you want to use them, convert sizes to numerical equivalents first, but at that point you might as well use story points directly.

What if the team can’t agree on a size?

Use the same approach as Planning Poker: ask the people with the most divergent views to explain their reasoning. Usually, one person has context the others lack. After a brief discussion, ask for a re-vote. If there’s still no agreement, go with the larger size. At the roadmap level, overestimating slightly is safer than underestimating.

How do you handle items that are clearly XXL?

XXL items should be flagged for decomposition, not left as-is. An item too big to estimate meaningfully is also too big to deliver predictably. Work with the product owner to break it into smaller, independently valuable pieces. Then size those smaller pieces. This usually happens before the items reach sprint planning.

Do we need physical cards for T-shirt sizing?

No. You can use hand signals (hold up 1-5 fingers for S through XXL), chat-based reveals in video calls, or digital tools like Miro or Parabol. Physical cards are nice to have but not necessary. The simultaneous reveal is what matters, regardless of the medium.

How do you explain T-shirt sizing to executives?

Keep it simple: “We categorize work into Small, Medium, Large, and Extra Large based on relative effort. It’s like asking ‘is this a weekend project or a month-long project?’ without pretending to know the exact number of days.” Most executives appreciate the honesty of rough estimates over the false precision of detailed ones that turn out to be wrong.