Fibonacci (1, 2, 3, 5, 8, 13) vs T-shirt sizes (XS, S, M, L, XL)—which estimation scale should your team use? The answer depends on your team's comfort with numbers, need for precision, and how you integrate with project management tools.
Fibonacci Sequence Benefits
The Fibonacci scale is the most common in agile estimation. Here's why teams choose it:
Built-in Uncertainty
Gaps widen (5 vs 8 vs 13) as complexity increases, reflecting natural uncertainty. Small stories can be estimated precisely (1 vs 2), but large stories have larger jumps that acknowledge "we're less sure."
Prevents False Precision
No option for "6 points" or "7 points"—forces acceptance that estimation is approximate. Teams can't argue whether something is a 6 or 7; they must choose: is it closer to 5 or 8?
This constraint is a feature, not a bug. It prevents teams from wasting time on precision that doesn't exist.
Jira and Tooling Integration
Most project management tools default to Fibonacci. Switching to T-shirt requires custom field configuration. If you use standard agile tools, Fibonacci works out of the box.
Velocity Math is Easier
Summing numbers (5 + 8 + 3 = 16 points) is straightforward. T-shirt sizes require conversion to numbers before calculating velocity, adding a translation step.
Mathematically Grounded
The Fibonacci sequence appears throughout nature and reflects how humans naturally perceive size differences. Each number is ~1.6x the previous (golden ratio), matching how we perceive increasing complexity.
T-Shirt Sizing Benefits
T-shirt sizing has its own advantages, especially for certain team types:
Less Intimidating for Non-Technical Stakeholders
Product managers, designers, and business stakeholders immediately understand "this is a Large." No explanation needed. Fibonacci requires teaching: "What does 8 mean?"
Faster Initial Adoption
New teams grasp the concept immediately. Everyone's bought t-shirts; the metaphor is universal. First estimation session can start in 5 minutes, not 30.
Better for High-Level Roadmapping
When sizing epics before breaking into stories, T-shirts work well. "This initiative is an XL, that one's a Medium" communicates quickly without false precision.
Reduces Anchoring on Numbers
When teams use Fibonacci, they sometimes anchor: "Last API integration was 8, so this must be 8 too." T-shirts break that mental model—"Large" doesn't automatically link to previous work.
Works Well for Capacity Planning
Allocating team bandwidth using shirts is intuitive: "We can handle 2 Large and 3 Small stories this sprint" communicates capacity clearly.
Which Scale Should Your Team Use?
Choose Fibonacci if:
- Team is technical and comfortable with numbers
- You need velocity tracking and burndown charts
- Integration with Jira/Azure DevOps is important
- You estimate frequently (weekly refinement)
- Team has agile experience
Choose T-Shirt if:
- Cross-functional team includes many non-developers
- You're introducing estimation for the first time
- Focus is on epic-level roadmap planning, not sprint-level
- Team resists "mathematical" approaches
- Estimation happens infrequently (monthly/quarterly)
Use Both (Hybrid Approach)
Many teams use T-shirts for initial rough sizing, then convert to Fibonacci for sprint planning:
- Backlog grooming: Product owner sizes epics with T-shirts (XS=1, S=3, M=5, L=8, XL=13)
- Epic breakdown: Split Large epics into smaller stories
- Sprint planning: Team re-estimates stories using Fibonacci
This combines T-shirt speed with Fibonacci precision.
Converting Between Scales
Standard conversion:
- XS = 1-2 points
- S = 3 points
- M = 5 points
- L = 8 points
- XL = 13 points
- XXL = 21+ (too large, decompose first)
But avoid rigid conversion. The point of relative sizing is to compare stories, not map shirts to numbers mechanically.
Common Mistakes with Both Scales
Fibonacci Mistake: Debating 5 vs 8
If the team splits on 5 vs 8, the story isn't well understood. Either clarify requirements or take the higher estimate (acknowledges uncertainty).
T-Shirt Mistake: Inventing New Sizes
"Well, it's between Medium and Large, so let's call it Medium-Large." NO. Defeats the purpose of limited options. Pick Medium or Large.
Both: Forgetting It's Relative
Whether you use 5 or Medium, you're comparing to a baseline reference story. Without shared references, scales don't work. Maintain a library of "This is our reference 5" or "This is our reference Medium."
Can You Switch Scales?
Yes, but recalibrate your baseline. If you've been using Fibonacci and switch to T-shirts, re-estimate your reference stories in the new scale. Then use those as baselines going forward.
Don't try to convert historical velocity directly. Track new velocity for 3 sprints with the new scale before trusting forecasts.
Tools Supporting Both Scales
Alignlee supports both Fibonacci and T-shirt sizing—switch anytime. Also supports custom scales if neither fits your team.
Most teams start with T-shirts for simplicity, then graduate to Fibonacci once they're comfortable with relative estimation concepts. There's no wrong answer—pick what helps your team estimate consistently.
Start Estimating with Your Preferred Scale
Try both scales and see which your team prefers. The best scale is the one your team uses consistently.