Product Backlog Refinement
When
- During the Sprint.
How Long
- Time-boxed to a max of 1 hour per week.
What happens:
- Part 1: Product Owner provides the priorities and the sprint goals for the upcoming sprints?
- Part 2: Team to provide feedback on how will the chosen work get done?
NOTE: Only the Dev Team can assess what it can accomplish over the upcoming sprint.
Techniques for a successful Product Backlog Refinement
- Setting meeting guideline (etiquette) that everyone agrees to
- What are our sprint goals for the upcoming sprint?
- PO to identify, present and discuss priorities with team
- Show list of prioritized EPICs, related to upcoming Sprint Goals
- Review EPIC description and benefits
- Review each user story related to each EPIC
- Team to work on user story definition of ready
- Review user story format (as a ____ I want to ____ so that ____)
- Write and confirm acceptance criteria (test that__; validate that__; verify that__; confirm that__)
- Team to estimate user stories and provide feedback on size/effort and complexity
- Team to break story if too big
- Team to provide feedback if any research needed before development
- Use the team’s scrum board to create and break down user stories (manual or electronic)