Activity 10 | Stakeholder Map |
A stakeholder map is a network diagram of the people involved with or impacted by the software system. Use this method to visualize the relationships, hierarchies, and interactions between all the people who have an interest in the software system to be built.
30--45 minutes
Whole team, known stakeholders
This activity can be conducted alone or with groups of 25 or more people depending how much physical space is available.
A drawing surface such as a large whiteboard or large sheets of paper. Tape paper to a wall or roll out on a large table. Provide markers of different colors so that most participants have a marker. When working with a group, be sure there is enough space and writing surface for all participants to contribute.
If the participants are distributed, consider using a tool such as Mural.[34]
Introduce the activity by sharing the goal of the exercise. You might start by saying, For the next 30 minutes we’re going to explore who our stakeholders are. Once we have a better idea of who has a stake, we’ll come up with a plan for who we’re talking to first.
Share the guidelines and hints for creating a stakeholder map.
Start the activity. Working together, everyone adds and annotates stakeholders collaboratively until time runs out or the map seems complete.
Once the map is complete, ask participants to share observations about the map. Are there interesting connections or unexpected stakeholders? Who are the most important stakeholders?
Take a picture of the map and store it in your team’s wiki.
Use simple icons to represent individual people; use multiple icons to represent groups.
Be specific when naming stakeholders. Think about their roles or in some cases specific names.
Use speech bubbles to represent stakeholders’ needs or thoughts.
Connect people using arrows to show relationships and influence. Label connections to describe relationships.
Encourage participants to look beyond the obvious stakeholders if they stall out during the activity.
Nudge wallflowers, participants who are just watching, to pick up a marker and add to the map.
Here’s an example stakeholder map created by three people in about 15 minutes:
Thijmen de Gooijer. Quality Requirements on a Shoestring. SATURN 2015. http://resources.sei.cmu.edu/library/asset-view.cfm?assetID=436426
http://boxesandarrows.wpengine.com/understanding-the-business/
Liam O’Brien, Len Bass, and Paulo Merson. Quality Attributes and Service-Oriented Architectures. http://resources.sei.cmu.edu/library/asset-view.cfm?assetid=7405
3.141.201.106