Note: This is PART FIVE of a six-part series on Backlog Refinement.

<< Go Back to Part 4
Skip Ahead to Part 6 >>

Backlog Grooming includes the team responsibility for ensuring that the ENTIRE Product Backlog is estimated at all times. This means that, while we will spend 70% of our time discussing, slicing, and estimating the highest priority items, we must still do “deep dives” in the backlog, ensuring that all items have an estimate on them.

Estimating large items in story points is actually EASIER than estimating smaller items, due to the fact that the large items are lacking significant detail and, therefore, the amount of detail you have to discuss and review is limited. Because of the lack of detail, your accuracy is similarly reduced. However, because there are usually a large number of items to be estimated (more than 40 is sufficient), statistically you will estimate some higher and some lower than they will actually be – meaning that the average of the “wrongness” of your estimates will actually be reasonably precise. Also, remember that you will be discussing, slicing, and re-estimating these items anyway as the project progresses. Greater precision will come later.

Given that we have already covered how to do estimations, this blog post simply seeks to provide some tips you can use to help your teams successfully do large item estimation.

Don’t spend a lot of time on each item. You only know what you have in front of you and what your Product Owner can quickly provide. Don’t solve the problem (i.e., don’t figure out how you’re going to build it). Give yourself a time limit (perhaps 5 or 10 minutes). Then estimate.

If you can, capture the information you discuss in the process of estimating the item as comments on the item. It may help later in remembering what you discussed when you did the estimation.

Compare the larger items to the backlog items you’ve already estimated. If a backlog item seems to be a little harder than your 5 story point items, maybe it’s an 8. Harder than that? How about 13?

Don’t just come up with a bunch of new story point values (e.g., 20, 45, 60, 90, etc.). Extend the point sequence you are already using to accommodate the larger items. If you are using a Fibonacci sequence, you’ve probably already used 1, 2, 3, 5, 8, and 13. The next numbers in the sequence are 21, 34, and 55. The concept of a Fibonacci or doubling sequence works — don’t break it.

If an item is REALLY big and complicated, try slicing it into two or three smaller items. This is an expensive option (because of the effort involved), however, and a last option should all attempts to estimate fail.

Like small item estimation, large item estimation takes practice. The more your team does it, the better they get. For that reason, you might want to estimate ten or so large items and then do a quick review of your estimates to see if they still make sense.

Take your time. Follow the process – it works.

Good luck!

Be sure to continue by reading part six!

Note: This is PART FIVE of a six-part series on Backlog Refinement.

<< Go Back to Part 4
Skip Ahead to Part 6 >>

FEATURED RESOURCE:

FEATURED RESOURCE:

Story Slicing Reference Sheet

Download Now!

Swipe this FREE DOWNLOAD to supercharge your PBI slicing.

Normally available ONLY to Artisan students, we’re offering this handy guide to you for a limited time!

More About #Backlogs

Gearing a Team for Maximum Outcomes

Creating a maximum outcome team is every ScrumMaster’s goal, but you must first understand how great teams form and what YOU need to do to create a great team.

It’s All About Value

One small change can make a BIG difference to your Product Owner success. Before worrying about putting value on backlog items, here's some simple tips.

Simplify Your Work by Slicing

When slicing a backlog item, we're taking a complex problem and paring it down into smaller problems, which are easier to solve and build.

Speeding up Your Scrum Teams

Effective Scrum use is more than Sprint Planning, Daily Scrums, and so on. To see a big difference in your team's Sprints, make these workflow changes.

DONEness Definitions (DoD)

What's the one thing YOU could do as a Scrum Master to improve your team's reliability, quality, and productivity? Read on and find out!

Keep Your Eyes on the Sprint Goal

In this article, we'll discuss how a team bares responsibility for the Sprint and what should be done if they can’t get everything done they committed to.

Plan Only Small Backlog Items

Bigger requirements are more complex, which typically have greater risk, which leads to more cost and/or waste. In other words, bigger is DEFINITELY not better!