A highly influential project sponsor is actively resisting the adoption of a new agile framework, frequently disrupting sprint planning meetings and demanding traditional status reports. The project manager needs to address this resistance without jeopardizing the sponsor's critical support. What is the most effective approach?

Explore their underlying concerns privately, offer tailored reporting options, and co-create a viable compromise.

Agree to revert to traditional status reporting and bypass the sprint planning meetings to maintain sponsor satisfaction.

Delegate the responsibility of managing the sponsor's expectations to the scrum master to maintain team productivity and focus.

Provide the sponsor with a comprehensive formal presentation detailing the long-term benefits of the agile framework.

A high-influence sponsor insists on minimal verification for acceptance criteria. What is the project manager's best next step?

Negotiate traceable criteria while preserving auditability.

Accept sponsor criteria and waive all verification steps.

Add extra reviews without discussing them with the sponsor.

Escalate the request to the steering committee at once.

Sponsor NPS is declining while customer CSAT and on-time delivery remain stable. What is the most appropriate next sequence?

Assign owner and schedule focused touchpoint

Increase sprint velocity targets across all teams

Add two new risk categories to the register

Rebaseline the entire project schedule

A regulatory stakeholder constantly asks detailed questions about your project and attends all open meetings. However, you discover they are actively criticizing project decisions to senior leadership. How should you adapt your engagement strategy for this stakeholder?

Assess their willingness to support and tailor communications to build full alignment.

Confront the stakeholder publicly during the next meeting to demand project support.

Leverage their high interest by immediately assigning them an advisory project role.

Assume they are fully supportive based solely on their consistent meeting attendance.

Stakeholders state success metrics for a new portal. Which three measurable KPIs best translate those outcomes into acceptance thresholds?

User adoption rate above 80 percent, task time under 2 minutes, NPS above 70

Total revenue generated, server uptime percentage, and number of new features released

System uptime, defect density, and milestone completion percentage

Number of help desk tickets closed, code commit frequency, and sprint velocity average

An executive dashboard must display stakeholder satisfaction. Which fields and structure are required?

Trend lines, thresholds, owner, and next step per row

Full metric tables with all historical values

Metric names and current values only

Raw survey responses without summarization

A newly classified manage-closely stakeholder has missed the last three alignment meetings. What is the most appropriate immediate outreach?

Schedule recurring one-on-one alignment meetings with tailored decision briefs

Assign a team member to collect concerns on the stakeholder's behalf

Reduce meeting frequency to respect the stakeholder's limited availability

Send the standard project newsletter with an added personal note

A regulated-stakeholder workshop must decide contentious items. Which agenda and closing steps minimize late objections?

Distribute pre-work and decision rules, then obtain formal sign-off on outcomes

Hold open discussion without pre-work or decision rules

Close with verbal agreements and no minutes circulation

Record decisions informally and review at next status meeting

Within a three-month increment, which monitoring regimen best detects expectation divergence early?

Bi-weekly demos plus targeted user surveys with defined escalation thresholds

Monthly status reports reviewed only by the steering committee

End-of-increment survey sent after all deliverables are complete

Daily team velocity tracking without stakeholder involvement

Following a major scope change mandated by regulatory updates, several key stakeholders express frustration, claiming they were blindsided. Engagement levels drop, and trust in the project manager diminishes. What is the most appropriate action for the project manager to take to rebuild stakeholder credibility?

Realign expectations and capture new agreements in updated project artifacts.

Forward the regulatory mandate documentation to all stakeholders to prove the change was unavoidable.

Schedule individual meetings with each stakeholder to privately apologize for the communication failure.

Submit a formal change request to the change control board to reverse the mandated regulatory updates.

2.1.2

Domain 1 of 3 · People · task

Stakeholder engagement and expectations for the PMP® exam

Ask who the stakeholder is before you ask what they want, and read every engagement question on the PMP in that order. The topic holds three People tasks: engage stakeholders, align their expectations, and manage those expectations through delivery.

Exam: PMP
Domain: People
Domain weight: 33%
Packages: 20
Updated: Oct 13, 2026

The register is a snapshot. People change faster than the paperwork.

01Three tasks, three different verbs

The People domain is 33% of the exam (PMP Examination Content Outline, as of October 2026). Split evenly over the domain's tasks, these three are about 12.4%, by our estimate. The team side of the same skills is in leading the team.

Engage starts with identifying and analyzing: who is affected, who can affect the work, what they want, and how they feel about the project today. The stakeholder engagement assessment matrix records the gap between each person's current engagement and the level the project needs.

