Agile beyond Scrum: How to help the PO build the right thing at the right time?
- Hello everybody,
Let's say you have a disciplined team that believes in Agile methods and has fully implemented methods like Scrum and XP, to the extent that the PO is considered an integral member of the team and sits in the same room as the developers, and solutions to the top-priority requirements are delivered within the agreed timeframe while keeping a high code quality. However, let's also say that some of the solutions delivered aren't used at all or their use doesn't justify the development costs. How do you solve this?
Without having any practical experience using it, it seems to me like adopting Lean would solve the problem, but this is a medium to long term solution. In the very short term, it can be required that each epic/story had a metric to measure its success over a period of time (e.g., "the feature is used by at least 10 users within the first month") and if the expectations aren't met then the feature is dropped, which should keep maintenance costs down and also make it easier to implement future features. Do they sound like sensible short-, medium- and long-term solutions?
Any suggestions? Pointers to other resources?
Thanks in advance.
- Hello Gustavo
Your problem would appear to come from who is specifying the requirements (user stories) and who is ordering them.
The Scrum Guide says that the PO has 'sole responsibility' for the Product Backlog but that person is not expected to do 'it' all by themselves, they need to discover all the stakeholders and get the User Stories from them and facilitate the discussions on the order.
Is your PO doing it all by him/herself?
If not, then we can start looking at other possible problems