Topic

Stakeholder Directory

Response

A Stakeholder Directory is typically a single living document (e.g. spreadsheet) created by an agile team, which they use to record all the Stakeholder attributes and when used in a combination with a Communication Matrix ensure an effective stakeholder relationship is formed through the entire life cycle. In particular, the solicitation of their needs and wants, as well as their participation in the various agile ceremonies, when the agile team provides an update on their progress and receives timely feedback on the quality of their deliverables.
Attributes of a Stakeholder Directory are:

Stakeholder Role (Customer, Consumer, Catalyst, User or Contributor)
Stakeholder Matrix (RACI Model)
Organisation or Department (Team, Internal, External, Supplier or Partner)
Stakeholder Influence (low or high)
Stakeholder Interest (low or high)
Engagement Approach
Stakeholder Power Map Matrix
Stakeholder Communities
Stakeholder Communication Strategy
Stakeholders Feature Ownership

Stakeholder Identification

Stakeholder is any person, organisation, group that has a stake in the success of the project. Therefore, stakeholders can be internal or external to the project or the wider organisation. Ensuring successful identification and long-term engagement of your stakeholders is an important activities during the early phase of a project. And one that requires constant refinement and relationship building through a well developed stakeholder communication strategy.

Identification

Using the sample template Teams are required to capture the details for each and everyone of their Stakeholders (column b): Stakeholder Name. An initial investment is required to capturing the following details for each of the Stakeholders to ensure the Team engages with them correctly and correctly communicates with them.

Stakeholder Role (Customer, Consumer, Catalyst, User or Contributor)
Stakeholder Matrix (RACI Model)
Organisation or Department (Team, Internal, External, Supplier or Partner)
Stakeholder Influence (low or high)
Stakeholder Interest (low or high)
Recommended Approach

Stakeholder Communities

A reasonable amount of Stakeholder analysis is necessary to correctly group the Stakeholders based on their core characteristics to form an appropriate number of Stakeholder Communities (i.e. groups of Stakeholders that have a similar interest, contribution or need).

Stakeholder Communication Strategy

Ideally, Teams will identify approx 5 to 10 Stakeholder Communities (columns B, C & D in the Plan tab).

Stakeholder by Features

As the matrix below indicates, individual Stakeholder involvement must be defined for each major Feature on the Product Backlog.

See Wikipedia to learn more about RACI - Click here

Discover more

Additional information, including working examples and templates are available in the Monetical knowledge base.