T-Shirt Sizing for Coarse Estimates
What You'll Learn
You'll learn when and how to use abstract sizes (XS, S, M, L, XL) to quickly estimate work without false precision.
The Core Idea
T-shirt sizing applies clothing sizes to software tasks, giving you a fast way to estimate complexity or effort when detailed analysis isn't worthwhile—or even possible yet. Instead of debating whether something is 5 or 8 story points, you simply ask: "Is this Small, Medium, or Large?"
This approach shines in early planning stages when requirements are fuzzy. You're acknowledging uncertainty upfront rather than pretending a "3-point story" has mathematical precision.
When to Use T-Shirt Sizing
Early roadmap planning: When you need to size dozens of ideas quickly to prioritize them.
Portfolio management: Comparing initiatives that span months without knowing implementation details.
Pre-refinement triage: Deciding which backlog items deserve detailed breakdown.
The Scale
A typical scale looks like:
- XS: Trivial change, almost no risk
- S: Small feature, clear path forward
- M: Standard feature requiring some design
- L: Complex feature touching multiple systems
- XL: Major initiative, possibly should be broken down
Some teams use only S/M/L to force simpler decisions.
Advantages Over Numeric Estimates
T-shirt sizes feel approximate, which discourages false precision. Stakeholders intuitively understand "this is Large" doesn't mean "exactly 13 days." It's harder to game or manipulate, and teams reach consensus faster because there are fewer options to debate.
The method acknowledges what you learned in "Why Estimation is Hard"—that precision early is often impossible, so embrace the ambiguity with appropriate tools.
Key Takeaway: T-shirt sizing trades precision for speed, making it ideal for high-level planning when detailed estimates would be wasted effort or misleading.