about 4.1% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Alignment gets everyone pointed the same direction on day one. Managing expectations is what
keeps them pointed that way through six months of weather delays, material substitutions, a homeowner's health
change, and a funder's new reporting requirement. It is the daily, unglamorous work of engagement: monitoring how
people feel, communicating before they have to ask, handling resistance, and re-negotiating when the world moves.
Stakeholder engagement assessment matrix: comparing each stakeholder's desired engagement level
against their current, observed level. A gap between the two, like the homeowner's or the funder's, is a
variance that calls for a response; alignment, like the code official's, needs monitoring only.
Engagement is monitored, not assumed
PMI treats stakeholder engagement as something you measure and correct, the same way you measure schedule
variance. The signals are behavioral: attendance at reviews, speed of decisions, tone of questions, whether people
bring problems to you early or you hear about them from someone else. When the engagement assessment matrix says a
stakeholder should be Supportive and their behavior says Resistant, that is a variance requiring a response.
Warning sign
What it usually means
Response
Stops attending demos or walkthroughs
Disengagement or lost confidence
Direct one-to-one conversation; find out what changed
Decisions take longer each cycle
Unclear authority, or fear of committing
Clarify decision rights; reduce decision size
Requests routed around the PM
Trust gap or unclear process
Rebuild the relationship; make the process easy to use
Surprise objections late in the work
Information is not reaching them in a usable form
Revisit the communications plan for that stakeholder
Repeated re-litigation of settled decisions
The original agreement was never truly shared
Return to alignment; re-confirm criteria in writing
Proactive beats reactive, every time
The single most reliable way to lose a stakeholder's trust is to let them discover bad news on their own. If the
accessible shower pan is back-ordered four weeks, the homeowner should hear it from the project manager within a day
of the PM knowing, with an assessment of impact and at least one option, not at the walkthrough where the bathroom
is obviously unfinished. On the exam, an answer choice that informs the affected stakeholder early, with impact and
options, almost always beats one that waits for more certainty.
Key points
Engagement is monitored against the desired level and corrected like any other variance
Deliver bad news early, with impact and options: never let stakeholders discover it themselves
Address the person directly before escalating; escalation is a late tool, not a first one
Resistance is information: find the objection before trying to overcome it
Changed expectations follow the change process; they are not absorbed silently
Handling resistance and difficult stakeholders
Resistance is data. Someone opposing the project usually has a reason that is rational from where they sit: the
homeowner's son may be worried about resale value, the code official may have been burned by a previous contractor,
a board member may be protecting a budget line. The sequence that works, and that the exam rewards:
Listen actively: ask open questions, paraphrase back, and confirm you have the objection
right before responding to it.
Separate position from interest: "no ramp on the front" is a position; "I do not want the
house to look institutional" is the interest, and it has several solutions.
Address the interest with options: bring choices and trade-offs, not a single verdict.
Document the agreement: a resolved objection that lives only in memory comes back.
Escalate only when the decision genuinely exceeds your authority, and then with options and
impacts attached.
Expectations change, so manage the change
Stakeholder needs legitimately shift. A homeowner's mobility declines and a threshold ramp is no longer enough. A
funder's board adds an ESG reporting requirement mid-grant. None of this is misbehavior; it is the environment
changing. What matters is the discipline: assess impact on scope, schedule, cost, and risk; route it through the
change process appropriate to your approach; and confirm the new agreement.
In predictive work that means a change request evaluated by the change control board. In adaptive work it usually
means the item goes to the backlog and the product owner re-prioritizes; the scope of the release flexes, or
something else drops out. In both cases the unacceptable move is the same: quietly absorbing new work and hoping the
schedule holds.
Scope creep starts as a favor
"While you are here, could you also…" is how nearly every GCHS overrun begins. The answer is not a flat no; it
is "let me price that and get it approved." Saying yes on the spot converts a documented project into an informal
one, and the crew absorbs the difference in unpaid overtime.
Managing expectations across a portfolio of stakeholders
Different stakeholders need different management. A funder needs outcome data and early warning of variance. A
homeowner needs plain-language updates and a predictable point of contact. An inspector needs accurate documents and
no surprises. Regulators need compliance evidence. Trying to serve them all with one status report satisfies none of
them; the communications approach follows the engagement plan, not convenience.
Increasingly, funders and municipal partners ask for sustainability and community-impact reporting: energy
savings from insulation and window work, households kept in place instead of displaced, materials diverted from
landfill. Manage these like any other expectation: confirm exactly what is being measured, agree how it is
collected, and report it on a rhythm rather than scrambling at the close of a grant year.
Never do this
Do not manage an upset stakeholder by going over their head first. Emailing the sponsor about a homeowner's
complaint before speaking with the homeowner damages trust, wastes the sponsor's attention, and is nearly always
the wrong answer on the exam. Engage the person directly first.
Practice Questions
1. A project manager learns that an accessible shower pan is back-ordered four weeks. What should the project manager do FIRST?
Report it in the next monthly status package
Wait until a second supplier independently confirms the four-week delay and quotes an alternate date
Re-sequence the schedule quietly and hope to recover the time
Inform the homeowner promptly with the impact and options
Answer: d. Stakeholders should never discover bad news on their own, and early notice with impact and options preserves trust and lets them participate in the response. Waiting for more certainty only shortens their reaction time.
2. A homeowner's adult son objects to a front-yard ramp, saying it will make the house look institutional. What should the project manager do NEXT?
Escalate to the executive director
Ask the homeowner to overrule her son
Explain that the design already meets code and the accessibility standards, then proceed as planned
Explore options that address the appearance concern, such as other placement or materials
Answer: d. 'No front ramp' is a position; the interest is appearance, and interests usually have multiple solutions. Citing code answers a question he did not ask, and escalation skips the direct engagement PMI expects first.
3. Which observation is the STRONGEST early warning that a key stakeholder is disengaging?
They requested a copy of the schedule
They forwarded a vendor recommendation
They have stopped attending reviews and walkthroughs
They ask detailed questions in every review
Answer: c. Withdrawal from the feedback loop means drift accumulates unseen and confidence may already be lost. Detailed questions and information requests are signs of active, healthy engagement.
4. Mid-project, a homeowner's mobility declines and a threshold ramp will no longer meet her needs. What should the project manager do?
Assess the impact on scope, schedule, cost, and risk and route it through change control
Absorb the added work to be compassionate
Complete the original scope as planned and start a separate project later without discussing it with her
Tell her the scope is fixed
Answer: a. Legitimate changes in need still require impact assessment and an approved change; quietly absorbing work creates unfunded scope and hides the true cost. Compassion is delivered through a fast, honest change process, not by skipping it.
5. During a walkthrough a homeowner asks the crew to also replace a leaking hose bib 'while you are here.' What is the BEST response from the project manager?
Refuse and explain the scope is closed
Acknowledge the request, price it, and get approval before committing
Have the crew do it without recording it
Approve it on the spot as good customer service, since the cost of one hose bib is small
Answer: b. Uncontrolled small additions are how overruns begin, but a flat refusal damages the relationship. Acknowledging and pricing keeps the door open while preserving the documented agreement.
6. An adaptive team receives a new stakeholder requirement mid-iteration. What is the BEST handling?
Add it to the backlog for the product owner to prioritize against other items
Reject it outright and ask the stakeholder to resubmit at the next release planning session
Escalate it to the change control board
Add it to the current iteration immediately
Answer: a. Adaptive delivery welcomes change but protects the iteration in progress; the backlog and the product owner's prioritization are the mechanism. A formal change control board is a predictive construct that does not fit here.
7. A newly recruited board member emails the project manager directly asking for detailed weekly cost reports, bypassing the agreed communications plan. What should the project manager do FIRST?
Comply immediately and send the detailed weekly cost reports so the new board member feels heard and valued
Ignore the request since it conflicts with the plan
Discuss with the board member to understand the need and reconcile it with the engagement plan
Escalate the request to the executive director
Answer: c. A new information need is real data, and the right move is to understand it and update the engagement approach, not to silently obey or silently refuse. Escalating a routine communications preference skips a conversation the PM should have directly.
8. Which artifact records, for each stakeholder, both a current engagement level (such as Resistant or Neutral) and a desired engagement level (such as Supportive or Leading)?
The stakeholder register
A RACI chart
The communications management plan
The stakeholder engagement assessment matrix
Answer: d. The engagement assessment matrix plots current against desired engagement so gaps are visible and actionable. The stakeholder register holds identifying and influence data but not this current-versus-desired comparison, and a RACI chart addresses decision roles, not engagement level.
9. On an adaptive team, a stakeholder representative stops engaging visibly after several iteration reviews. What is the BEST first step?
Remove them from future reviews
Have a direct conversation to understand what changed
Add a formal escalation item to the steering committee agenda
Increase the frequency of status emails to them
Answer: b. Withdrawal is a warning sign, and the direct approach PMI expects is a one-to-one conversation to find the cause before anything else. Escalating or adding more one-way communication does not address why they stopped engaging.
10. A junior engineer wants to escalate a disagreement with a stakeholder straight to the sponsor without speaking to the stakeholder first. As a servant leader, how should the project manager respond?
Handle the disagreement personally without involving the engineer
Direct the engineer to send a formal memo to the sponsor documenting the disagreement instead
Coach the engineer to engage the stakeholder directly first and offer support
Approve the escalation to save time
Answer: c. Servant leadership builds the team's own capability rather than taking the problem away; coaching toward direct engagement, with support, teaches the right instinct for next time. Approving the premature escalation or doing it yourself both skip the direct conversation PMI expects first.
11. A code official insists on additional inspection visits beyond what the permit requires. Applying interest-based negotiation, what should the project manager do FIRST?
Refuse, citing the permit requirements
Ask questions to understand the underlying concern driving the request
Escalate to the building department director
Agree to every additional visit requested
Answer: b. The request for extra visits is a position; understanding the interest behind it, such as a prior bad experience with a contractor, opens up options a flat refusal or blanket agreement would miss. Escalating skips direct engagement that has not yet been tried.
12. A funder's board adds a new ESG reporting requirement mid-grant on a predictively managed rehab program. What should the project manager do?
Submit it through the change control board for assessment of scope, schedule, and cost
Delegate the decision to the program specialist
Quietly add the reporting to the next status update
Refuse it outright since the new reporting requirement was not in the original grant agreement
Answer: a. A legitimately changed requirement still needs an impact assessment and formal approval before it is absorbed into predictive work. Quietly adding it hides the true cost, and a flat refusal ignores a funder's real and often unavoidable need.
13. A stakeholder who was expected to be Leading on the engagement assessment matrix is instead behaving as Neutral. This represents:
An acceptable difference in communication style
A reason to remove them from the stakeholder register
Something to note only at project close-out
An engagement variance requiring a response
Answer: d. Any gap between desired and current engagement is a variance to investigate and correct, the same discipline applied to schedule or cost variance. It is not something to simply tolerate, erase from the register, or defer to close-out.
14. During a heated site meeting, a subcontractor raises a strong objection to a schedule change. What should the project manager do FIRST?
End the meeting immediately and follow up by email once everyone has calmed down
Ask another team member to handle it
Listen actively, paraphrase the objection, and confirm understanding first
Overrule the objection to protect the schedule
Answer: c. Confirming you have the objection right, before responding to it, is the first move in handling resistance and prevents answering a concern the subcontractor did not actually raise. Overruling, deflecting, or delegating away from the moment all skip that step.
Glossary
Stakeholder engagement assessment matrix
A tool comparing each stakeholder's current, observed engagement level against the desired level, used to spot and prioritize gaps.
Engagement level
A stakeholder's disposition toward the project, ranging from Unaware through Resistant, Neutral, Supportive, to Leading.
Position
The specific demand a stakeholder states, such as "no ramp on the front."
Interest
The underlying concern behind a position, such as not wanting the house to look institutional; interests usually admit several possible solutions.
Escalation
Raising a decision or conflict to a higher authority when it genuinely exceeds the project manager's authority to resolve; a late tool, not a first one.
Scope creep
Uncontrolled expansion of project or product scope through unapproved requests, often introduced informally as a small favor.
Change request
A formal proposal to modify a document, deliverable, or baseline, evaluated for impact before approval.
Backlog reprioritization
In adaptive work, the product owner's ongoing reordering of backlog items to reflect newly discovered or changed stakeholder needs.