refinement
/rɪˈfaɪnmənt/noun
Refinement is the ongoing clarification, breakdown and estimation of backlog work so the team understands what each item involves.
During refinement, the team discussed exceptions and split the feature into two smaller backlog items.
During refinement, the team discusses future work before starting implementation. The Glossary · In briefproduct ownerIn Scrum, the product owner is accountable for maximizing product value and managing the product backlog. They order the work and communicate the product goal.Read more, developers and other participants share knowledge, ask questions and add detail to backlog items. They establish which problem an item solves and what is needed to plan the work.
What is discussed during refinement?
The team can discuss intended behaviour, user scenarios, dependencies and risks. It clarifies Glossary · In briefacceptance criteriaAcceptance criteria are agreed, testable conditions that a product, feature or change must meet to be accepted.Read more where needed and estimates the size of the work. A large backlog item can be split into smaller parts that each provide value.
Not every detail needs to be settled in advance. The item mainly needs to be clear enough to determine its priority and approach. The amount of detail depends on the work and the uncertainties still to be investigated.
Refinement is an ongoing process
Teams often schedule a regular refinement session. Within Scrum, however, refinement is not a separate, mandatory event. Backlog items can be updated throughout the sprint as new information becomes available.
Refinement also differs from sprint planning. Refinement investigates and clarifies possible future work. During sprint planning, the team chooses work that contributes to the sprint goal and that it expects to complete in that sprint. Careful refinement helps, but does not guarantee an item will enter the next sprint.