Purpose
The purpose of the stakeholder register is to document who is impacted by the project, documenting relevant information regarding their interests, involvement, and impact on project success. It is critical to the success of the project to start early in identifying all the people, groups, or organizations that are touched (positively or negatively) or have some influence on the project.
Once identified, stakeholder analysis is performed to identify stakeholders’ levels of interest, expectations and needs of the project. This information is then used to determine communication needs, expectation alignment and gaining overall support for the project.
Template
Stakeholder Register
Stakeholder List in Team Dynamix
Guidelines
What is a Stakeholder?
A stakeholder is an individual, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity or outcome of a project. The effect or impact could be positive or negative. Effective engagement and involvement of stakeholders is critical for project’s success. This includes internal and external stakeholders, such as business executives, leadership team, SMEs, team members, departments, end users, vendors, customers, partners, and regulators
Types of Stakeholder
Some examples of stakeholder include
• Project manager
• Project team members
• Project sponsor
• Customer
• End users
• Vendors/suppliers
• Business partners - External organizations that have a special relationship with the enterprise, provide specialized expertise or fill a specified role such as installation, training or support
• Organizational Groups
• Organizational groups
• Functional managers
• Other Stakeholders
o Environmentalists, social pressure groups
o Government and political leadership
Stakeholder Register
Input into the stakeholder register may come from many different sources including, but not limited to, Sponsor, senior leadership, project request form and/or business case, business requirements, subject matter experts within business unit(s), and interaction with other stakeholders. The register is normally completed by the Project Manager.
The Stakeholder register is one of the key deliverable from the define stage, it is a living document and should be continuously reviewed throughout the project for any changes in stakeholder influence or impact, especially if there are changes in scope or requirements.
For small and less complex project following project lite methodology the stakeholder register within Team Dynamix should be used to identify all project stakeholders
For large and more complex projects following the Standard Project methodology the stakeholder register should be used.
Note: The information in this register also contains fields to record the results of stakeholder analysis which can produce information that can be very sensitive and is meant for limited circulation only. Exercise caution in who this document is sent to and how it is published.
Stakeholder Analysis
Stakeholder analysis involves gathering and analysing information to determine whose interests should be taken into account through out the project. It identifies interests, expectations, and influence of the stakeholders and relates them to the purpose of the project
Stakeholder Power Map
The influence/impact grip groups stakeholders based on their active involvement (influence) in the project and their ability to effect changes to the project planning or execution (Impact). A Stakeholder’s position on the grid shows the type of player (category) the stakeholder is for the project and identifies how that stakeholder should be managed
Stakeholder Engagement Map
The stakeholder engagement map is a tool used by the project manager to identify the level of engagement required at each stage of the project from each stakeholder. This information can then be used by the Project Manager in determining how to manage various stakeholders. For example, at the beginning of the project it may be necessary for the senior stakeholders to be highly engaged in order to clear away any obstacles. Once these have been removed, it may be sufficient to change their level of engagement from leading to supportive, and other stakeholders, such as end users, may become more important.
The current engagement level of all stakeholders is compared with the planned engagement level required for successful project completion. The engagement level of the stakeholders is classified as follows:
Unaware – Unaware of project or potential impacts
Resistant – Aware of project and potential impacts and resistant to change
Neutral – Aware of project, yet neither supportive nor resistant
Supportive – Aware of project and potential impacts and supportive to change
Leading – Aware of project and potential impacts and actively engaged in ensuring the project is a success
The engagement levels are documented using a stakeholder engagement assessment matrix, shown below.
The current engagement level of all stakeholders is identifies with a 'C' and the planned/or desired engagement level is identified with a 'D'.
