Embedded Files
This is a reference resource intended to be linked to in order to provide just a little more insight in an easily digestible format. This is not intended to introduce the concept as a standalone article.
Stakeholder Map
Stakeholder Map
The importance of creating a Stakeholder map and ensuring that it is an integral part of your daily considerations
Transparency is an essential aspect of stakeholder management and your Product Backlog, Roadmap and Release plan should play an important role.
Have clarity on how to collaborate with each stakeholder. If you treat all of them the same way, you will inevitably face troubles. A simple method to adopt is to consider power, interest, and attitude as three critical points to evaluate for each stakeholder. You can visualise it in this matrix.
Monitor
Monitor
Low power and low interest: this group of people shouldn’t drive your decisions and consume your time. When stakeholders have low interest and low power, you should not involve them in the development process. Yet, you should be careful with how you deal with their eventual demands.
Keep Satisfied
Keep Satisfied
High power and low interest: some people have the decision power but are uninterested in your initiative. However, you should ensure alignment with them; otherwise, you will face resistance and ultimately slow down or progress.
Inform
Inform
Low power and high interest: I consider this group as the most dangerous. People with high interest tend to be quite active and demanding. Still, if they lack decision power, you should be careful with how their input influences your decisions.
Manage Closely
Manage Closely
High power and high interest: this is the group you should work on your daily business. People with high power and high interest will help you deliver value faster. Engage with them as close as you can.
Attitude
Attitude
In addition to power and interest, you can evaluate which attitude each person has. Once you have clarity on this, it will become easier for you to deal with each individual.
Non-functional Requirements
Non-functional Requirements
Business Requirements come in all forms. As such a Product is defined by more than just user stories.
Thus, the Scrum Team members are stakeholders too.
Page updated
Google Sites
Report abuse