What are the project forms or templete needed for Project Manager :Initiating Forms STAKEHOLDER REGISTER

The Stakeholder Register is used to identify those people and organizations impacted by the project and document relevant information about each stakeholder. Relevant information can include:

• Name
• Position in the organization
• Role in the project
• Contact information
• List of stakeholder’s major requirements
• List of stakeholder’s expectations
• Potential influence on the project
• A classification or categorization of each stakeholder
The Stakeholder Register is a dynamic project document. The stakeholders, their level of influence, requirements,and classification are likely to change throughout the project. Initially you will not have enough information to complete the register. As the project gets underway you will gain additional information and understanding about each stakeholder’s requirements, expectations, and infl uence and the Stakeholder Register will become more robust.

Information in the Stakeholder Register should be tailored to meet the needs of the project. For example,some projects may have internal and external stakeholders while others may only have internal stakeholders. The following sample is just one approach to identifying and documenting stakeholder information.

The Stakeholder Register receives information from:
• Project charter
• Procurement documents

It is related to:
• Stakeholder Analysis Matrix

It provides information to:
• Requirements Documentation
• Quality Management Plan
• Communications Management Plan
• Risk Management Plan
• Risk Register
• Stakeholder Management Plan

Document Element Description :

 
Name Stakeholder’s name. If you don’t have a name you can substitute a position or organization until you have more information.
Position : The position the stakeholder holds in the organization or enterprise, for example, programmer,human resources analyst, or quality assurance specialist.
Role : The function the stakeholder performs on the project team, such as testing lead, scrum master, or scheduler.
Contact information :How to communicate with the stakeholder, such as their phone number, email address, or physical address.
Requirements : High-level needs for the project and/or product.
Expectations : Main expectations of the project and/or product.
Influence: The degree of infl uence the stakeholder has on the project. This can be a narrative description or high, medium, or low infl uence.
Classification : Some projects may categorize stakeholders as friend, foe, or neutral; others may classify them as high, medium, or low impact.