In this energizing 38th Hands-on Agile session, Roman Pichler delved into your questions on the role of the Product Owner. The topics range from product manager vs. Product Owner vs. business analyst to the right size of a Product Backlog to linking product vision to Product Goal and Sprint Goal.
📺 Watch the video now: Roman Pichler: The Product Owner — Hands-on-Agile #38.
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. Neglecting the critical Scrum artifact for continuous value creation is one of the common Scrum anti-patterns. If your Scrum Team strives to make your customers’ lives easier Sprint after Sprint, beware of the oversized Product Backlog.
📺 Join me and explore the consequences of inadequate Product Backlog management in less than three minutes.
Update: I am running a poll on LinkedIn—join the voting: “What reasons have you observed why Scrum Teams stuff their Product Backlogs — a very costly pattern that diminishes ROI and value creation?”
There are plenty of Product Owner failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.
Explore with me three widespread examples of how Product Owners fail their team in three short video clips, totaling 6 minutes and 9 seconds.
Make no mistake: Your Product Backlog is the last line of defense preventing your Scrum Team from becoming a feature factory; hence Product Backlog defense is vital: Figure out a process that creates value for your customers. Moreover, have the courage — and the discipline — to defend it at all costs.
A few weeks, Scrum.org hosted a webinar on Product Backlog anti-patterns with me, which left several questions unanswered as we ran out of time. Hence please find following my answers to the additional 18 questions I could not answer during the webinar Product Backlog anti-patterns Q&A session.
Garbage in, garbage out: No matter whether your team chose Scrum for the right purpose—solving complex, adaptive problems. No matter whether your Scrum Team’s product quality is top-notch or whether your teammates embrace self-management to the fullest. If your Product Backlog is not up to the job, all of these accomplishments will account for little, as your team will provide less value to its customers than possible. Here is where the forensic Product Backlog analysis steps in, a light-weight, simple practice to help Product Owners and Scrum Masters unearth anti-patterns that led to your low-value Product Backlog.
Learn more on how a piece of paper and a pencil can turn around the perception of your Scrum Team among stakeholders and customers.
