When a Product Owner isn’t Held Accountable
Product Owners need to be accountable for product outcomes, but sometimes they aren’t. Learn more about the anti-patterns you should avoid.
The Agile Product Owner role on a Scrum Team is THE key to success. Check out this blog collection covering the skills and traits necessary to succeed.
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.
There are many problems and struggles that can occur between Product Owners and their stakeholders. Thankfully, most of them are avoidable.
Have you ever seen a Product Owner cause Scrum events to go bad? I have, and it’s not pretty. Read on to learn what NOT to do if you’re a PO.
What happens if you have an uncommitted Product Owners? When a Product Owner isn’t interested, available, or engaged, you are in for trouble.
Some people can jump right into the Product Owner role, but for most, training provides an essential foundation to do the job successfully.
Product Owners are inherently leaders. To succeed, Product Owners must navigate every level of an organization, from the Help Desk to the CEO.
It’s a fact: The Product Owner is indeed a member of the Scrum Team. But when the PO doesn’t act like a team member, you’re in for trouble.
Having a vision aligned to the strategy of our product is like having a north star to guide you. Without one, you will probably fail.
Unfortunately, quality is often skipped or overlooked when developing products using an Agile approach. So, who owns quality in Scrum?