When your Agile Requirements go Wrong, Part 2
There are many ways requirements can go wrong in Agile. In Part 2 of 4, I tackle five more requirements anti-patterns so you can avoid them.
This is a collection of my top Agile blogs. In it, you will find numerous articles on various topics such as Scrum, Product Ownership, and more.
There are many ways requirements can go wrong in Agile. In Part 2 of 4, I tackle five more requirements anti-patterns so you can avoid them.
The problem of Agile requirements going wrong is endemic; this is the first of a four-part series on what can go wrong, and how to fix it.
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.
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.