Accurately estimating the effort needed to develop product backlog requirements is a challenge faced by every Scrum team. The secret? It’s not about achieving perfect precision, but about using collaborative techniques and the right level of detail at the right moment. Let’s explore the tried-and-true estimating practices that keep teams focused, adaptive, and ready for success each sprint!
The Fibonacci sequence—a mathematical pattern from the 13th century—powers some of the most effective estimation techniques in modern Agile teams.
Estimating effort is not a one-time event; it’s an ongoing process that evolves as the team learns more about the product and its requirements. Some teams dedicate a set time each day—say, 30 minutes before wrapping up—to chip away at estimation, ensuring steady progress and readiness for the next sprint.
Scrum teams typically refine their estimates across three key levels, progressing from the broadest to the most detailed:
- Product roadmap
- Release planning
- Sprint planning
The developers themselves are responsible for estimating the effort required to build requirements. The Scrum Master facilitates, and the Product Owner clarifies—but only developers doing the work make the final call.
Relative estimating is more feasible than precise estimating. It’s easier for humans to compare the size of two things than to guess an exact measurement. Scrum teams value accuracy over false precision—making relative sizing a powerful tool.
Why do you think teams struggle to make accurate estimates when dealing with large, complex requirements?
Fibonacci Numbers and Story Points
The Fibonacci sequence is a cornerstone of Agile estimation. This sequence—where each number is the sum of the two preceding ones—creates a scale that naturally reflects increasing uncertainty with bigger work items:
1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, and so on
As the numbers grow, so does the gap between them. This isn’t accidental: it mirrors the fact that it’s harder to estimate large work items accurately. The bigger the chunk, the fuzzier the picture.
A story point is the Fibonacci number assigned to an individual requirement (such as a user story).
Leonardo Pisano Bigollo, known as Fibonacci, popularized the sequence in Europe—and helped spread the Hindu-Arabic numeral system that underpins modern mathematics.
In your own words, why might Fibonacci numbers be a better choice than a simple 1–10 scale for estimating work?
A unit of measure using a Fibonacci number to represent the relative effort required to complete a user story or requirement.
A large user story or requirement, often too big to fit into a single sprint, typically estimated with higher Fibonacci numbers and broken down further before being sprint-ready.
Many software companies use story points during sprint planning to avoid debates over hours—focusing the team on what matters: comparing, breaking down, and refining work, not estimating to the minute.
- Fibonacci estimates 1–8: Requirements small enough for a sprint; these are usually user stories.
- Fibonacci 13–34: Requirements large enough for a release, but not yet ready for a sprint; these are called epics.
- Fibonacci 55–144: High-level features, too large for a release, only estimable at the roadmap level. Anything larger than 144 is a theme and must be broken down further to be actionable.
Don’t estimate requirements larger than 144—they’re too big to be meaningful! Break them down until developers can estimate with confidence.
Precise estimates are always better and mean more accurate planning.
Accuracy is more valuable than false precision. Using relative sizing like Fibonacci story points helps teams make consistent, reliable estimates—even when the exact effort is uncertain.
Think about the last time you estimated a task in your personal or professional life. Did you aim for precision or accuracy? How did that affect your outcome?
Want to go deeper? The science behind relative estimation
Human brains are naturally better at comparing items (“Is A bigger than B?”) than assigning precise values. This is known as “relative judgment.” In Scrum, using relative estimation (like Fibonacci) turns a cognitive weakness into a team strength, as it encourages discussion, reduces bias, and produces more robust forecasts over time.
- Estimation is progressively refined from roadmap to sprint level.
- Fibonacci numbers help teams deal with uncertainty and variability in work size.
Estimation Techniques: Poker and Affinity
With the Fibonacci sizes in hand, Scrum teams use several collaborative techniques to arrive at shared estimates:
- Estimation Poker: Used for smaller sets of requirements, this technique has the team assign story points together—each person plays a card, followed by discussion and consensus.
- Affinity Estimation: Used for large backlogs, requirements are rapidly sorted into groups by relative size, then mapped to Fibonacci numbers.
Gather 3–5 “requirements”—these can be tasks at home, school, or work. With a group (or by yourself for practice):
- Assign a “5” story point to a task that feels like a lower-mid-range effort.
- For each other task, decide: Is it bigger or smaller than your “5”? Assign the closest Fibonacci number.
- Discuss any disagreements and arrive at consensus.
Starting with a “5” as an anchor helps the team compare up and down the scale, making it easier to reach consensus quickly.
Practitioners report that estimation poker is not just about the number—it’s about surfacing risks, misunderstandings, and hidden complexity through conversation.
Scrum teams value accuracy more than precision. Using relative sizing is an effective way to overcome humans’ difficulty in making absolute estimates.
What is a story point?
Tap to revealA unit using a Fibonacci number to represent the relative effort required for a user story or requirement.
Why does Scrum use relative (not absolute) estimation?
Tap to revealBecause humans are more accurate comparing sizes than assigning exact values, making estimates more reliable.
What is the purpose of starting estimation with a “5”?
Tap to revealIt provides a mid-range anchor, making it easier for the team to compare and assign other story points.
Absolute estimates (exact hours or days) are always more accurate than relative estimates using story points.
The most effective Scrum teams use relative estimation techniques, like Fibonacci-based story points and collaborative activities, to achieve accurate, actionable estimates that drive successful sprints.
Estimation is a team responsibility: developers do the estimating, the Scrum Master facilitates, and the Product Owner clarifies requirements—ensuring the team owns their commitments.
Reflect on a time when your team underestimated or overestimated a project task. What factors contributed to the outcome, and how might using a technique like estimation poker have changed things?
How confident are you that you can explain the purpose and use of Fibonacci numbers in Scrum estimation?