Backlog Refinement Part 2: How Small is Small Enough?
Note: This is PART TWO of a six-part series on Backlog Refinement.
As previously discussed, Backlog Refinement is a workshop held to take large backlog items and slice them down into smaller pieces. More specifically, we discussed the three major goals of Backlog Refinement:
Estimate backlog items that have no estimate
Correct estimates that appear to be considerably off target
Discuss backlog items and divide them into smaller component pieces (slicing).
In this blog post, I want to discuss how we know how small to make our backlog items before we stop refining them and move on to something else. If the backlog item is too large at the beginning of the Sprint, we run the risk of problems during Sprint Planning and during the Sprint. On the other hand, if we slice the item too small, we’re wasting time discussing something that can be easily dealt with in Sprint Planning.
Many experts currently agree that the “right” size for a backlog item is one that 2 or 3 people on your team can complete in less than a week (this concept, getting people working on one backlog item collaboratively is called “swarming”). This maximizes the Scrum team’s flexibility (small backlog items are easier to “fit” into a Sprint should some re-planning be necessary during a Sprint) while still allowing the team to do “functional” slicing during Backlog Refinement (as opposed to solving the backlog item).
So, what is small enough that 2 or 3 people on your team can finish an item is less than a week? That will have to be up to your team. Every team is different; the best thing to do for a new team is let them make their best guess and then look at how it worked out at Sprint Retrospective (then, you can look at the Sprint Burndown and see how long each backlog item took to complete from the first day to the last). If the backlog items are taking too long, slice them down further. Eventually, the team will get an idea of the proper size based on the story point size they are putting on the backlog items (for example, 5 point items may seem too big – then the team knows to slice to sizes of 1, 2, or 3 story points).
In Backlog Refinement, once a backlog item is refined down to the “ready” range, stop. Don’t refine it further. Any remaining discussion can wait until Sprint Planning. Do not solve or slice the backlog item into tasks. Move on to another backlog item.
In the next installment, we’ll talk about how many backlog items you need to slice before you should stop holding Backlog Refinement meetings during the current Sprint. Continue to part three of this blog post!
Note: This is PART TWO of a six-part series on Backlog Refinement.
