about 4.1% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Every project GCHS runs (a wheelchair ramp for a homeowner in Port Arthur, a roof replacement funded by a
disaster-recovery grant, a whole-house rehab) has more than one person who cares how it turns out. The homeowner,
the grant officer, the city inspector, the neighbor whose driveway your crew parks across, your own board: each of
them shows up with a picture in their head of what "done" looks like. Aligning expectations is the
work of getting those pictures close enough together, before the work starts, that nobody is shocked later.
Align versus manage: two different jobs
The exam separates these deliberately, and so should you.
Aligning is front-loaded and negotiated. You surface what each party assumes, name the gaps
out loud, and reach an explicit agreement: scope, acceptance criteria, definition of done, roles, how decisions
get made. It is a conversation between people, not a memo.
Managing is continuous. Once the agreement exists, you keep people informed, catch drift,
respond to changing needs, and re-align when reality moves.
If you skip alignment and jump to managing, you spend the rest of the project defending a definition nobody ever
agreed to. On the exam, when a stakeholder is surprised late in a project, the root cause is almost always missing
alignment at the front, and the best answer is to go re-establish shared understanding, not to argue about the
contract.
Know who you are aligning with
Stakeholder identification is not a one-time task. New stakeholders appear as the project moves: a code official
shows up at framing inspection, an insurance adjuster appears after a storm, a second funder joins mid-year. The
stakeholder register records who they are, what they care about, their influence, and how they want
to be involved. Analysis then sorts them: power/interest grids, salience models, or simple influence-versus-impact
thinking. The point of the analysis is not the picture; it is deciding how much of your attention each person
deserves.
The stakeholder engagement assessment matrix
This is PMI's tool for making engagement measurable rather than vague. You plot each stakeholder's
current level of engagement (C) and their desired level (D). Where C and D differ,
you have a gap that needs a deliberate action, not a hope.
Level
What it looks like
GCHS example
Unaware
Does not know the project exists or its impact
Neighbor who has not been told a dumpster arrives Monday
Resistant
Aware, and opposed to the change or its effects
Homeowner's adult son who thinks the ramp will hurt resale value
Neutral
Aware, neither supportive nor opposed
City permit clerk processing the application
Supportive
Aware and in favor, but not actively working the project
Board member who approves the budget and moves on
Leading
Aware and actively engaged in making it succeed
Grant officer who co-designs the reporting format with you
A useful habit: mark C and D in the same cell of a grid. If the code official is Neutral and Neutral is fine,
leave it alone. Trying to move everyone to Leading wastes the attention you owe the stakeholders who actually
need it.
Key points
Align first, manage continuously; surprise late in a project usually traces to missing alignment early
The stakeholder register is living; identification repeats throughout the project
The engagement assessment matrix compares current to desired, and gaps drive actions
Desired is not always Leading; sometimes Neutral is exactly right
Alignment is achieved through conversation and written agreement, not through announcement
Building shared understanding
PMI puts real weight on shared understanding: the idea that people agreeing to different things
in the same meeting is the normal failure mode. Techniques that force the picture into the open:
Charter or project brief workshop: write the purpose, success measures, and boundaries with
stakeholders in the room, not for them afterward.
Acceptance criteria and definition of done: concrete, testable statements. "Grab bars
installed" is weak. "Grab bars anchored to blocking, 1.25 to 2 inch diameter, 33 to 36 inches above finished
floor, resisting 250 pounds" is alignment.
Prototypes, mock-ups, walkthroughs: a homeowner who stands on a chalk outline of the new ramp
landing understands slope better than one who reads a drawing.
Backlog refinement with stakeholders present: in an adaptive approach, alignment happens
repeatedly at small scale rather than once at large scale.
Assumption logs and open questions: writing down what you are assuming turns silent
disagreement into a visible item someone can challenge.
Alignment in adaptive and hybrid work
Roughly six of every ten exam questions assume an adaptive or hybrid setting, and adaptive work aligns
expectations differently: instead of one big agreement up front, you set direction with a product vision and
then re-align every iteration through reviews and demos. The product owner (or, at GCHS, the
program manager who owns the client relationship) carries the accountability for value and priority. Expectations
stay aligned because the stakeholder sees working results on a fixed cadence, not because the scope document was
perfect.
Hybrid is common in construction-flavored work: the permit, structural, and code-compliance path is predictive
with hard gates, while finish selections, accessibility fixture choices, and homeowner-facing decisions run
adaptively. Say which parts are which, out loud, at kickoff; misalignment often comes from a stakeholder assuming
the whole project is as flexible as the part they can see.
Common trap
"I sent them the scope document" is not alignment. One-way transmission does not confirm shared understanding.
Alignment requires a feedback loop: the stakeholder repeats back what they expect, or signs off on specific
acceptance criteria, or reacts to something tangible. On the exam, an answer that only sends information
loses to one that confirms understanding.
When expectations cannot be aligned
Sometimes a stakeholder wants something the project genuinely cannot deliver: a funder who wants twenty homes
for a fifteen-home budget, or a homeowner who expects a full kitchen remodel from an accessibility grant. The
sequence PMI rewards is: understand the underlying need first (why twenty? is the metric homes, or people served?),
then present options and trade-offs with data, then negotiate a documented agreement, and only then escalate if the
gap is outside your authority. Escalation is a legitimate tool; it is just rarely the first tool.
Sustainability and ESG expectations increasingly show up in this space. A funder may expect reporting on
energy-efficiency outcomes or on materials sourcing that was never scoped. Treat it exactly like any other
expectation gap: surface it early, cost it honestly, and get the agreement in writing rather than absorbing it
quietly.
Practice Questions
1. At kickoff for a whole-house rehab, the homeowner, the grant officer, and the crew lead each describe a different finished result. What should the project manager do FIRST?
Start work on the items all three mentioned and defer the rest
Send all three the signed scope of work by email
Facilitate a working session to surface each party's expectations and reach documented agreement on scope and acceptance criteria
Ask the sponsor to decide whose version is correct
Answer: c. Alignment is achieved through a two-way conversation that produces an explicit, documented agreement. Emailing the scope is one-way transmission and does not confirm shared understanding; escalating to the sponsor skips the PM's own facilitation role.
2. Which BEST describes the difference between aligning and managing stakeholder expectations?
Aligning applies to predictive projects, where scope is baselined; managing applies to adaptive projects that use a backlog
They are two names for the same activity
Aligning sets an explicit shared agreement up front; managing keeps it current as conditions change
Aligning is done by the sponsor; managing is done by the project manager
Answer: c. Alignment is the front-loaded negotiation that produces shared understanding; management is the ongoing work of keeping stakeholders informed and re-aligning as reality shifts. Both apply to any delivery approach.
3. A stakeholder engagement assessment matrix shows the city code official as Current=Neutral, Desired=Neutral. What action does this call for?
Launch a campaign to move the official to Leading
No change action is needed; maintain current communication
Escalate to the sponsor because the official is not yet supportive of the project
Remove the official from the stakeholder register
Answer: b. The matrix drives action only where current and desired differ. Neutral is an appropriate target for many regulatory stakeholders; spending effort to move everyone to Leading diverts attention from real gaps.
4. Halfway through a ramp installation, a neighbor complains that no one told her about the dumpster in the shared drive. Her engagement level was never assessed. What does this MOST indicate?
The communications management plan needs a bigger distribution list and more frequent status emails
The neighbor is out of scope and should be ignored
Stakeholder identification was treated as a one-time activity, not an ongoing one
The crew failed to follow the safety plan
Answer: c. Stakeholders emerge throughout a project, so identification and register updates must be continuous. Adding names to a distribution list treats the symptom without fixing the process that missed her.
5. Which statement of acceptance criteria BEST supports expectation alignment?
Bathroom work will meet all applicable standards
Bathroom will be completed to the homeowner's satisfaction
Bathroom will be made accessible
Grab bars anchored to blocking, 33 to 36 inches above finished floor, resisting a 250-pound load
Answer: d. Alignment requires concrete, testable criteria that two people cannot interpret differently. Phrases like 'accessible', 'applicable standards', and 'satisfaction' each leave the definition of done in someone's head.
6. On a hybrid project, permits and structural work follow a predictive plan while finish and fixture choices are handled adaptively. A homeowner is upset that the framing layout cannot change as easily as the paint colors did. What is the root cause?
The approach and its limits were not explained at kickoff
The homeowner is being unreasonable
The team used the wrong delivery approach and should have kept the whole project fully predictive
Change control was applied too strictly
Answer: a. Hybrid projects require explicit alignment on which parts are flexible and which are gated. Stakeholders generalize from the part they can see, so naming the boundary up front prevents exactly this surprise.
7. Which of the following is an example of ALIGNING rather than MANAGING stakeholder expectations?
Posting sprint results to a shared dashboard that all stakeholders can open at any time
Facilitating a kickoff workshop to agree on acceptance criteria up front
Sending a weekly status email
Updating the risk register after a schedule slip
Answer: b. Aligning is the front-loaded, negotiated work that produces an explicit agreement before work starts. The other three are all ongoing management activities that keep an already-aligned picture current.
8. In an adaptive GCHS project, stakeholders attend backlog refinement sessions regularly. What does this achieve with respect to expectations?
It re-aligns expectations repeatedly at small scale, not once at large scale
It substitutes for acceptance criteria because stakeholders clarify each item in the session
It is purely an administrative reporting step
It replaces the need for a stakeholder register
Answer: a. Adaptive alignment happens repeatedly at small scale through activities like refinement, rather than as one large up-front agreement. It does not remove the need for a register or for acceptance criteria; it complements both.
9. A funder insists on twenty completed homes for a budget sized for fifteen. What should the project manager do FIRST?
Understand the underlying need behind the number, such as whether the real metric is homes or people served
Decline the grant
Escalate immediately to the funder's board
Agree to twenty homes and quietly cut scope per home to compensate
Answer: a. The sequence PMI rewards starts with understanding the underlying need, then presenting options and trade-offs with data, then negotiating, and escalating only if the gap remains outside the project manager's authority. Quietly cutting scope per home hides a decision the funder never agreed to.
10. A project manager writes, "I am assuming the homeowner wants the ramp on the south side of the house," in a document shared with the team before proceeding. What technique is this?
Communications management plan
Stakeholder register update
Acceptance criteria
Assumption log
Answer: d. Writing down an assumption turns a silent, unconfirmed belief into a visible item someone can challenge, which is exactly the purpose of an assumption log. It is not a register entry about a person, nor a testable acceptance condition for a deliverable.
11. A homeowner stands on a chalk outline of a proposed ramp landing marked on the driveway and immediately says the turn is too tight. Which alignment technique is this?
RACI chart
Stakeholder engagement assessment matrix
Assumption log
Prototype / mock-up walkthrough
Answer: d. A tangible mock-up that a stakeholder can react to on the spot is a prototype walkthrough, and it resolved the ambiguity about slope faster than a drawing would have. Neither the engagement matrix nor a RACI chart involves anything physical to react to.
12. A funder mentions, almost in passing, that they would like reporting on materials sourcing that was never scoped or budgeted. What should the project manager do?
Wait until the final report is due to address it, since nothing has been promised yet
Surface it early, cost it honestly, and get the agreement in writing
Ignore it since it was mentioned informally
Absorb the extra work quietly to avoid conflict
Answer: b. An ESG or sourcing expectation is treated like any other expectation gap: surfaced early, costed honestly, and documented, rather than absorbed silently or discovered at closeout.
13. At kickoff for a hybrid rehab project, what should the project manager do regarding the boundary between baselined and iteratively handled scope?
State explicitly, out loud, which parts are frozen and which are still open
Leave it implicit so the team retains flexibility
Document it only in the risk register
Address it only if a stakeholder later asks
Answer: a. Stakeholders generalize from the part of the project they can see, so naming the frozen-versus-flexible boundary out loud at kickoff prevents exactly the kind of surprise that shows up later. Leaving it implicit or burying it in a document nobody reads produces the same misalignment.
14. After presenting trade-offs and negotiating in good faith, a funder still insists on a scope change the project genuinely cannot absorb within budget. What is the appropriate NEXT step?
Absorb the change without further discussion
Refuse to discuss it further and cite the signed agreement as the final word on the scope of work
Repeat the same negotiation session again
Escalate the gap, since it is outside the project manager's authority to resolve alone
Answer: d. Escalation is a legitimate tool once genuine negotiation has been tried and the gap remains beyond the project manager's authority; it is just rarely the first tool. Repeating the same conversation or unilaterally absorbing the change does not resolve a genuine budget constraint.
Glossary
Align
The front-loaded, negotiated work of surfacing each party's expectations and reaching an explicit, documented agreement before work begins.
Manage (expectations)
The continuous work of keeping stakeholders informed, catching drift, and responding to changing needs once alignment exists.
Stakeholder engagement assessment matrix
A tool plotting each stakeholder's current engagement level against the desired level, across unaware, resistant, neutral, supportive, and leading.
Assumption log
A record of what the team is assuming to be true, turning silent disagreement into a visible item someone can challenge.
Acceptance criteria
Concrete, testable conditions that a deliverable must meet, written to leave no room for differing interpretation.
Hybrid delivery
An approach in which some scope, such as permits and structural work, is baselined and gated, while other scope, such as finish selections, is handled iteratively.
Product owner
In adaptive work, the accountable voice for value and priority who carries alignment through reviews and demos rather than a single up-front agreement.
Escalation
Raising an expectation gap beyond the project manager's authority; a legitimate but last-resort tool, used only after understanding, options, and negotiation have been tried.