Fibonacci vs T-Shirt Sizing: Choosing the Right Estimation Scale

When agile teams sit down to estimate work, they need a shared language for sizing. The two most popular approaches are the Fibonacci sequence (1, 2, 3, 5, 8, 13, 20, 40, 100) and T-shirt sizing (XS, S, M, L, XL, XXL). Both are legitimate, both are widely used, and both have passionate advocates. But they serve different purposes and work better in different contexts.

The right choice depends on your team's maturity with estimation, how you use estimates downstream, and whether you need numeric precision or just rough categorization. This guide breaks down both approaches so you can make an informed decision for your team.

Fibonacci estimation assigns numeric story point values from a modified Fibonacci sequence. The key property of this sequence is that the gap between adjacent numbers increases as the numbers grow. The jump from 1 to 2 is small (just 1 point), while the jump from 13 to 20 is large (7 points). This mirrors a fundamental truth about estimation: our ability to distinguish between effort levels decreases as complexity increases.

When teams use Fibonacci points, they build up a shared reference library over time. A "3-point story" has a specific meaning for your team — perhaps it is a new API endpoint with validation and tests. An "8" might be a feature involving multiple components, database changes, and integration testing. These reference stories become the yardstick against which all future work is measured.

Advantages of Fibonacci:

• Numeric values allow velocity calculation and sprint capacity planning
• Gaps between numbers reduce false precision debates ("Is this a 6 or a 7?")
• Widely understood across the agile community — new team members likely have experience with it
• Enables trend analysis and predictability metrics over multiple sprints
• Works well with planning poker's vote-discuss-revote cycle

Disadvantages of Fibonacci:

• New teams sometimes treat points as hours, creating frustration
• Can lead to unhealthy fixation on velocity numbers
• Requires calibration sessions to establish what each number means for your team
• Stakeholders may misinterpret points as commitments rather than estimates

T-shirt sizing replaces numbers with familiar clothing sizes: XS, S, M, L, XL, and sometimes XXL. The approach deliberately avoids numbers to prevent the temptation to do math with estimates. You cannot calculate velocity in T-shirts, and that is exactly the point for teams that want estimation to focus purely on relative sizing.

T-shirt sizing works especially well for high-level roadmap planning and backlog grooming sessions where you need to quickly bucket a large number of items into rough size categories. It is also popular with teams that include non-technical stakeholders who find numeric points confusing or intimidating.

Advantages of T-shirt sizing:

• Intuitive and accessible — everyone understands clothing sizes
• Removes the temptation to convert estimates to hours
• Faster for rough categorization of large backlogs
• Lower stress for teams new to estimation
• Works well for roadmap-level planning where precision is not needed

Disadvantages of T-shirt sizing:

• Cannot calculate velocity or sprint capacity directly
• Fewer distinct categories means less granularity (only 5-6 buckets)
• Harder to track estimation accuracy over time
• May need a "conversion table" if you also need numeric capacity planning
• Teams often disagree on the boundaries between sizes

Fibonacci points are the better choice when your team needs to plan sprint capacity, track velocity trends, or report on predictability to stakeholders. If you are doing sprint-level planning and need to answer "how much can we get done in two weeks?", you need numeric values that add up.

Fibonacci also works better for mature agile teams that have been working together long enough to have calibrated reference stories. The numeric scale rewards consistency and enables data-driven retrospectives: "Our velocity has been trending down — what changed?"

Choose Fibonacci when you need to forecast delivery dates, when you use story points for release planning, or when your organization has standardized on points for cross-team comparison (though comparing velocity between teams is generally a bad idea).

T-shirt sizing excels in early-stage estimation and high-level planning. If you are grooming a backlog of 50 items and need to quickly sort them into rough categories, T-shirts are faster and less mentally taxing than debating Fibonacci numbers for each one.

T-shirts are also the right choice for teams that are new to agile and struggling with the concept of abstract estimation. Starting with T-shirts builds the muscle of relative sizing without the baggage of numbers. Once the team is comfortable, you can optionally transition to Fibonacci if numeric tracking becomes important.

Use T-shirt sizing for product roadmap discussions, PI planning sessions with large groups, teams that include non-developers, and any context where you need "roughly how big" rather than "how many story points."

Many successful teams use both scales at different levels. T-shirt sizes at the epic or feature level during quarterly planning, then Fibonacci points at the story level during sprint planning. This gives you rough sizing for the big picture and numeric precision for sprint execution.

If you go hybrid, establish a clear mapping. For example: S = 1-3 points, M = 5-8 points, L = 13-20 points. This lets you convert between scales when needed without losing the benefits of either approach.

Some teams also use T-shirt sizing as a "first pass" before planning poker. They quickly categorize all stories by T-shirt size, then only run detailed Fibonacci estimation on the stories planned for the upcoming sprint. This is an efficient use of the team's estimation time.

There is no universally correct answer. The best estimation scale is the one your team uses consistently and finds valuable. If Fibonacci points are causing arguments about velocity targets and pressure to "hit the number," T-shirts might reduce that stress. If T-shirt sizes are too vague for meaningful sprint planning, Fibonacci provides the granularity you need.

Start with whatever feels most natural for your team. Use it for at least three or four sprints before evaluating. If it is working — meaning estimates roughly match reality and the process feels lightweight — keep it. If not, try the other approach. The estimation technique is a tool, not a religion.