Backlog grooming. Discuss and prepare backlog items.

What is backlog grooming? What advantages does it offer and how do you carry out a backlog grooming?


What is backlog grooming?

Like a garden, the product backlog of your Scrum project also has to be trimmed and maintained. Which product items (user stories, bugs, technical stories, etc) will you implement in your next sprint? Are they formulated clearly enough and does you scope allow them to be implemented in one sprint? To clarify these questions, the development team and the product owner meet for some backlog grooming (or backlog refinement, backlog estimation or story time). Here, you take the items more precisely under the magnifying glass, add details, clear up unclearness, estimate workloads, change priorities, add new items, or remove entire items. Backlog grooming is not an officially defined Scrum meeting, like, for example, the daily Scrum or sprint planning. However the Scrum guide advises carrying out backlog grooming or refinement regularly.

Read here to learn more about backlogs >>

What does the Scrum guide say about this?

„Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.” *