Align is where categorizing happens, and then the harder part: getting groups who want different things to agree on what the project will deliver. That usually means turning a wish into a test someone can pass. “Easy to use” becomes “a new hire submits a timesheet unaided on day one.”

Manage runs through delivery, because expectations drift as the work takes shape. Satisfaction is checked at points you planned, and the register changes when the answer does.

02A stakeholder problem, worked in order

Find them in the register
Is this person identified, and is the entry current? A new name or a changed role is a signal to redo the analysis before doing anything else.
Understand the interest
Ask what they need and why. A demand for a weekly report can be worry about a single deliverable in disguise.
Check it against the plan
Compare the request with scope, priorities and the engagement approach already agreed. Anything that would change a baseline goes to change control.
Tailor the response
Adjust channel, depth and frequency to the person. Clashes between competing demands are handled with the conflict resolution techniques.
Record it and follow up
Update the register, then check later that the change actually worked.

03Look-alike tools in this topic

Stakeholder register: Who is involved and what you know about them: role, interest, influence, expectations. Living, not filed.
Stakeholder engagement plan: How you intend to move each group toward the engagement the project needs. Part of the project management plan.
Power/interest grid: A two-by-two sorting people by how much they can affect the work and how much they care. Good for deciding attention; silent on what to do next.
Salience model: Sorts by power, legitimacy and urgency. Useful when a stem stresses who has a rightful claim on the project.
Engagement assessment matrix: Current and desired engagement per person (unaware, resistant, neutral, supportive, leading), marked C and D. The gaps are your work list.

04Who holds the power here?

Sponsors, regulators and end users take turns in these stems, in predictive and agile settings alike.

Work packages 20

