Stakeholder Register

Stakeholder Register

Below are the description of all the uses of the working document “Stakeholder Register”:

Stakeholder Register” is an input for the processCollect Requirements”.
The stakeholder register is used to identify stakeholders who can provide information on the requirements. The stakeholder register also captures major requirements and main expectations stakeholders may have for the project.

Stakeholder Register” is an input for the processPlan quality management”.
The stakeholder register aids in identifying those stakeholders possessing a particular interest in, or having an impact on, quality.

Stakeholder Register” is an input for the processPlan communications management”.
The stakeholder register provides the information needed to plan the communication with project stakeholders.

Stakeholder Register” is an input for the processPlan Risk management”.
The stakeholder register, which contains all details related to the project?s stakeholders, provides an overview of their roles.

Stakeholder Register” is an input for the processIdentify risks”.
Information about the stakeholders is useful for soliciting inputs to identify risks, as this will ensure that key stakeholders, especially the stakeholder, sponsor, and customer are interviewed or otherwise participate during the Identify Risks process.
Project documents provide the project team with information about decisions that help better identify project
risks. Project documents improve cross-team and stakeholder communications and include, but are not limited to:
Project charter,
Project schedule,
Schedule network diagrams,
Issue log,
Quality checklist, and – Other information proven to be valuable in identifying risks.
. If the project requires external procurement of resources, procurement documents become a key input to the Identify Risks process. The complexity and the level of detail of the procurement documents should be consistent with the value of, and risks associated with, planned procurement.
Enterprise environmental factors that can influence the Identify Risks process
include, but are not limited to:
– Published information, including commercial databases,
– Academic studies,
– Published checklists,
Benchmarking,
– Industry studies, and – Risk attitudes.
Organizational process assets that can influence the Identify Risks process include,
but are not limited to:
– Project files, including actual data,
– Organizational and project process controls,
Risk statement formats or templates, and – Lessons learned.

Stakeholder Register” is an input for the processPlan Procurement management”.
The stakeholder register provides details on the project participants and their interests in the project.

Stakeholder Register” is an output for the processIdentify Stakeholders”.
The main output of the Identify Stakeholders process is the stakeholder register. This contains all details related
to the identified stakeholders including, but not limited to: – Identification information. Name, organizational position, location, role in the project, contact
information;
– Assessment information. Major requirements, main expectations, potential influence in the project,
phase in the life cycle with the most interest; and – Stakeholder classification. Internal/external, supporter/neutral/resistor, etc.
The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change?or new ones identified?throughout the life cycle of the project.

Stakeholder Register” is an input for the processPlan Stakeholder Management”.
The stakeholder register provides the information needed to plan appropriate ways to engage project stakeholders.

This definition was found in the PMBOK V5

Go back to the Glossary or to the Mapping

Leave a Reply

Your email address will not be published. Required fields are marked *

18 − 10 =