When Product Owners cause Scrum Events to go Bad
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.
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?
Product Ownership is a difficult job, especially if you’re not an expert in your industry, market, competition, business, and the product.
If one thing spells the success or doom of a product, it’s the Product Owner. This blog explores Organizational Product Owner Anti-patterns.
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.