Engaging Stakeholders and Managing Expectations

PMP PMP · People

By Abu Anns · Last updated 20 November 2026Exam version: July 2026 ECO (current since 9 July 2026)

Why stakeholders decide whether a project succeeds

A stakeholder is anyone who can affect, or is affected by, the project — the sponsor, the customer, the team, functional managers, regulators, end users, and sometimes the wider public. The July 2026 ECO gives stakeholder work three tasks in the People domain: engage stakeholders, align stakeholder expectations, and manage stakeholder expectations. That is three of the eight People tasks, which tells you how heavily the exam weights this topic. Projects rarely fail because the schedule was wrong; they fail because the people who matter were not engaged, not heard, or surprised at the wrong moment.

The first step with stakeholders is always identification, and it happens early — during initiation, before the project management plan is written. The project manager identifies stakeholders, analyzes their interest, influence, and expectations, and records the results in a stakeholder register. A common exam point is that stakeholder identification is not a one-time activity: new stakeholders emerge throughout the project (a reorganization creates a new sponsor, a regulation creates a new compliance stakeholder), and the register must be updated when they do. A question that describes a surprise stakeholder appearing late in the project is usually testing whether you would update the register and the engagement approach — not whether you would ignore them or complain about the late arrival.

Stakeholder analysis: power, interest, and engagement levels

Stakeholder analysis turns a list of names into a strategy. The most tested model is the power/interest grid, which sorts stakeholders by their power to influence the project and their level of interest in it. High-power, high-interest stakeholders (the sponsor, the key customer) must be managed closely: frequent, direct engagement. High-power, low-interest stakeholders (a senior executive who is only loosely involved) must be kept satisfied: enough engagement to keep them supportive, not so much that you waste their time. Low-power, high-interest stakeholders (end users, the project team) must be kept informed: regular communication so they feel heard. Low-power, low-interest stakeholders need only monitoring: light-touch updates, with attention if their position changes.

PMI also expects you to assess each stakeholder's current engagement level against the desired level. The five levels are: unaware (does not know about the project), resistant (knows about it and opposes it), neutral (neither supports nor opposes), supportive (backs the project), and leading (actively champions it). The stakeholder engagement assessment matrix records the current level (C) and the desired level (D) for each stakeholder, and the gap between them is the engagement work to be done. A question might describe a resistant stakeholder and ask what to do: the answer is to understand why they are resistant — what they fear losing — and to engage them with information and involvement, not to work around them or escalate over their head.

Engaging stakeholders and aligning expectations

Engagement means involving stakeholders in the project in ways that fit their needs: the sponsor in decisions about scope and budget, users in defining requirements and testing deliverables, the team in planning the work. The stakeholder engagement plan records how each stakeholder (or group) will be engaged — how often, through which channels, and with what information. It is a living document, updated as stakeholders and their needs change. The exam tests this through scenarios: a stakeholder who complains they were not consulted, a sponsor who feels out of the loop, a user group that rejects a deliverable they never saw during development. In every case, the root cause is an engagement failure, and the fix is to involve the stakeholder properly — not to defend the project or to blame the stakeholder for not paying attention.

Aligning expectations is the harder half of the work. Stakeholders often hold different, unstated expectations about what the project will deliver, when, and at what cost. The project manager's job is to surface those expectations early, compare them against what the project can actually deliver, and negotiate a shared understanding — documented in the project charter, the scope statement, and the stakeholder engagement plan. A classic exam scenario: a stakeholder believes the project includes a feature that was never in scope. The correct response is to review the scope documents with them, explain what is and is not included, and use the change control process if they want the feature added. The wrong responses are to add the feature quietly (scope creep) or to dismiss the stakeholder's expectation without discussion.

Managing difficult stakeholders

Every project has at least one difficult stakeholder: the sponsor who changes their mind, the functional manager who will not release resources, the user group that resists the change, the executive who wants the project to fail for political reasons. PMI's approach is consistent: understand their interests, engage them directly, and look for common ground. A resistant stakeholder is usually protecting something — their budget, their team, their reputation, their way of working. The project manager who finds out what that is can usually find a way to address it. Escalation is not the first move, and working around a stakeholder almost always backfires, because they will use their influence at the worst possible moment.

One specific exam pattern is the stakeholder who bypasses the project manager and goes directly to team members with requests. The correct response is to speak with the stakeholder, explain the agreed communication and change processes, and redirect their requests through the proper channel — while also reminding the team to route such requests to the project manager. The wrong response is to let it continue (which creates uncontrolled scope change) or to forbid the team from talking to stakeholders (which damages relationships and transparency).

Stakeholders in agile and hybrid projects

In agile and hybrid projects, stakeholder engagement is continuous rather than periodic. Sprint reviews (demos) are the main engagement event: stakeholders see working product every few weeks, give feedback, and help set the next priorities. This frequent feedback loop is what prevents the classic predictive failure of delivering exactly what was specified and finding that nobody wants it. The product owner is the key stakeholder-facing role in Scrum, responsible for ordering the backlog and representing stakeholder needs to the team. The exam expects you to know that the product owner — not the project manager, and not individual stakeholders — is the single voice of priority for the team.

Customer collaboration is also a value the exam tests directly. The Agile Manifesto values customer collaboration over contract negotiation, and exam questions reward behaviors that bring customers into the work — inviting them to reviews, showing them working increments early, and adapting the plan based on their feedback. An option that hides the work from the customer until it is finished, or that treats the contract as a reason not to listen, is almost always wrong.

Exam mindset for stakeholders

For stakeholder questions, the decision tree mirrors the rest of the People domain. First, identify and analyze: who is this stakeholder, what do they want, what is their current engagement level? Then engage: involve them in the way that fits their needs, communicate proactively, and align expectations early and honestly. When expectations conflict with reality, use the documented scope and the change control process — never silent scope creep, never dismissal. And when a stakeholder is resistant, understand why before deciding what to do. The project manager who knows their stakeholders and keeps them engaged rarely gets surprised; the exam rewards that project manager.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.During project execution, a department head who was not identified as a stakeholder objects to a deliverable and threatens to block its rollout. What should the project manager do FIRST?

Report an error

Q2.A project manager is analyzing stakeholders using the power/interest grid. The finance director has high power over the project but low interest in its day-to-day progress. How should the project manager engage the finance director?

Report an error

Q3.A key stakeholder tells the project manager they expected the new system to include automated reporting, but automated reporting was never in the project scope. What should the project manager do?

Report an error

Q4.A sponsor has been bypassing the project manager and giving work requests directly to team members. Team members are confused about priorities and some planned work is slipping. What should the project manager do?

Report an error

Q5.Using the stakeholder engagement assessment matrix, a project manager finds that the operations manager is currently RESISTANT to the project but needs to be SUPPORTIVE for the rollout to succeed. What is the BEST action?

Report an error

Q6.An agile project team has completed three sprints but has not invited the customer to any sprint review. The customer now says the product does not match what they expected. What should the project manager do?

Report an error

Q7.A project manager is preparing the stakeholder engagement plan. Which information is MOST important to include for each stakeholder?

Report an error

Q8.A project affects two departments with opposite priorities: Sales wants the new system to launch before the holiday season, while Operations wants a longer testing period to protect service quality. What should the project manager do FIRST?

Report an error