“Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items.” Source – Scrum.org

Activities

• Product Vision: The Product Owner is responsible for making sure all team members know and understand the product vision.
• User Story Roadmap: As with the vision the Product Owner is responsible for making sure the team understand the scope of the roadmap.
• Outline Backlog Stories: If at this stage the stories have been prepared then the Product owner will run through the detail of the story and assumptions made.
• Refine Story Detail: The full Scrum Team is responsible for refining and adding detail to the stories / adding missing stories. Throughout the process each member should add detail, it is not one persons job to scribe, it is a collaborative effort.
• Dev Huddle: After a story is refined and the detail is understood by the team the Dev team should have a separate ‘huddle’ to build out dev tasks / add detail to achieve the story.
• Add Estimates: The development team will story point or provide time estimates but the full team must discuss and jointly agree
• Order Items in the Backlog: Although ultimately the PO may have the final say in the backlog order, the full team should agree and provide feedback. The Dev team might need to reorder to ensure tickets are dev’d and released in a sensible order to align with technical requirements

Dev Huddle