|Scott Ambler's Role of Product Owner|
If you are a Product Owner and you struggle to partner effectively with the various stakeholders in your company or organization, rest assured that you are NOT alone. Depending on the product you responsible for and size of your organization you may have numerous stakeholders and need to develop ways to coordinate among so many people. We all have limited time, so we need to determine how to invest your it most effectively to deliver value. In traditional project management, a suggested technique is to prioritize stakeholders based on their influence and interest so you can identify who you want to manage closely, keep satisfied, keep informed, and monitor with minimum effort.
The problem with this approach is that it is a power grid and emphasizes a stakeholder's influence, instead of knowledge or value, that a stakeholder can provide to a product owner and agile team. It positions the stakeholder as a power broker that the team serves, rather than a partner who works with it the team.
I like the concept of a simple matrix for prioritizing stakeholders, however, I choose not to use the power or influence of the stakeholder as an axis. Instead, I modify the grid to focus on the value the stakeholders can provide the team. I define value as knowledge that can take many forms. It could be domain expertise, understanding of customer needs, business acumen, technical know-how, and the list goes on.
My form of the stakeholder prioritization matrix looks like this:
- High Knowledge / High Interest = Stakeholders that you partner closely with
These are the stakeholders require little effort to involve and willingly work with the team. As a product owner, I identify touch points (development / updates to product roadmap, prior / following release planning, during backlog grooming sessions) to keep these stakeholders in the loop and often seek their counsel.
- High Knowledge / Low Interest = Stakeholders that you consult with (and try to move to high interest category)
These are stakeholders that you want to involve but they are either too busy, or may not (yet) see the value to them helping the team. I seek to convert these stakeholders to willing partners (i.e., high interest) by . I seek
- Low Knowledge / High Interest = Stakeholders who you keep informed
Agile teams believe in transparency. I believe demos should and any communication of team progress should be made available to anyone who is interested. You may discover that one of these stakeholders deep knowledge in an area that you were unaware of.
- Low Knowledge / Low Interest = Stakeholders who have an open door in get more involvedThese stakeholders are welcome to attend demos or express interest in becoming more informed, but I don't go out of my way to involve them.
If you have a number of stakeholders and find it difficult to keep up, this technique might help you prioritize your efforts accordingly. While this post is geard at Agile product Owners, it is useful to others who work with Stakeholders on a diaily basis.