T-Shirt Sizing in Agile: Simple Estimation Guide for Teams (2026)

T-Shirt Sizing is an agile estimation technique that uses clothing sizes (XS, S, M, L, XL, XXL) instead of numbers. It’s intuitive, fast, and perfect for high-level estimates.

What is T-Shirt Sizing?

Instead of assigning numerical story points (1, 2, 3, 5, 8), you assign categorical sizes:

• XS (Extra Small): Trivial tasks
• S (Small): Small tasks
• M (Medium): Medium tasks
• L (Large): Large tasks
• XL (Extra Large): Very large tasks
• XXL (Extra Extra Large): Epics that should be split

When to Use T-Shirt Sizing

✅ Ideal Situations

1. Initial Backlog Grooming

You have 50-100 new stories and need to classify them quickly.

Before (with Fibonacci):
- 4 hours estimating 50 stories with Planning Poker
- Debate over each number

After (with T-Shirt):
- 1 hour classifying 50 stories into 5 categories
- Conversations only for ambiguous cases

2. Teams New to Agile

Numbers and Fibonacci are intimidating. Sizes are familiar.

"Is this story small, medium, or large?"
vs
"Is this story a 3, 5, or 8 in Fibonacci?"

3. Roadmap Planning

High-level estimates for quarterly or annual planning.

Q1: 5 L features, 10 M features, 20 S features
Q2: 3 XL features, 8 L features, 15 M features

4. Stakeholder Prioritization

Non-technical people understand sizes better than story points.

CEO: "How much does this feature cost?"
You: "It's an L" ✅

vs

You: "It's 13 story points" ❌ (requires explaining what story points are)

❌ Don’t Use T-Shirt Sizing For

1. Detailed Sprint Planning

T-Shirt doesn’t allow calculating numerical velocity.

❌ You can't: "Our velocity is 3M + 5S per sprint"
✅ You can: "Our velocity is 25 points per sprint"

2. Metrics and Reports

Difficult to create burndown charts or projections with sizes.

3. Mature Teams

If you already master Fibonacci, T-Shirt is a step backwards.

How to Implement T-Shirt Sizing

Step 1: Define Your Sizes

Create concrete examples for each category:

Size	Complexity	Approximate Time	Example
XS	Trivial	< 2 hours	Change button text
S	Low	2-8 hours	Add field to existing form
M	Medium	1-3 days	Create REST endpoint with validation
L	High	3-5 days	Integrate payment service
XL	Very High	1-2 weeks	Redesign authentication module
XXL	Epic	> 2 weeks	Migrate to new architecture

Important: These times are approximate. Focus is on relative complexity.

Step 2: Estimate by Affinity

The “Affinity Estimation” technique is perfect with T-Shirt Sizing:

1. Prepare: Write each story on a card (physical or digital)

2. Classify silently: Each team member groups cards into columns (XS, S, M, L, XL, XXL)

3. Compare and adjust: As a team, review stories that are in different columns

4. Move consensually: Discuss only stories with disagreement

Advantage: You can estimate 30 stories in 30 minutes.

Step 3: Plan with Capacity

Instead of numerical velocity, use categorical capacity:

Team capacity per sprint (based on past sprints):
- 1 XL
- 3 M
- 5 S

Sprint Planning:
✅ Feature A (XL) + Feature B (M) + 3 bugs (S each)
❌ Feature A (XL) + Feature C (XL) ← Overload

T-Shirt Sizing vs Story Points

Aspect	T-Shirt Sizing	Story Points (Fibonacci)
Learning	Immediate	Requires practice
Speed	Very fast	Moderate
Precision	Low	Medium-High
Metrics	Difficult	Easy
Long-term planning	Excellent	Good
Sprint planning	Adequate	Excellent
Burndown charts	No	Yes

Recommended Hybrid Strategy

Many teams use both:

1. Backlog grooming (monthly): T-Shirt Sizing
   - Classify new stories quickly
   - High-level prioritization

2. Sprint planning (every 2 weeks): Fibonacci
   - Estimate next sprint stories in detail
   - Calculate velocity and create burndown

3. Conversion (when necessary):
   XS = 1-2 points
   S = 3 points
   M = 5 points
   L = 8 points
   XL = 13 points
   XXL = Split into smaller stories

Common Mistakes with T-Shirt Sizing

Mistake 1: Too Many Categories

❌ XS, S, SM, M, ML, L, XL, XXL, XXXL

Too many options cause decision paralysis. Keep maximum 6 sizes.

Mistake 2: Equating Sizes with People

❌ “S = junior work, L = senior work”

Sizes reflect task complexity, not skill required.

Mistake 3: Not Documenting Examples

❌ “What was an M last week?”

Without reference stories, sizes lose consistency.

✅ Keep a document with 2-3 examples per size.

Mistake 4: Attempting Exact Math

❌ “If M = 5 points and L = 8 points, then 2M + 1L = 18 points”

T-Shirt isn’t that precise. Use for approximations, not exact calculations.

Best Practices

1. Keep it simple: Use maximum 6 sizes. More options = more confusion.

2. Document examples: Create a “catalog” of reference stories for each size.

3. Review and calibrate: Each month, review if “M” stories really took similar effort.

4. Combine with Fibonacci: T-Shirt for grooming, Fibonacci for planning.

5. Don’t force precision: If a story is between M and L, it’s okay to call it “M+” temporarily.

6. Evolve definitions: As the team learns, adjust what each size means.

Conclusion

T-Shirt Sizing doesn’t replace story points, but complements them perfectly. Use it when you need speed over precision, or when working with non-technical stakeholders.

The best strategy is hybrid: T-Shirt for quick grooming of large backlog, Fibonacci for detailed sprint planning.

Try T-Shirt Sizing Now

Create a session with T-Shirt mode on GoSprintPlanning. Switch between Fibonacci and T-Shirt with one click.

Related Resources

• Fibonacci Sequence in Agile Estimation
• Planning Poker: Complete Guide
• Scrum Team Velocity Guide