There’s no planning in Agile – is there?
It’s a common misconception that there’s no planning in Agile (there is), and the Product Owner is responsible, but a lot can still go wrong.
Unlike Projects, which are temporary endeavors, Products are like living things, with a full life cycle from inception to sunsetting; while a Product exists it should have a backlog.
It’s a common misconception that there’s no planning in Agile (there is), and the Product Owner is responsible, but a lot can still go wrong.
What happens when a Product Owner doesn’t have control or even visibility into the product’s budget? No one will know if it’s successful.
Value in agile is an elusive topic to cover; it means something different to everyone. So, what does value mean to you as a Product Owner?
In this subseries’s third and last blog, I tackle the final five ways that Product Owners should not behave. Watch out for these behaviors.
If your Product Owner used to be a developer or has a technical background rather than business experience, you may run into a few issues.
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.
Some people can jump right into the Product Owner role, but for most, training provides an essential foundation to do the job successfully.
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.