Top 10 Problems with Product Owners in Scrum
Without a caring, competent Product Owner, most products will fail to come to fruition, earn and retain market share, and evolve.
As a member of a Scrum Team, you have the accountability to keep your commitments.
Without a caring, competent Product Owner, most products will fail to come to fruition, earn and retain market share, and evolve.
I can’t tell you how many times I have seen Scrum go wrong. If you want the perfect recipe for screwing up Scrum, you’re in the right place.
There are only three official roles in Scrum, but there’s widespread confusion about the roles and what each one is responsible for.
Product Owners need to be accountable for product outcomes, but sometimes they aren’t. Learn more about the anti-patterns you should avoid.
Managing the Product Backlog is a big job, and there are many ways it can go epically wrong. Learn about the top 5 ways you can screw it up.
I have worked with good and bad Agile Product Owners, and I found some sure signs that a Product Owner is doomed to fail. Learn what they are.
Agile teams are fully cross-functional so they can create a done increment each sprint. But what does that mean? Explore the official roles.
Can the Scrum Master be a Developer on a Scrum Team, too? Join me in exploring why (or why not) a Scrum Master could have these dual roles.
The Product Owner is the KEY role on any agile Scrum Team. This role (now known as an “accountability”) is also the most difficult. The tagline most often associated with a PO is “value maximizer”. I love the sentiment, but there is so much more to the role than that. “The Product Owner is accountable …