Scrum Product Owner Anti-Patterns (10) – The Interfering Product Owner (Hands-on Agile Webinar #6)
625 بار بازدید -
6 سال پیش
-
NEWSLETTER — join 18,000 peers:
NEWSLETTER — join 18,000 peers: https://age-of-product.com/subscribe/...
START FROM EPISODE #1: Scrum Product Owner Anti-Patterns (0)...
If you are working as a product owner, there is — very likely — room for improvement. I curated the most common product owner anti-patterns to help you up your game. If you like to improve on those anti-patterns that you recognize why don’t you ask the scrum master and the team for support? The product owner anti-patterns list is a good starting point for a mutually beneficial retrospective.
According to the Scrum Guide, the product owner is sole and accountable person optimizing the work of the engineers. In other words, the product owner has ideas or identifies ideas, or at least he or she curates suitable ideas from wherever and validates them whether those ideas are “product backlog worthy” or not. In my experience, this approach turns the product owner into the Achilles heel — or bottleneck by design — of the whole process. If you "remove" the PO as an independent and respected role, for example, by sticking with your organizations' stage-gate process, Scrum easily mutates into a Waterfall 2.0 process.
This Hands-on Agile mini-series addresses 12 familiar product owner anti-patterns interfering with the concept of the Scrum product owner role. Learn how to improve your professional performance by avoiding the typical product owner mistakes: from oversized product backlogs and prioritization by proxy, to be absent during the sprint, and outing yourself as a loner during the sprint review.
This episode covers the product owner who cannot let go product backlog items once they become sprint backlog items. For example, the product owner increases the scope of a user story. Or, he or she changes acceptance criteria once the team accepted the issue into the sprint backlog. (There is a clear line: before a product backlog item turns into a sprint backlog item the product owner is responsible. However, once it moves from one backlog to the other, the development team becomes responsible. If changes become acute during the sprint the team will collaboratively decide on how to handle them.)
HOST: Stefan Wolpers
NEWSLETTER: Learn about new webinars in advance: https://age-of-product.com/subscribe/...
BLOG: “Product Owner Anti-Patterns”: https://age-of-product.com/product-ow...
SLIDEDECK: https://www.slideshare.net/wolpers1/h...
START FROM EPISODE #1: Scrum Product Owner Anti-Patterns (0)...
If you are working as a product owner, there is — very likely — room for improvement. I curated the most common product owner anti-patterns to help you up your game. If you like to improve on those anti-patterns that you recognize why don’t you ask the scrum master and the team for support? The product owner anti-patterns list is a good starting point for a mutually beneficial retrospective.
According to the Scrum Guide, the product owner is sole and accountable person optimizing the work of the engineers. In other words, the product owner has ideas or identifies ideas, or at least he or she curates suitable ideas from wherever and validates them whether those ideas are “product backlog worthy” or not. In my experience, this approach turns the product owner into the Achilles heel — or bottleneck by design — of the whole process. If you "remove" the PO as an independent and respected role, for example, by sticking with your organizations' stage-gate process, Scrum easily mutates into a Waterfall 2.0 process.
This Hands-on Agile mini-series addresses 12 familiar product owner anti-patterns interfering with the concept of the Scrum product owner role. Learn how to improve your professional performance by avoiding the typical product owner mistakes: from oversized product backlogs and prioritization by proxy, to be absent during the sprint, and outing yourself as a loner during the sprint review.
This episode covers the product owner who cannot let go product backlog items once they become sprint backlog items. For example, the product owner increases the scope of a user story. Or, he or she changes acceptance criteria once the team accepted the issue into the sprint backlog. (There is a clear line: before a product backlog item turns into a sprint backlog item the product owner is responsible. However, once it moves from one backlog to the other, the development team becomes responsible. If changes become acute during the sprint the team will collaboratively decide on how to handle them.)
HOST: Stefan Wolpers
NEWSLETTER: Learn about new webinars in advance: https://age-of-product.com/subscribe/...
BLOG: “Product Owner Anti-Patterns”: https://age-of-product.com/product-ow...
SLIDEDECK: https://www.slideshare.net/wolpers1/h...
6 سال پیش
در تاریخ 1397/04/01 منتشر شده
است.
625
بـار بازدید شده