--- title: "Backlog Refinement: Definition and Example" description: "Backlog refinement is the ongoing work of detailing, sizing and reordering backlog items. See why it matters, an example, and how Beyond Agile teaches it." canonical_url: "https://builderscamp.com/guides/glossary/backlog-refinement" date_published: "2026-09-16" date_modified: "2026-09-16" author: "Andre Albuquerque" publisher: "Builders Camp" guide_class: "glossary" --- # What Is Backlog Refinement? **TL;DR:** Backlog refinement is the ongoing activity of adding detail, sizing, and reordering items in a product backlog, so the team only ever builds what customers want and the business needs. Unlike Scrum's formal events, refinement happens continuously rather than at a fixed point in the sprint. ## What does backlog refinement mean? Backlog refinement is the process of reviewing, detailing, sizing, and reordering items in a product backlog on an ongoing basis. Per [Atlassian](https://www.atlassian.com/agile/scrum/backlog-refinement), refinement is defined in the Scrum Guide as an ongoing activity to add details, such as description, order, and size, and it is an important part of product development because it helps a team build only the features and functionality that customers want and the business needs. Unlike a scheduled Scrum event, refinement is continuous rather than limited to a specific point in the sprint, and it is ideally kept to no more than 10 percent of total sprint time. Refinement is what keeps a backlog useful rather than a graveyard of half-formed ideas that nobody ever revisits or removes. ## Why backlog refinement matters for product managers Beyond Agile treats backlog discipline as one of the clearest, most fixable signs of team health or dysfunction. The bootcamp's certification quiz states the standard directly: the Product Backlog should be regularly refined, with only items contributing to objectives remaining, and other items removed to maintain focus, warning explicitly against keeping items indefinitely just to appear responsive to every stakeholder request. The bootcamp's own Backlog Refinement template frames the practice as working, hands-on grooming, breaking down work, and clarifying [acceptance criteria](https://builderscamp.com/guides/glossary/acceptance-criteria), not a status meeting where items get discussed but nothing actually changes. ## Backlog refinement example Beyond Agile's own practical challenge surfaces a version of a broken backlog through a QA lead's complaint: stories marked "Done" in the tracker clearly are not, flagged three times in retrospectives with no change afterward. Weak refinement is part of what allows this to persist, since a backlog that never gets cleaned up or checked against real acceptance criteria leaves room for stories to slip through without real scrutiny. The bootcamp's recommended fix for this kind of dysfunction is concrete: delete backlog items that no longer align with current goals and say why, rather than letting a bloated, unrefined backlog quietly erode a team's ability to tell real progress from the appearance of progress. ## How Builders Camp teaches backlog refinement Builders Camp teaches backlog refinement inside the [Beyond Agile bootcamp](https://builderscamp.com/bootcamps/beyond-agile), directed by Andre Albuquerque, using its Backlog Refinement Miro template as a working tool for grooming items, breaking down work, and clarifying acceptance criteria. Builders Camp runs live and self-paced bootcamps in product management and AI product building. [See the Beyond Agile bootcamp](https://builderscamp.com/bootcamps/beyond-agile) for the next cohort dates. ## Frequently asked questions ### Who is responsible for backlog refinement? It is a shared, continuous effort championed by the product owner, with input from product managers, the scrum master, and representatives from the development team, not a task any one role does alone. ### How much time should refinement take? Ideally no more than about 10 percent of total sprint time, since refinement supports the sprint's work without consuming so much time that it competes with actually building. ### What is the difference between backlog refinement and sprint planning? Refinement is continuous, ongoing detail work on the backlog itself. Sprint planning is the specific event at the start of a sprint where the team selects and commits to items to build. ### What happens to backlog items that no longer align with current goals? They should be removed during refinement, with the reason shared with the team, rather than left indefinitely on a backlog that keeps growing without ever getting smaller. ### Why is refinement described as an ongoing activity rather than an event? Because the Scrum Guide itself defines it that way: an ongoing activity to add details such as description, order, and size, rather than a scheduled ceremony with a fixed agenda. ### Does backlog refinement include writing acceptance criteria? Yes. Clarifying acceptance criteria for backlog items is one of the core outputs of a good refinement session, alongside sizing and reordering. ## Sources - [Atlassian: What Is Backlog Refinement?](https://www.atlassian.com/agile/scrum/backlog-refinement) ## How this guide was made Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.