Project Stakeholders: Identification and Engagement Strategy
PMBOK v8 Definition
Stakeholder refers to an individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project. The Stakeholder Register is a project document that contains information about project stakeholders, including an assessment and classification of project stakeholders. This document includes identification information such as name, organizational position, location, contact details, and role on the project. The Stakeholder Engagement Plan provides specific strategies or approaches for engaging with individuals or groups of stakeholders; it can be formal or informal and highly detailed or broadly framed, based on the needs of the project and the expectations of stakeholders.
Why It Matters for the Exam
Stakeholder concepts appear in approximately 15-20% of PMI exam questions, frequently in situational scenarios testing your ability to identify the correct process, output, or tool. Questions often require distinguishing between the Stakeholder Register (identifying and documenting) and the Stakeholder Engagement Plan (strategies for engagement). Expect scenario-based questions where you must determine whether the project team needs to first identify stakeholders or plan engagement strategies.
Key Points to Remember (for the exam)
- Main Input for Identify Stakeholders: Project charter, business documents, project management plan, project documents, agreements, enterprise environmental factors, and organizational process assets
- Main Output: Stakeholder Register (containing identification information, assessment, and classification)
- Key Tool: Stakeholder analysis and stakeholder mapping/representation (Data representation techniques)
- Plan Stakeholder Engagement Output: Stakeholder Engagement Plan (strategies based on needs, expectations, interests, requirements, and potential impact)
- Common Confusion: The Stakeholder Register is a project document, not a plan; the Stakeholder Engagement Plan is a component of the Project Management Plan
- Process Frequency: Both Identify Stakeholders and Plan Stakeholder Engagement are performed periodically throughout the project as needed
- Key Benefit of Identify Stakeholders: Enables the project team to identify the appropriate focus for the engagement of each stakeholder or group of stakeholders
Typical PMI Exam Example
You are managing a software development project. During project planning, you identify 15 stakeholders, analyze their interests and influence, and document their names, organizational positions, and roles. Which document are you creating?
Answer: Stakeholder Register (not Stakeholder Engagement Plan, which comes later and contains engagement strategies)
PMI Exam Traps
-
Trap: Confusing Stakeholder Register with Stakeholder Engagement Plan Reality: Register = who stakeholders are (identification + classification); Plan = how to engage them (strategies)
-
Trap: Thinking Identify Stakeholders is performed only once at project start Reality: This process is performed periodically throughout the project as needed; continuous stakeholder identification works as a risk management strategy
-
Trap: Assuming the Stakeholder Engagement Plan must be highly detailed and formal Reality: The plan can be formal or informal and highly detailed or broadly framed, based on project needs and stakeholder expectations
-
Trap: Confusing "interested parties" with "stakeholders" in exam scenarios Reality: Stakeholders are specifically individuals, groups, or organizations that have a stake in the project; they may affect, be affected by, or perceive themselves to be affected by the project
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Communications Management Plan | Output of Plan Stakeholder Engagement | Both plans are updated during Identify Stakeholders; Communications Management Plan is a separate but related output |
| Risk Management Plan | Output of Identify Stakeholders | Continuous stakeholder identification works as a risk management strategy |
| Risk Register | Project document update | Stakeholder analysis feeds into risk identification; issue log and assumption log are also updated |
| Requirements Management Plan | Project management plan update | Stakeholder needs and expectations directly influence requirements management |
Quick Review Questions
-
What is the key benefit of the Identify Stakeholders process according to PMBOK v8?
-
A project manager is developing strategies to engage stakeholders based on their needs, expectations, interests, requirements, and potential impact. Which process is being performed?
-
The Stakeholder Register contains identification information, an assessment, and what other element?
-
True or False: The Stakeholder Engagement Plan must be a formal, highly detailed document.
-
During which project phase should the Identify Stakeholders process be performed?
PMBOK v8 Reference
Section 2.5.2 - Stakeholders Performance Domain
- Section 2.5.2.1 - Identify Stakeholders
- Section 2.5.2.2 - Plan Stakeholder Engagement
Figure 2-33: Identify Stakeholders Inputs, Tools and Techniques, and Outputs