T-Shirt Sizing: The Simplest Agile Estimation Technique

Quick, intuitive estimation that anyone can understand.

---

What Is T-Shirt Sizing?

T-Shirt sizing is the simplest estimation technique--perfect for high-level roadmap planning when precision isn't the goal. It uses familiar clothing sizes to categorize work by relative complexity.

How It Works

Assign each item a size: XS, S, M, L, XL, or XXL. That's it.

Size	Meaning	Example
XS	Trivial, no complexity	Fix a typo, update a constant
S	Straightforward, well-understood work	Add form validation, simple UI change
M	Moderate complexity, some unknowns	New API endpoint with basic logic
L	Significant effort, multiple components	User authentication feature
XL	Major feature, many unknowns	Dashboard with multiple widgets
XXL	Epic-level work, should be broken down	Mobile app, major platform migration

The key insight is that everyone intuitively understands "this is bigger than that." You don't need to define exact criteria--the team naturally calibrates through discussion.

---

When to Use T-Shirt Sizing

T-Shirt sizing excels for:

Roadmap Planning

"This quarter we can fit 2 Large features and 5 Small ones"

When planning months ahead, precise estimates are impossible and wasteful. T-Shirt sizes give enough information to prioritize and staff appropriately.

Initial Backlog Grooming

Quick categorization of new ideas before they're refined. You can size 30 items in 20 minutes.

Non-Technical Stakeholders

Everyone understands "this is a Large." No need to explain what story points mean or how velocity works.

Very Early-Stage Estimates

When you haven't designed the solution yet, T-Shirt sizes honestly represent your level of uncertainty.

---

Running a T-Shirt Sizing Session

Step 1: Set the Stage

Gather the team (or at least representatives from different disciplines). Explain that you're doing rough sizing, not detailed estimates.

Step 2: Start with Anchors

Pick 2-3 items everyone agrees on:

• "Adding a tooltip is clearly an XS"
• "Our checkout redesign was a solid L"
• "The mobile app is definitely XXL"

These anchors help calibrate the discussion.

Step 3: Size Quickly

Go through items one by one. If there's immediate consensus, move on. If there's disagreement, discuss briefly:

• "Why do you think this is M instead of L?"
• "Are we forgetting something?"

Step 4: Handle XXL Items

Anything sized XXL is a red flag. These need to be broken down before they're useful. Note them and move on--don't spend time debating the size of something that's clearly too big.

---

Example Session

Your team is estimating Q2 features:

Feature	Initial Size	Discussion	Final Size
Dark mode toggle	S	"One component, existing pattern"	S
User notifications	M→L	"Wait, includes email integration"	L
Performance dashboard	M	"Charts + data aggregation"	M
Mobile app	XXL	"Break this down"	XXL (needs split)
API rate limiting	S→M	"Needs Redis, some unknowns"	M
Export to PDF	M	"Library does the heavy lifting"	M

Notice how the discussion surfaces hidden complexity (notifications include email) and clarifies assumptions (PDF uses a library).

---

Pros and Cons

Pros

Speed - You can size 20 items in 15 minutes. No mathematical debates.

Low Cognitive Overhead - No need to remember what "5 points" means vs "8 points."

Universal Understanding - Works for mixed teams, stakeholders, and new members.

Honest Uncertainty - Doesn't pretend to precision you don't have.

Cons

Too Imprecise for Sprint Planning - You need more granularity to fill a 2-week sprint.

No Mathematical Relationship - Is XL twice as big as M? Nobody knows, and that's the point--but it limits what you can calculate.

Hard to Track Velocity - "We completed 3 Mediums and 2 Smalls" doesn't give you trending data.

Inflation Risk - Without calibration, everything becomes "Medium" over time.

---

Converting to Other Techniques

T-Shirt sizing often serves as a first pass before more detailed estimation:

T-Shirt	Typical Story Points
XS	1
S	2-3
M	5
L	8
XL	13
XXL	21+ (break down)

But don't treat this as a formula. Re-estimate in story points when you need precision.

---

Best Practices

1. Keep It Fast

If you're spending more than 2 minutes on an item, you're missing the point. Note the disagreement and move on.

2. Recalibrate Regularly

Every few sessions, review: "Are our sizes consistent? Has 'Medium' gotten smaller over time?"

3. XXL = Action Required

Never let XXL items sit. They must be broken down before they're prioritized.

4. Document Your Anchors

Keep a list of reference items for each size. New team members can study these.

5. Don't Mix Techniques

If you're T-Shirt sizing, everyone uses T-Shirts. Don't let someone say "that's about 8 points"--it creates confusion.

---

When to Graduate to Story Points

Move to story points when:

• You need sprint-level planning precision
• You want to track velocity over time
• The team is stable enough to maintain calibration
• Stakeholders accept the additional complexity

T-Shirt sizing remains valuable even after you adopt story points--use it for roadmaps while using points for sprints.

---

Try It Now

Ready to try T-Shirt sizing with your team? Our free tool makes it easy:

T-Shirt Sizing Calculator - Collaborative estimation with your team

---

Next up: Story Points - the industry standard for sprint planning.

---

Last updated: January 2026