What is a stakeholder register in project management?

What is a stakeholder register in project management?

• A. A risk log.
• B. A procurement contract template.
• C. A document listing stakeholders, their roles, interest, influence, and engagement strategies.
• D. A budget baseline.

Answer: (C)

The main idea here is understanding who is involved in the project and how they should be engaged. A stakeholder register is a formal document that lists all people and groups with a stake in the project, along with key details about them: their roles, their interests, their level of influence or power, and the planned approach for engaging them. It helps project teams know who needs to be consulted, who must be kept informed, and who has decision-making authority, so communications and expectations can be tailored accordingly. The register typically includes contact information, the stakeholder’s potential impact on the project, and the engagement strategies or plan for communicating with them. This tool is not about risks, contracts, or financials. It focuses on people and relationships, not on risk logs, procurement templates, or budget baselines. For example, a software implementation project might list sponsors, end users, IT staff, and vendors, noting how important each is to success, how they prefer to receive updates, and who is responsible for maintaining the relationship.

The main idea here is understanding who is involved in the project and how they should be engaged. A stakeholder register is a formal document that lists all people and groups with a stake in the project, along with key details about them: their roles, their interests, their level of influence or power, and the planned approach for engaging them. It helps project teams know who needs to be consulted, who must be kept informed, and who has decision-making authority, so communications and expectations can be tailored accordingly. The register typically includes contact information, the stakeholder’s potential impact on the project, and the engagement strategies or plan for communicating with them.

This tool is not about risks, contracts, or financials. It focuses on people and relationships, not on risk logs, procurement templates, or budget baselines. For example, a software implementation project might list sponsors, end users, IT staff, and vendors, noting how important each is to success, how they prefer to receive updates, and who is responsible for maintaining the relationship.