← PMP Exam: Stakeholder Engagement

PMP Project Management Professional Exam Study Guide

Key concepts, definitions, and exam tips organized by topic.

25 cards covered

PMP Exam Study Guide: Stakeholder Engagement


Overview

Stakeholder Engagement is a critical knowledge area in the PMBOK framework that covers identifying, analyzing, planning for, managing, and monitoring all individuals and groups impacted by or able to influence a project. Effective stakeholder engagement directly influences project success by building support, managing resistance, and ensuring needs and expectations are addressed throughout the project lifecycle. The PMP exam heavily tests your ability to select the right strategy, tool, or action for a given stakeholder scenario.


---


1. Stakeholder Identification


Summary

Stakeholder identification must begin as early as possible — ideally during the Initiating Process Group — because early identification maximizes stakeholder influence on project direction and minimizes costly changes later. The primary output of this process is the Stakeholder Register.


Key Concepts


  • • Stakeholder Register contains three types of information:

    • - Identification information (name, role, contact)

    - Assessment information (requirements, expectations, potential influence)

    - Stakeholder classification (internal/external, supporter/resistor)

  • • Stakeholder identification is iterative — new stakeholders may be discovered throughout the project
  • • Snowball sampling uses existing stakeholders to identify others who may be impacted or influential

    • Stakeholder Analysis Models


    | Model | Dimensions Used | Purpose |

    |---|---|---|

    | Power/Interest Grid | Power vs. Interest | Determine engagement strategies |

    | Power/Influence Grid | Power vs. Influence | Assess ability to effect change |

    | Salience Model | Power, Urgency, Legitimacy | Prioritize stakeholder attention |


    The Salience Model — Three Attributes

  • • Power — Level of authority
  • • Urgency — Need for immediate attention
  • • Legitimacy — Appropriateness of their involvement

    • Key Terms

  • • Stakeholder — Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a project
  • • Snowball Sampling — A technique where known stakeholders recommend other potential stakeholders
  • • Salience Model — A classification model using power, urgency, and legitimacy

    • Watch Out For ⚠️

    > The exam may ask when to identify stakeholders. The answer is always as early as possible — during Initiating, not Planning or Executing. Waiting to identify stakeholders is a common mistake that leads to project problems.


    > Stakeholder identification is never a one-time event — it continues throughout the project lifecycle.


    ---


    2. Stakeholder Analysis & Classification


    Summary

    After identifying stakeholders, the project manager must analyze and classify them to develop targeted engagement strategies. The Power/Interest Grid and the Stakeholder Engagement Assessment Matrix are the two most commonly tested analysis tools on the PMP exam.


    Power/Interest Grid — Four Strategies


    | Quadrant | Power | Interest | Strategy |

    |---|---|---|---|

    | Manage Closely | High | High | Most critical; maximum engagement |

    | Keep Satisfied | High | Low | Must be kept content; avoid overwhelming |

    | Keep Informed | Low | High | Regular updates; involvement in decisions that affect them |

    | Monitor | Low | Low | Minimal effort; watch for changes |


    > 📌 Exam Tip: "Keep Satisfied" (High Power/Low Interest) is frequently tested. These stakeholders can kill your project if they become dissatisfied, even though they aren't highly engaged day-to-day.


    Stakeholder Engagement Assessment Matrix


    Tracks current vs. desired engagement levels across five categories:


    | Level | Description |

    |---|---|

    | Unaware | Not aware of the project or its potential impact |

    | Resistant | Aware of the project; actively works against it |

    | Neutral | Aware but neither supportive nor resistant |

    | Supportive | Aware and in favor of the project |

    | Leading | Aware, supportive, AND actively engaged in driving success |


  • • C = Current engagement level
  • • D = Desired engagement level
  • • A gap between C and D requires updates to the Stakeholder Engagement Plan

    • Leading vs. Supportive — The Critical Distinction

    | Supportive | Leading |

    |---|---|

    | Aware of the project | Aware of the project |

    | In favor of the project | In favor of the project |

    | Does not take active steps | Actively engaged in helping it succeed |


    Key Terms

  • • Power/Interest Grid — Tool grouping stakeholders by authority and concern level
  • • Stakeholder Engagement Assessment Matrix — Tool comparing current vs. desired engagement
  • • Resistant Stakeholder — Aware of the project and actively working to ensure its failure
  • • Leading Stakeholder — Fully engaged, supportive, and actively championing the project

    • Watch Out For ⚠️

    > Resistant ≠ Unaware. A resistant stakeholder knows about the project and consciously opposes it. Unaware stakeholders simply haven't been informed yet — these require different response strategies.


    > When a gap exists between current and desired engagement, the document to update is the Stakeholder Engagement Plan, not the Communications Management Plan.


    ---


    3. Stakeholder Engagement Planning


    Summary

    The Plan Stakeholder Engagement process (a Planning process) produces the Stakeholder Engagement Plan, which defines strategies to increase stakeholder support and reduce resistance. The Stakeholder Register is the most critical input to this process.


    Stakeholder Engagement Plan vs. Communications Management Plan


    | Stakeholder Engagement Plan | Communications Management Plan |

    |---|---|

    | Strategies to increase support and reduce resistance | What, who, how, and when information is communicated |

    | Focuses on relationships and engagement | Focuses on information flow and delivery |

    | Defines how to move stakeholders to desired engagement levels | Defines communication channels, frequency, and format |


    > 📌 These two documents are closely related but distinct — a common exam trap is confusing their purposes.


    Key Inputs to Plan Stakeholder Engagement

  • • Stakeholder Register (most critical) — provides identification, assessment, and classification data
  • • Project Charter
  • • Resource Management Plan
  • • Risk Register
  • • Organizational process assets and enterprise environmental factors

    • Agile vs. Predictive Stakeholder Engagement


    | Predictive | Agile |

    |---|---|

    | Engagement planned at defined milestones | Engagement is continuous and collaborative |

    | Formal consultation points | Frequent feedback loops (e.g., Sprint Reviews) |

    | Plan-driven communication schedule | Adaptive, real-time stakeholder involvement |


    Key Facilitation Technique

  • • Facilitated Workshops — Bring together stakeholders with diverse perspectives to collaboratively discuss and align on project needs, expectations, and engagement strategies

    • Key Terms

  • • Stakeholder Engagement Plan — Document defining strategies to move stakeholders toward desired engagement levels
  • • Plan Stakeholder Engagement — The Planning process that produces the Stakeholder Engagement Plan
  • • Facilitated Workshops — Collaborative sessions used to align diverse stakeholder perspectives

    • Watch Out For ⚠️

    > The Stakeholder Engagement Plan is a component of the Project Management Plan, meaning changes to it go through Integrated Change Control.


    > In Agile projects, the absence of a formal Stakeholder Engagement Plan doesn't mean engagement is ignored — it means engagement is built into the framework through ceremonies like Sprint Reviews.


    ---


    4. Managing & Monitoring Stakeholder Engagement


    Summary

    Manage Stakeholder Engagement (Executing) focuses on actively working with stakeholders to meet their needs, address issues, and resolve conflicts. Monitor Stakeholder Engagement (Monitoring & Controlling) tracks whether engagement strategies are working and adjusts them as needed.


    Manage Stakeholder Engagement — Key Facts

  • • Primary Goal: Communicate and work with stakeholders to meet needs/expectations, address issues, and foster appropriate involvement
  • • Key Output: Change Requests (along with updates to the PM plan, project documents, and OPAs)
  • • Critical Tool: The Issue Log — tracks identified issues, owners, target resolution dates, and status

    • Monitor Stakeholder Engagement — Key Facts

  • • Purpose: Monitor stakeholder relationships and adjust strategies as needed
  • • Trigger: When actual engagement levels diverge from desired levels
  • • Output: Work performance information, change requests, updates to plan and documents

    • Managing Resistant Stakeholders — Step-by-Step


    When a previously supportive stakeholder becomes resistant:

    1. Identify root cause first — Meet with the stakeholder to understand their concerns

    2. Update the Stakeholder Engagement Plan with revised strategies

    3. Implement new engagement actions

    4. Monitor for improvement


    > 📌 The exam will almost always reward responses that investigate before acting. Never jump straight to escalation or re-planning without first understanding why resistance occurred.


    Critical Interpersonal Skills for Stakeholder Management

  • • Active Listening — Most important skill for managing resistant stakeholders; builds trust and uncovers root causes
  • • Conflict Management — Resolving disagreements constructively
  • • Negotiation — Finding mutually acceptable solutions
  • • Facilitation — Guiding productive discussions

    • Agile Stakeholder Feedback Mechanism

  • • Sprint Review (Iteration Review) — The primary formal mechanism for stakeholder feedback in Agile; the team demonstrates completed increments and stakeholders provide input to shape the product backlog

    • Key Terms

  • • Issue Log — Document tracking stakeholder issues, owners, target dates, and resolution status
  • • Manage Stakeholder Engagement — Executing process; actively working with stakeholders
  • • Monitor Stakeholder Engagement — M&C process; tracking and adjusting engagement effectiveness
  • • Active Listening — Interpersonal skill prioritized when managing resistant stakeholders
  • • Sprint Review — Agile ceremony for formal stakeholder feedback on product increments

    • Watch Out For ⚠️

    > The Issue Log is for tracking stakeholder issues, not risks. Don't confuse it with the Risk Register.


    > Change Requests are a key output of Manage Stakeholder Engagement. When strategies must change significantly, they go through formal change control.


    > In Agile, the Product Owner often serves as the primary interface between the development team and stakeholders — this role is frequently tested in hybrid and Agile scenarios.


    ---


    5. Stakeholder Communication Strategies


    Summary

    Effective stakeholder engagement depends on selecting the right communication method, channel, and approach for each situation. The PMP exam tests your ability to match communication strategies to stakeholder needs, project context, and the sensitivity of information.


    Communication Channels Formula


    $$\frac{N(N-1)}{2}$$


    Where N = number of project stakeholders


    | Stakeholders | Channels |

    |---|---|

    | 5 | 10 |

    | 10 | 45 |

    | 20 | 190 |


    > 📌 This formula demonstrates how complexity grows exponentially as stakeholders are added — a key argument for keeping the team lean.


    Three Communication Methods


    | Method | Description | Best Used For |

    |---|---|---|

    | Interactive | Real-time, two-way (meetings, calls, video) | Sensitive issues, complex topics, immediate clarification needed |

    | Push | Sent directly to recipients (email, memos, reports) | General updates; no confirmation of comprehension |

    | Pull | Recipients access information themselves (intranet, portal) | Large audiences, optional information, reference materials |


    Choosing the Right Communication Method

  • • Sensitive or complex issues → Interactive (face-to-face or video)
  • • Status updates to a defined list → Push (email, reports)
  • • Large audience with variable needs → Pull (knowledge base, portal)

    • Communication Considerations in Stakeholder Engagement

  • • Communication frequency should match stakeholder engagement level and information needs
  • • Communication format should be tailored to stakeholder preferences and technical literacy
  • • Feedback mechanisms must be built in to confirm understanding, especially for complex information

    • Key Terms

  • • Interactive Communication — Real-time two-way exchange; highest fidelity for sensitive topics
  • • Push Communication — Information sent to recipients; no receipt confirmation
  • • Pull Communication — Recipients retrieve information on demand
  • • Communication Channels Formula — N(N-1)/2; measures complexity of communication network

    • Watch Out For ⚠️

    > Push communication does NOT confirm comprehension. If understanding is critical (e.g., a major scope change), use interactive communication instead.


    > The communication channels formula uses the total number of stakeholders, not just team members. Be careful about what "N" includes in the scenario.


    ---


    Quick Review Checklist ✅


    Use this checklist to confirm mastery before exam day:


  • • [ ] Stakeholder identification begins in the Initiating Process Group — as early as possible
  • • [ ] The Stakeholder Register is the primary output of Identify Stakeholders
  • • [ ] The Salience Model uses Power, Urgency, and Legitimacy
  • • [ ] Power/Interest Grid strategies: Manage Closely → Keep Satisfied → Keep Informed → Monitor
  • • [ ] High Power / Low Interest = Keep Satisfied (most commonly tested quadrant)
  • • [ ] The Stakeholder Engagement Assessment Matrix compares Current (C) vs. Desired (D) engagement
  • • [ ] Five engagement levels: Unaware → Resistant → Neutral → Supportive → Leading
  • • [ ] Leading = supportive AND actively engaged; Supportive = aware and in favor but passive
  • • [ ] Gap between C and D → Update the Stakeholder Engagement Plan
  • • [ ] Stakeholder Engagement Plan = strategies for support/resistance; Communications Plan = what/who/how/when
  • • [ ] The Issue Log tracks stakeholder issues during execution
  • • [ ] Change Requests are a key output of Manage Stakeholder Engagement
  • • [ ] When a stakeholder becomes resistant → identify root cause FIRST, then update the plan
  • • [ ] Active listening is the most important skill for managing resistant stakeholders
  • • [ ] Sprint Review = primary formal mechanism for stakeholder feedback in Agile
  • • [ ] Communication channels = N(N-1)/2
  • • [ ] Interactive > Push > Pull in order of immediacy and suitability for sensitive topics
  • • [ ] Push communication does not confirm comprehension
  • • [ ] Agile stakeholder engagement is continuous and collaborative, not milestone-based
  • • [ ] The Stakeholder Engagement Plan is part of the PM Plan → changes require Integrated Change Control

    • ---


    Focus your final review on scenario-based questions that test your ability to choose the correct next action, select the right document to update, or identify the most appropriate communication method. These "what should the PM do FIRST?" questions are the hallmark of PMP stakeholder engagement testing.

    📝

    Take a Practice Test

    Test yourself with multiple choice questions
    📇

    Study with Flashcards

    Flip through all 25 cards

    Want more study tools?

    Subscribe for $7.99/mo and turn your own notes into personalized flashcards and study guides.

    View Pricing