6 Tips for Effective Product Backlog Refinement
Are your Sprint planning meetings taking longer and longer each Sprint? Are some of the stories vague, complex, or very large? Do you regularly reach the end of the Sprint and have unfinished user stories that just get rolled over onto the next Sprint? These are all symptoms of ineffective Product Backlog Refinement which results in painful Sprint planning meetings and unmet Sprint Goals. Product Backlog Refinement is an important activity that is frequently overlooked. Come to this session to understand the importance of Product Backlog Refinement as we cover 6 tips to run effective product backlog refinement sessions. Learn how to progressively elaborate on user stories, size them, split them, and get them "ready" for upcoming Sprints. Leave with new techniques for your toolbox that you can use in your very next refinement session.
Outline/Structure of the Talk
This session will be interactive lecture style with polls and 2 short group discussions. The first is an opening connection exercise to discuss and answer these questions:
How often do you do refinement?
How far ahead do you refine?
What's the agenda like?
The second group discussion is a connection exercise on the definition of ready. What does your definition of ready look like?
The 6 tips for effective product backlog refinement are based on this blog post https://www.kaizenko.com/6-tips-for-effective-product-backlog-refinement/
The agenda will follow the 6 tips:
Group discussion 1
Tip 1 - Ensure the right people are participating
Tip 2 - Allocate the appropriate time
Tip 3 - Progressively elaborate
Tip 4 - Size and split
Group discussion 2
Tip 5 - Create a Definition of Ready
Tip 6 - Address what has changed
* Recognize the importance of Product Backlog Refinement and progressive elaboration
* Identify the right participants in Product Backlog Refinement as well as the right amount of time to dedicate to Product Backlog Refinement
* Understand how to properly size and split product backlog items
* Understand how to properly use a Definition of Ready
* Use the Product Backlog Refinement Canvas as a template to run effective Product Backlog Refinement sessions