Study guide
5.3 Stakeholder Management
CAPM Certified Associate in Project Management Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & CAPM Exam Overview
1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences
2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)
2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas
3 Chapter 3: Project Management Planning (Domain 1, Task 2)
3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management
4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)
4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques
5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)
5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints
6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)
6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations
7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)
7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts
8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)
8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment
9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)
9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps
10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)
10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary
5.3 Stakeholder Management
Key Takeaways Explain This Topic AI
A stakeholder is anyone who may affect, be affected by, or perceive themselves to be affected by the project — supporters and opponents alike.
Identify Stakeholders runs in the Initiating process group (one of only two Initiating processes), and the stakeholder register is built and continuously updated from there on.
The Power/Interest grid yields four strategies: Manage Closely (high/high), Keep Satisfied (high power/low interest), Keep Informed (low power/high interest), and Monitor (low/low).
Engagement levels run Unaware, Resistant, Neutral, Supportive, Leading; the assessment matrix marks Current (C) and Desired (D) to expose the gap to close.
The salience model adds power, legitimacy, and urgency; a stakeholder with all three is a definitive stakeholder and the top priority.
Last updated: June 2026
Who Counts as a Stakeholder
PMI defines a stakeholder broadly: any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of the project. The phrase perceive themselves matters — a community group that merely believes it will be impacted is a stakeholder you must manage, even if the objective impact is small. Stakeholders include both supporters and opponents .
- Internal stakeholders External stakeholders
- Sponsor, PM, team members Customers and end users
- Functional managers Regulators and government
- Senior management, PMO Suppliers and vendors
- Other departments Community, media, competitors
- The Four Stakeholder Processes
- Process Process Group Purpose
- Identify Stakeholders Initiating Find everyone affected; build the stakeholder register
- Plan Stakeholder Engagement Planning Decide how to engage each stakeholder
- Manage Stakeholder Engagement Executing Communicate and work with stakeholders to meet needs
- Monitor Stakeholder Engagement Monitoring & Controlling Track relationships; adjust strategies
Identify Stakeholders is one of only two Initiating processes (the other is Develop Project Charter). The exam frequently tests that stakeholder identification starts as early as possible and is iterative — new stakeholders surface throughout the life cycle.
The Power/Interest Grid (Mendelow)
This classifies stakeholders by power (authority to influence) and interest (level of concern):
- Low Interest High Interest
- High Power Keep Satisfied — meet needs, don't overload with detail Manage Closely — full, active engagement
- Low Power Monitor — minimal effort, watch for change Keep Informed — regular updates
The most-missed cell is high power / low interest = Keep Satisfied . These stakeholders (often a senior executive) can derail the project if annoyed, yet they don't want daily detail — give them concise, high-level updates. Engaging them like a Manage-Closely stakeholder wastes effort and irritates them.
The Salience Model
The salience model ranks stakeholders on three attributes:
Power — ability to impose their will.
Legitimacy — their involvement is appropriate and valid.
Urgency — they need timely attention.
A stakeholder holding all three is a definitive stakeholder and earns the highest priority. One attribute alone (e.g., only urgency) makes a "latent" stakeholder of low priority.
Engagement Levels and the Assessment Matrix
- Level Meaning
- Unaware Doesn't know the project exists
- Resistant Aware and actively opposed
- Neutral Aware but neither helps nor hinders
- Supportive Aware and willing to help when asked
- Leading Aware and actively championing the project
The stakeholder engagement assessment matrix marks each stakeholder's Current (C) and Desired (D) level:
- Stakeholder Unaware Resistant Neutral Supportive Leading
- Sponsor C, D
- IT Director C D
- End Users C D
The gap between C and D drives the engagement plan; the IT Director (Resistant -> Supportive) needs more effort than the Sponsor (already where you want them). Note you do not always need every stakeholder at Leading — for many, Supportive or even Neutral is the desired target.
The Stakeholder Register
The stakeholder register is the master list, started in Initiating and updated continuously. It records:
Identification — name, role, organization, contact.
Assessment — power, interest, expectations, influence, the engagement phase of greatest interest.
Classification — internal/external, supporter/neutral/resistor.
Exam Tip: Sensitive engagement data (e.g., "this director is Resistant") is often kept out of the widely shared register to avoid damaging relationships. Distribution of the register itself is a stakeholder-management judgment call.
Stakeholder Analysis Step by Step
The CAPM expects you to know the sequence of stakeholder work, not just the tools:
Identify every potential stakeholder, internal and external, including those who only perceive an impact.
Analyze their power, interest, influence, expectations, and likely attitude.
Classify them using a model (Power/Interest grid, salience, or a power/influence or influence/impact grid).
Prioritize so engagement effort goes where it changes outcomes most.
Plan, engage, and monitor through the remaining three processes.
Beyond the Power/Interest grid, PMI lists related classification models: the power/influence grid (authority vs. active involvement), the influence/impact grid (involvement vs. ability to change the project), and the directions of influence view (upward, downward, outward, sideward). They all serve the same purpose — focus limited attention where it matters most.
Plan and Manage Stakeholder Engagement
Plan Stakeholder Engagement produces the stakeholder engagement plan , which states the strategy to move each stakeholder from their current to their desired engagement level and how to maintain it. Manage Stakeholder Engagement is the active, executing-phase work: communicating with stakeholders, negotiating expectations, building trust, and addressing concerns and resistance before they become issues. The PM's interpersonal and team skills — conflict management, cultural awareness, negotiation, and political awareness — are the primary tools here.
Monitoring and Common Traps
Monitor Stakeholder Engagement checks whether engagement strategies are working and adjusts them as relationships and the project evolve. A frequent exam scenario: a previously Supportive stakeholder turns Resistant after a scope change. The correct first response is usually to engage them directly to understand the concern (interactive communication), then update the engagement plan — not to escalate immediately or ignore the shift.
Common Trap: Do not confuse the stakeholder register (a project document listing stakeholders and their assessment data) with the stakeholder engagement plan (a component of the project management plan describing engagement strategy). The register says who ; the plan says how . CAPM questions test that you can tell them apart.