Agile Estimation Techniques
The real value of estimation is not the number you write down. It is the conversation that gets you there.
When your team estimates a piece of work, the number matters far less than the conversation that produces it. Estimation is a forcing function for alignment: it surfaces assumptions, reveals gaps in understanding, and gets everyone on the same page before work begins.
Consider what happens when the person who "was going to take this ticket" is suddenly unavailable. If they estimated alone, critical context walks out the door with them. But when the whole team estimated together, everyone already knows why that work matters and how they planned to approach it. The team adapts and keeps moving.
This shared understanding is what makes teams resilient. Estimation sessions create space to:
- Discuss different approaches before committing to one
- Learn from colleagues who have solved similar problems
- Spot risks early when they are cheap to address
- Build collective ownership of the work ahead
The techniques that follow are simply structures for having these conversations. Whether you use T-shirt sizes, Fibonacci numbers, or something else, the goal is the same: get the team talking, learning, and aligned.
T-shirt sizing is one of the most accessible estimation techniques. Small, Medium, Large, Extra-Large. Everyone understands what these mean, which makes the conversation easier to start.
The product owner introduces a piece of work and explains it as clearly as possible. Then the real estimation begins: the team asks questions. What problem are we actually solving? What have we tried before? What could go wrong?
These questions often reveal that people had different assumptions. That is exactly what you want. Better to discover now that one developer assumed a "simple" change and another spotted a major dependency.
Each team member then indicates their estimate. When there is quick consensus, great. When there is not, you have found something worth discussing. The outliers often hold information the rest of the team needs to hear.
By the time you agree on a size, everyone understands what is being built and why. That shared context is what keeps the team moving when plans change.
The Fibonacci sequence (1, 2, 3, 5, 8, 13, 21...) reflects a simple truth: as work gets larger, our ability to estimate precisely decreases. The growing gaps between numbers force teams to make real choices rather than debating whether something is a 14 or a 15.
Most teams also include a question mark for "I need more information" and an infinity symbol for "this is too big to estimate." These are signals to pause and have a different conversation: What would we need to learn? How could we break this down?
The estimation process is the same as with T-shirt sizes. Introduce the work, discuss, vote, and talk through any differences. The conversation matters more than which scale you choose.