Why is backlog grooming not a formal scrum event?

I recently received an email from one of my blog followers, and she asked me why is backlog grooming not a formal scrum event? I want to share with you my thought on this question today.

What is backlog grooming? Who should attend and how long should it take?

Let’s start by making it easy to keep, the process of refining backlog items by adding detail, estimates, and prioritising those that need to start first is backlog grooming. It’s simply something that many have found to be beneficial and can contribute to a sprint-planning meeting that is more effective.

Since the product owner is in charge of leading backlog grooming, you must encourage each developer to engage in backlog grooming sessions depending on your company’s structure. Also, you can invite any other individual who has valuable user insights related to the backlog.

Per the Scrum Guide, backlog grooming usually consumes no more than 10% of the Development Team’s capacity. I would recommend that your grooming meeting cap at 60 min. This time box will inspire participants to remain focused and keep the discussion on track.

Why is backlog grooming not a formal scrum event?

For answering the question, first, we need to answer this question, Does every Scrum Team have to do backlog grooming in every Sprint? Based on the Scrum Guide, the Product Owner is responsible for the Product Backlog, and Product Owner needs to decide running backlog grooming or no, so backlog grooming doesn’t have to happen. Based on above the answer to the question is simple, NO.

Since backlog grooming included in Sprint, it is not a Scrum event itself. However, it is a recommended practice that can do in many forms.

My personal experience

For me, every Wednesday, a new Sprint begins, and backlog grooming sessions held every Tuesday. Backlog grooming helps Product Owner and me to ensure that tasks are ready for Sprint Planning at some future point. We aim to remove most risk/uncertainty regarding the business criteria set out for the development team to cover by doing backlog grooming.

Thanks for reading the Scrumsaturday.com! Take a minute to follow me on Twitter if you enjoyed this post and want to see more.