Regular backlog grooming: clarifying, estimating, prioritizing, splitting items.
Backlog Refinement is the regular maintenance of the Product Backlog, during which items are clarified, estimated, prioritized, and split when needed. Without Refinement, the backlog quickly becomes outdated, and Sprint Planning turns into a bottleneck as the team is forced to discuss unprepared items. The recommended rule of thumb is to invest no more than ten percent of Sprint capacity in Refinement.
The central principle is just-in-time detailing. Items near the top of the backlog that will be implemented soon must be described and estimated at a fine-grained level. Items further down are deliberately kept rough. In a typical Refinement session, the Product Owner presents an Epic or larger feature, the team asks clarifying questions, breaks the Epic into smaller User Stories, and estimates the effort. This produces a backlog that is ready for Sprint Planning without requiring detailed planning weeks in advance.
Refinement was originally known as Grooming and was renamed in the Scrum Guide in 2013. It is not a formal Scrum event with a fixed timebox but an ongoing activity that the team shapes according to its own needs.
Apply methods, don't just know them. View trainings and workshops
