Beyond Fibonacci: When Numbers Hurt

The Fibonacci sequence (1, 2, 3, 5, 8, 13...) has been the gold standard for agile estimation for decades. It beautifully forces teams to recognize a core truth of software development: the bigger a task gets, the more uncertainty it holds.

But sometimes, numbers just get in the way.

Breaking the Points-to-Hours Trap

When teams fixate on numbers, they inevitably start equating them to hours. You’ll hear things in planning like, "Well, a 5 is roughly two days of work, so this one should be an 8."

Once that happens, you are no longer estimating complexity; you are guessing time. And if there is one thing developers are notoriously bad at, it is guessing exactly how many hours a task will take.

If your team is stuck in the "points equal hours" trap, it’s time to abandon numbers entirely.

Switching to T-Shirt sizing (XS, S, M, L, XL) completely breaks that mental link. You can't easily convert a "Medium" into a specific number of days. It forces the team's brain back to what matters: relative sizing. Is this task bigger or smaller than the one we did yesterday?

Don't let your process dictate your tools. Our online estimate poker tool lets you swap out Fibonacci for T-shirt sizes (or entirely custom decks) with a single click. Change the deck, change the conversation.