T-Shirt Sizing for Agile Teams

T-shirt sizing is a relative estimation method that trades numeric precision for speed. Teams bucket work as XS, S, M, L, or XL based on rough effort compared to other items — similar to picking a shirt size without measuring exact centimeters. It works well early in discovery when stories are epics, themes, or placeholders rather than sprint-ready tickets.

When T-shirt sizing shines

• Roadmap and release planning with stakeholders who do not use story points daily
• Initial backlog grooming before acceptance criteria exist
• Portfolio-level comparisons across teams with different velocities
• Workshops where the goal is priority order, not sprint commitment

T-shirt sizing vs Fibonacci story points

• T-shirt sizes — Fast, intuitive, low cognitive load. Great for sorting a large backlog into rough buckets. Not ideal for tracking sprint velocity numerically.
• Fibonacci story points — Better for sprint planning when the team needs comparable velocity sprint over sprint. Supports burndown charts and capacity math.

Many teams T-shirt size during discovery, then re-estimate with Fibonacci when stories meet Definition of Ready. PlanITPoker lets you pick the deck when creating a room so you can match the ceremony.

Mapping T-shirts to story points (optional)

Some teams define internal mappings — for example XS ≈ 1–2 points, S ≈ 3, M ≈ 5, L ≈ 8, XL ≈ 13+. Mappings are team-specific and should be recalibrated against actual delivery data. Treat mappings as guidance, not law: an XL story might split into three Medium Fibonacci items.

Facilitation tips for T-shirt sessions

• Keep the whole backlog visible so relative comparisons are easy.
• Anchor with one story everyone agrees is a Medium.
• Allow question cards when scope is unknown — do not force a size.
• Capture outliers: if half the team says S and half says L, discuss.

Using T-shirt decks in PlanITPoker

When creating a room, select the T-shirt deck to estimate with XS, S, M, L, XL plus question and coffee cards. Switch to Fibonacci for the next session when you move from refinement to sprint commitment. Read Fibonacci estimation for numeric scale details.