Are your Sprint planning meetings taking longer and longer each Sprint. Do you find yourself discussing new stories that the team is seeing for the very first time? Are some of the stories vague, complex, or very large? Is the priority unclear? These are all symptoms of ineffective Product Backlog Refinement which results in painful Sprint planning meetings. Team Product Backlog Refinement is an important activity that is frequently overlooked. The team is usually focused on delivering features for the current Sprint and devotes little time to work with the Product owner to prepare for the upcoming Sprints. Come to this session to understand the importance of Product Backlog Refinement, the different types of activities that are needed, when to perform each type, who should attend and how to make the most of everyone's time. Understand the importance of having a Definition of Ready, learn how to do progressive elaboration on user stories and how to expand on your acceptance criteria. Leave with tips and technique for conducting effective Product Backlog Refinement before your very next Sprint planning meeting.

 
 

Outline/Structure of the Talk

This will be a new 45 minute talk using my preferred presentation style of using a slide deck of mostly pictures and examples that cover the topic at hand. Below is an outline of the presentation:

  • Introduction
  • Product Backlog Refinement
  • Why/Who/What/When/How
  • Timebox and schedule
  • Different types
  • Prioritization
  • Evaluating new discovery
  • Story decomposition
  • Required attendees
  • 80/20 rule
  • User Story life cycle and progressive elaboration
  • Working towards the Definition of Ready
  • Summary

Learning Outcome

  • Signs of poor Product Backlog Refinement
  • Life cycle of a user story and progressive elaboration
  • What to do during Product Backlog Refinement, when to perform each type of activity, who should attend
  • Working towards a Definition of Ready

Target Audience

Product Owners, Business Analysts, ScrumMasters, and team members in general

schedule Submitted 4 years ago

Public Feedback

comment Suggest improvements to the Speaker