Estimation and Story Points in Scrum: A Simple Guide
Estimation helps a Scrum Team develop a shared understanding of the size and complexity of Product Backlog items.
Scrum does not require a specific estimation technique. Teams can choose an approach that works for their product and circumstances.
What Is Estimation?
Estimation is the process of assessing how much effort, complexity, uncertainty or work may be involved in a Product Backlog item.
The purpose is not to predict the future perfectly. It is to support better conversations and planning.
Who Estimates the Work?
The Developers who will perform the work are responsible for sizing the work.
The Product Owner can provide context and help clarify trade-offs, but should not dictate the estimate.
An estimate is not a commitment to complete a specific amount of work.
What Are Story Points?
Story Points are a relative way of comparing the size of Product Backlog items.
They can take several factors into account, such as:
- Amount of work
- Complexity
- Uncertainty
- Technical difficulty
Example
Suppose a team uses the following Story Point scale:
The numbers do not represent hours or days. They represent relative size.
Why Relative Estimation?
It can be difficult to predict exactly how many hours a piece of work will require.
Comparing items with one another can be easier.
If Story A is considered twice as large and complex as Story B, the team might give them 8 and 4 points.
Story Points Are Not Hours
A common mistake is treating Story Points as a direct conversion to hours.
For example:
1 Story Point = 4 hours
Story Points are intended to represent relative size, not a fixed amount of time.
Common Estimation Techniques
- Story Points — compare relative size.
- T-Shirt Sizes — use S, M, L, XL and similar relative categories.
- Planning Poker — team members independently estimate and then discuss differences.
- Bucket System — quickly place items into predefined size categories.
What If Estimates Are Different?
Different estimates are useful because they can reveal different assumptions or levels of understanding.
Instead of immediately choosing the highest or lowest number, the team should discuss why the estimates differ.
"Why do you think this item is larger?"
"What assumption are we making?"
"Is there something we have not understood yet?"
Common Mistakes
What Is the Scrum Master's Role?
The Scrum Master helps the team understand useful estimation practices and facilitates healthy conversations when needed.
The Scrum Master should not use Story Points as a tool for controlling or ranking Developers.
Estimation is primarily about creating understanding, not creating a perfect prediction.
Key Takeaway
Story Points are one possible technique for relative sizing. They are not mandatory in Scrum and they are not units of time.
The best estimation approach is one that helps the team understand the work and make useful decisions.