6 Tips for Effective Product Backlog Refinement - Fadi Stephan
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
Where we hear about:
- 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 progressively elaborate, size, split, and identify "Ready" product backlog items
- Use the Product Backlog Refinement canvas to help run effective refinement sessions
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 tools and techniques for your toolbox like the Product Backlog Refinement Canvas that you can use in your very next refinement session.
Find out more about Fadi Stephan on LinkedIn
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.