WP 01A highly influential project sponsor is actively resisting the adoption of a new agile framework, frequently disrupting sprint planning meetings and demanding traditional status reports. The project manager needs to address this resistance without jeopardizing the sponsor's critical support. What is the most effective approach?
Debrief answer to open the notes
1. ADropping the agreed agile events to please one person trades the delivery approach for short-term comfort and leaves the real concern unaddressed.
2. BSponsor relationships stay with the project manager; handing them to the scrum master moves the problem without resolving it.
3. CA formal benefits pitch talks at the sponsor before anyone understands why they resist, so it rarely changes a strongly held view.
4. DCorrect: resistance is handled by first understanding the underlying concern, then tailoring how information reaches the sponsor so the framework and their support both survive.
More notes below ↓
WP 02A high-influence sponsor insists on minimal verification for acceptance criteria. What is the project manager's best next step?
Debrief answer to open the notes
1. ACorrect: the project manager negotiates criteria that stay lean for the sponsor yet remain traceable and verifiable, so acceptance can still be defended in an audit.
2. BWaiving verification removes the evidence that the deliverable meets requirements, which exposes the project at acceptance and in any later review.
3. CAdding reviews behind the sponsor's back damages trust and still leaves the disagreement about criteria unresolved.
4. DThis is a negotiation the project manager can lead directly; the steering committee becomes relevant only if the sponsor and project cannot agree.
More notes below ↓
WP 03Sponsor NPS is declining while customer CSAT and on-time delivery remain stable. What is the most appropriate next sequence?
Debrief answer to open the notes
1. AVelocity targets measure team output, and the data shows delivery is fine; pushing the team harder does nothing for a sponsor-specific perception gap.
2. BCorrect: the dip is isolated to the sponsor, so the fix is targeted: name an owner for the relationship and hold a focused conversation to learn what changed.
3. CNew risk categories add administration without explaining or addressing why one stakeholder's satisfaction is falling.
4. DSchedule performance is stable, so rebaselining responds to a problem the data does not show.
More notes below ↓
WP 04A regulatory stakeholder constantly asks detailed questions about your project and attends all open meetings. However, you discover they are actively criticizing project decisions to senior leadership. How should you adapt your engagement strategy for this stakeholder?
Debrief answer to open the notes
1. APublic confrontation damages the relationship and is likely to deepen the opposition.
2. BAn advisory role may come later, but offering one before understanding the concerns could amplify the criticism.
3. CAttendance shows interest, not support; the criticism reaching leadership shows the assumption is wrong.
4. DCorrect: Re-assess where the stakeholder actually stands and tailor engagement to their concerns; high interest is not the same as support.
More notes below ↓
WP 05Stakeholders state success metrics for a new portal. Which three measurable KPIs best translate those outcomes into acceptance thresholds?
Debrief answer to open the notes
1. ARevenue and feature counts are business or output measures; they do not test whether the portal delivers the outcomes stakeholders named.
2. BCorrect: each KPI pairs a user outcome with a measurable threshold, so acceptance becomes a clear pass or fail test.
3. CUptime, defect density, and milestone percentage describe system and project health rather than the stakeholder outcomes being accepted.
4. DTicket closures, commit frequency, and velocity track team activity, not whether users achieve the intended results.
More notes below ↓
WP 06An executive dashboard must display stakeholder satisfaction. Which fields and structure are required?
Debrief answer to open the notes
1. ACorrect: executives need direction, a tolerance line, accountability, and the next action on each row, which turns satisfaction data into decisions.
2. BComplete historical tables bury the signal; an executive view should summarize trends rather than reproduce the data warehouse.
3. CCurrent values without trends or thresholds cannot show whether satisfaction is improving or crossing a tolerance.
4. DRaw survey responses leave the analysis to the executive and fit an appendix better than a dashboard.
More notes below ↓
WP 07A newly classified manage-closely stakeholder has missed the last three alignment meetings. What is the most appropriate immediate outreach?
Debrief answer to open the notes
1. ASending a proxy keeps the stakeholder at arm's length; a manage-closely stakeholder needs direct contact with the project manager.
2. BCutting meeting frequency lowers engagement exactly when a key stakeholder is already drifting away.
3. CCorrect: recurring one-on-ones with briefs tailored to the stakeholder's decisions make engagement easier to give and restore the close contact this quadrant requires.
4. DA newsletter is a push channel suited to keep-informed stakeholders, not to someone whose decisions the project depends on.
More notes below ↓
WP 08A regulated-stakeholder workshop must decide contentious items. Which agenda and closing steps minimize late objections?
Debrief answer to open the notes
1. AOpen discussion without pre-work or decision rules invites the late objections the workshop is meant to prevent.
2. BCorrect: pre-work and agreed decision rules surface objections early, and formal sign-off closes outcomes so they cannot quietly reopen later.
3. CVerbal agreement with no circulated minutes leaves nothing to point to when someone later disputes a decision.
4. DInformal records pushed to a later meeting delay confirmation and make regulated decisions hard to evidence.
More notes below ↓
WP 09Within a three-month increment, which monitoring regimen best detects expectation divergence early?
Debrief answer to open the notes
1. AA monthly report seen only by the steering committee is too slow and too far from users to catch shifting expectations.
2. BA survey after delivery detects divergence only when it is too late to adjust within the increment.
3. CCorrect: frequent demos plus targeted surveys give early feedback loops, and preset thresholds say when a gap is escalated rather than just noted.
4. DVelocity measures team throughput and involves no stakeholders, so it cannot reveal changing expectations.
More notes below ↓
WP 10Following a major scope change mandated by regulatory updates, several key stakeholders express frustration, claiming they were blindsided. Engagement levels drop, and trust in the project manager diminishes. What is the most appropriate action for the project manager to take to rebuild stakeholder credibility?
Debrief answer to open the notes
1. ACorrect: rebuilding credibility means openly resetting expectations with stakeholders and recording the new agreements in updated artifacts so everyone works from the same baseline.
2. BSending proof that the change was mandatory defends the project manager but does nothing to restore engagement or shared expectations.
3. CPrivate apologies can ease feelings, yet without realigning expectations and documenting agreements the same gap will return.
4. DA regulatory mandate is not the project's to reverse; a change request against it wastes governance time.
More notes below ↓
WP 11A stakeholder requests a "fast and reliable system." Which sequence best converts this into measurable acceptance criteria?
Debrief answer to open the notes
1. ACorrect: eliciting examples, outcomes, metrics, constraints, and a definition of done turns a vague wish into criteria that can be tested and agreed.
2. BWriting stories straight from vague wording carries the ambiguity into the backlog, where it later becomes rework.
3. CDeferring the conversation leaves the requirement vague and delays the clarification that acceptance depends on.
4. DBenchmarks from one technical source miss the stakeholder's own meaning of reliability and other constraints.
More notes below ↓
WP 12A commitment to a high-influence stakeholder was not recorded, eroding trust. What immediate step restores credibility?
Debrief answer to open the notes
1. ACarrying on without a record leaves the commitment unverified and invites the same breakdown again.
2. BThe project manager can repair this directly; escalating before talking to the stakeholder makes a small lapse look larger.
3. CWaiting for the next status meeting extends the period of lost trust when a direct fix is available now.
4. DCorrect: owning the omission, recording the commitment, and confirming next steps restores credibility through transparency and follow-through.
More notes below ↓
WP 13Stakeholder value metrics conflict with regulatory compliance obligations. Which prioritization approach produces a defensible delivery plan?
Debrief answer to open the notes
1. AOptimizing only for schedule compression ignores both stakeholder value and the compliance obligations that must be met.
2. BCompliance is a constraint, not a deferrable feature; postponing it can make the delivered value unusable.
3. CInfluence and urgency are not value, and ranking by them leaves compliance trade-offs undocumented.
4. DCorrect: WSJF weighs value and time criticality against size, and recording the regulatory trade-offs makes the resulting order defensible.
More notes below ↓
WP 14Sponsor satisfaction is declining. Which executive summary best addresses the situation?
Debrief answer to open the notes
1. ACorrect: an executive summary should explain why satisfaction is slipping and give a few clear options to decide on.
2. BAsking for more budget and time before explaining the cause treats a relationship problem as a resource problem.
3. CFocusing on team shortcomings shifts blame and does not address what the sponsor is actually unhappy about.
4. DDetailed technical analysis suits a working session, not a summary meant to support a quick executive decision.
More notes below ↓
WP 15A project requires a stakeholder register that supports both engagement planning and regulatory audit trails. Which minimal set of fields satisfies both needs?
Debrief answer to open the notes
1. AOmitting role, influence, and engagement level leaves the register unable to support engagement planning or show an auditor who was assessed and how.
2. BName, role, and channel support communication logistics but give no basis for engagement planning or audit review.
3. CEngagement level and RACI help, yet without influence, interest, and concerns the register cannot justify the engagement strategy.
4. DCorrect: these fields cover identification, assessment, current engagement, channel, and concerns, which together support planning and leave an auditable record.
More notes below ↓
WP 16Technical acceptance criteria are too complex for stakeholders. Which rewrite enables validation?
Debrief answer to open the notes
1. ACorrect: plain-language checks let stakeholders validate the result, and mapping them to test cases keeps the technical rigor behind each check.
2. BDropping the technical checks makes the criteria readable but no longer verifiable.
3. CMore jargon widens the gap between the criteria and the people who must accept them.
4. DKeeping the original steps for everyone ignores the reason stakeholders cannot validate them in the first place.
More notes below ↓
WP 17A project dashboard must serve sponsor, operations, and end-user groups. Which design best balances segment thresholds and escalation triggers?
Debrief answer to open the notes
1. ATraffic lights without numbers hide where the threshold sits and why a status changed, which weakens escalation decisions.
2. BAn issue count and raw exports give no segment view and no trigger for when to escalate.
3. CCorrect: per-segment NPS and CSAT show each group's own picture, and color-coded alerts tie each measure to a defined escalation trigger.
4. DA single delivery metric drilled down only for the sponsor ignores the operations and end-user groups the dashboard must serve.
More notes below ↓
WP 18Low-influence, low-interest stakeholders require monitoring. Which cadence avoids wasted resources while managing risk?
Debrief answer to open the notes
1. AMonthly in-person briefings for this group spend effort where little is at stake.
2. BAn engagement plan matching the high-influence group wastes effort on stakeholders who neither need nor want it.
3. CWeekly detailed meetings are far more than low-influence, low-interest stakeholders require.
4. DCorrect: light, periodic monitoring with outreach triggered by a change in their position keeps effort proportionate while still catching emerging risk.
More notes below ↓
WP 19Stakeholder requests exceed capacity while contractual deliverables are at risk. What is the best next action?
Debrief answer to open the notes
1. AInformal changes bypass change control and put the contractual deliverables at further risk.
2. BCorrect: a phased MVP protects the contractual commitments first, and recording the trade-offs keeps the decision transparent and governed.
3. CApproving everything ignores capacity and turns a scope problem into a contract dispute.
4. DA blanket freeze avoids the trade-off conversation and can leave legitimate needs unaddressed for a long time.
More notes below ↓
WP 20A sponsor demands immediate enterprise-wide rollout of a new platform despite identified integration risks. What is the project manager's best recommendation?
Debrief answer to open the notes
1. ATraining everyone now prepares users for a rollout whose integration risks are still unresolved.
2. BEscalating before offering a workable alternative passes the problem up instead of giving the sponsor options.
3. CFunding parallel legacy support may help later but does not test whether the integrations work.
4. DCorrect: a limited pilot tests the platform against the known integration risks before the whole enterprise depends on it, which answers the sponsor's urgency with evidence.
More notes below ↓

Open a row to answer. Keys: 1–4 or A–D answer, N opens the next row.