During a product backlog refinement meeting, the team and product owner discuss the top items on the product backlog. The team is given a chance to ask the questions that would normally arise during sprint planning: What should we do if the user enters invalid data here? 26 мая 2015 г.
What happens in backlog Refinement meeting?
In the Backlog Refinement Meeting, the team estimates the amount of effort they would expend to complete items in the Product Backlog and provides other technical information to help the Product Owner prioritize them. (The team should collaborate together to produce one jointly-owned estimate for an item.)
How do you perform a backlog refinement?
Conducting a Backlog Refinement (Grooming)1Create and Refine. In preparation of the Backlog Refinement (Grooming), the Product Owner should remove user stories that are no longer relevant and create new ones based on the Scrum Team's discoveries from the previous sprint. ... 2Estimate. ... 3Prioritize. ... 4Good Reads.Conducting a Backlog Refinement (Grooming) - Tech at GSA
What happens in refinement sessions?
The refinement sessions usually happen once or twice a sprint usually just before the end of the last week. The purpose of the meeting is to provide the development team with an overview and clarification of the backlog. The teams can focus on the items with higher priority for longer duration.
What should not be doing during a backlog Refinement meeting?
What NOT to do during Product Backlog Refinement?17 traps that we must avoid during backlog refinement. ... 21 — Do not bring solutions. ... 32 — Do not accept the word impossible. ... 43 — Do not estimate in hours. ... 54 — Do not fall into endless technical discussions. ... 65 — Do not split User Stories into implementation tasks.What NOT to do during Product Backlog Refinement? | Serious Scrum
More useful articles on a similar topic 👇
How often should you groom the backlog?How long are backlog refinement meetings?