when the PO is useless
I work in a project that is very complex. Lot of math and finance analysis.
Stakeholders are expert users with deep business knowledge. Developers ate actuaries or data scientist.
As soon as I introduce them to each other, as a po, I'm out.
Development is basically made of one to one conversations, im not even invited.
My attempt to create backlog and user stories are failing, as ther are are only placeholders saying that the dev is ongoing.
I cannot decide any priority, as the developers think that stakeholders have priority over me. Stakeholders/users, want everything they ask done on the fly.
I can just listen and ask why are they late and inform my bboss.
Funny thing is that I was a mathematician myself, but my point of view is not considered useful. The scrum master is just doing cerimonies.
There is one guy that every day in the daily says: im working wit C.to implement the dashboard. Since 4 sprints. during reviews, I see something which I don't understand whether is working or not. The only user, declares himself happy and says that needs more work. If she leaves the company, I don't know what we achieved.
I don't understand what to do in this situation....
Are you accountable for all of the investments and ROI for this product over its lifetime?
Is there a budget for example, and do you hold it?
First I would suggest work closely with the stakeholders and build relationships. It is not neccessary to understand the technical detail, but important is to understand which functionality is important to stakeholders, so that you can order the Product backlog.
It's perfectly acceptable to add Product Backlog items in a skeletal form, as long as you can determine the importance and priority of each item from stakeholder discussions. In situations like this, it's common for the Product Owner to rely on developers (subject matter experts) and stakeholders to work out the finer details of the Product Backlog items. In fact, it's preferable for this close collaboration, rather than having all communication pass through the Product Owner. Then by injecting yourself into the conversations, you will over time learn more of the detail and the system. I understand the frustration, but don't be concerned as it is not uncommon.