Stakeholder Analysis: Identification, Classification, and Engagement Planning
PMBOK v8 Definition
Stakeholder analysis results in a list of stakeholders and relevant information such as their positions in the organization, roles on the project, "stakes," expectations, attitudes (their levels of support for the project), and their interest in information about the project. This analysis is performed during the Identify Stakeholders process, which belongs to the Project Stakeholder Management Knowledge Area and the Initiating Process Group. The output is the Stakeholder Register, a project document that contains identification information, assessment, and classification of all project stakeholders.
Why It Matters for the Exam
Stakeholder analysis appears frequently in PMI exam questions testing your ability to distinguish between stakeholder identification, classification, and engagement assessment. Questions often present scenarios where you must determine which stakeholder information belongs in the stakeholder register versus the stakeholder engagement plan. Expect situational questions asking what to do when stakeholder attitudes change or how to close the gap between current and desired engagement levels.
Key Points to Remember (for the exam)
- Main Inputs to Identify Stakeholders: Business documents, project charter, project management plan, agreements, enterprise environmental factors, and organizational process assets
- Main Output: Stakeholder register (project document containing identification information, assessment, and classification)
- Key Tool: Stakeholder mapping/representation (categorization methods include power/interest grid, influence/impact grid, salience model)
- Key Output for Planning: Stakeholder engagement plan (formal or informal, specific strategies for engaging individuals or groups)
- Critical Concept: Stakeholder engagement assessment matrix tracks current (C) vs. desired (D) engagement levels across categories: Unaware, Resistant, Neutral, Supportive, Leading
- Common Confusion: Stakeholder register contains "what" (who they are, their stakes, attitudes) while stakeholder engagement plan contains "how" (strategies to engage them)
- Essential Information in Register: Name, organizational position, location, contact details, role on project, stakes, expectations, attitudes, interest level
Typical PMI Exam Example
You are managing a project to implement a new financial system. During stakeholder analysis, you discover that the CFO (Stakeholder 1) is currently "Resistant" but needs to be "Supportive" for project success. The project sponsor (Stakeholder 2) is currently "Neutral" and needs to be "Leading." What should you document first? Answer: Update the stakeholder engagement assessment matrix showing current (C) and desired (D) levels, then develop communication strategies to close the gap.
PMI Exam Traps
-
Trap: Confusing stakeholder register with stakeholder engagement plan
- Reality: Register = identification + assessment information; Engagement plan = strategies and approaches for engagement
-
Trap: Thinking stakeholder analysis is done only once at project initiation
- Reality: Stakeholder analysis should be reviewed and updated throughout the project as stakeholders change
-
Trap: Believing all stakeholders need the same level of engagement
- Reality: The desired engagement level varies per stakeholder based on project needs (C vs. D assessment)
-
Trap: Confusing "stakes" with "attitudes" in stakeholder information
- Reality: Stakes = what they have to gain/lose; Attitudes = level of support (Unaware to Leading)
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Communications Management Plan | Input to / Output from Identify Stakeholders | Stakeholder analysis determines communication needs; plan is updated based on stakeholder information |
| Risk Management Plan | Input to Identify Stakeholders | Stakeholder analysis identifies who has knowledge of risks; risk register is updated |
| Issue Log | Project document update | Stakeholder concerns become issues; issues may change stakeholder attitudes |
| Requirements Management Plan | Input to Identify Stakeholders | Stakeholder expectations directly influence requirements gathering and prioritization |
Quick Review Questions
-
What five categories of engagement are tracked in the stakeholder engagement assessment matrix?
-
During stakeholder analysis, you identify that a key stakeholder has specialist knowledge about organizational power structures. Under which stakeholder value category does this fall—knowledge or contribution?
-
A stakeholder is currently "Neutral" but the project team determines they must be "Supportive" for project success. What does the "C" and "D" represent in the stakeholder engagement assessment matrix?
-
Which project document contains identification information including name, organizational position, location, and role on the project?
-
When should stakeholder analysis be performed—only during project initiation or throughout the project lifecycle?
PMBOK v8 Reference
Section 2.5.3.1 - Monitor Stakeholder Engagement (Examples) Section 5.2 - Identify Stakeholders (Process: Project Stakeholder Management, Initiating Process Group) Figure 5-23 - Stakeholder Mapping/Representation Figure 2-38 - Monitor Stakeholder Engagement Inputs, Tools and Techniques, and Outputs