15 things a Professional Scrum Product Owner (PSPO) actually does

And, how often do you actually come across a PSPO that has focus on and the mandate to carry out these 15 important responsibilities?
In my approx 7 years of working with scrum, mostly as a PO, I have only once been in an environment where the PO had the trust and mandate to accomplish this. That results in a very efficient en effective process, but I have never seen it since.

If your experiences are the same (hardly any company is willing to have the PO drive the success basically), how are we going to change this as the scrum community? Without a strong and mandated PO, the development team cannot work effectively, output suffers and an image of 'Scrum not working' is reinforced. I am still trying to figure out how to change that, and would love to read your experiences.

I think the problem here is that the PO is defined as a god in most articles covering POs. I found a more practical article (https://www.scaledagilefram... that lists down the responsibilities of the PO which essentially portrays PO as primarily a Solution Team facing person, with the responsibility of ensuring that the team has had the full opportunity to understand the requirements from the stakeholders and has provided a solution that meets these requirements. This way the PO is not making the decisions about the product, but ensuring that the decision making process is solid and people are making the right decisions. This way the PO can be fully trusted because he's not validating his own decision, but mediating the decisions taken by others.

https://www.scaledagilefram...

Tend to disagree with part of your #3. I believe, we dropped the idea of "single wringable neck" for good reasons. If the Scrum Team only as a whole has the capabilities to deliver value, then value delivered is a team accountability.
IMO that´s the whole point of collaboration. No single individual alone can achieve desired outcomes, they all contribute. The original Scrum metaphor in "The New New Product Development Game"

It is a matter of definitions, or basically words. PO is responsible for turning value into the success of the product, presumably a business product, therefore a financial success is taken here into account as the only definition of "success" used. That being said, Scrum Team delivers value, however the PO "herself/himself" should be capable of turning the value to "success". At least this seems to me is a definition of success in #3. Cheers