Fibonacci vs T-Shirt Sizing: Which Estimation Scale Should Your Team Use?
Quick answer
Use Fibonacci (1, 2, 3, 5, 8, 13) when your team needs numeric precision for velocity tracking and sprint capacity planning. Use T-shirt sizing (XS, S, M, L, XL) for early-stage estimation, roadmap planning, or teams new to agile who find numbers intimidating. Most mature teams end up on Fibonacci because it feeds directly into velocity calculations.
Every agile team hits this question early: should we estimate in Fibonacci numbers or T-shirt sizes? The answer depends on what you are trying to get out of estimation. Both scales work. Both have tradeoffs. And the wrong choice for your team creates friction that makes estimation feel like a chore instead of a useful planning tool.
How does Fibonacci estimation work?
Fibonacci estimation uses the sequence 1, 2, 3, 5, 8, 13, 21 to size stories. The gaps between numbers grow larger as complexity increases, which forces the team to make a meaningful distinction between a 5-point story and an 8-point story rather than pretending there is a difference between a 6 and a 7. This deliberate imprecision is the point. Estimation is not about getting the exact number right. It is about having a shared understanding of relative effort. The Fibonacci sequence builds that understanding into the scale itself.
How does T-shirt sizing work?
T-shirt sizing uses XS, S, M, L, and XL to categorize stories by relative size. There are no numbers involved. A small story takes a few hours. A large story might take most of a sprint. An XL story probably needs to be broken down before the team can estimate it meaningfully. The appeal is simplicity. Nobody argues about whether something is a "medium-large" because that is not an option. The labels are intuitive and low-stakes, which makes them less intimidating for teams new to estimation.
When should you use Fibonacci?
Use Fibonacci when your team tracks velocity and uses it for sprint capacity planning. Velocity is the average number of story points completed per sprint. If your stories are sized in T-shirts, you cannot sum them into a velocity number without converting to points anyway, which defeats the purpose. Fibonacci also works better for mature teams that have calibrated their scale. When everyone agrees that a 5-point story looks like "the login page redesign we did last sprint," estimation sessions become fast and accurate.
When should you use T-shirt sizing?
Use T-shirt sizing for roadmap-level estimation, backlog grooming where you are triaging dozens of stories quickly, or teams that are brand new to agile and find numeric estimation intimidating. T-shirt sizing is also useful when you are estimating across teams that use different Fibonacci calibrations. A "large" story means roughly the same thing to everyone, even if one team calls it 8 points and another calls it 13.
Can you switch scales mid-project?
Yes, but reset your velocity baseline when you do. Historical velocity in T-shirt sizes is not comparable to velocity in Fibonacci points. Treat the switch as a fresh start and give it 3 to 4 sprints to stabilize. Most teams that switch do so from T-shirt to Fibonacci as they mature, not the other way around.
What about custom scales?
Some teams create their own scales like 1, 2, 4, 8, 16 (powers of two) or simple 1 through 10. These work fine as long as the entire team agrees on what each number means. The risk with custom scales is that they often drift over time without the natural guardrails that Fibonacci and T-shirt sizing provide. If you go custom, document your calibration examples and revisit them quarterly.
Try both scales in your next estimation session
PointPoker supports Fibonacci, T-shirt, Simple 1-10, and custom scales.
Start Free Session