about 4.1% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Before a project team can argue about schedule, budget, or who owns a task, everyone on it has to agree on
one thing: what are we actually trying to accomplish, and how will we know when we have done it?
PMI calls this building a shared understanding or developing a common vision. It sounds soft.
It is not. Most of the rework, most of the change orders, and most of the late-stage arguments on a GCHS
accessibility retrofit trace back to two people who thought they agreed and did not.
A concrete example: a homeowner says she wants a bathroom that is accessible. The crew lead hears
grab bars. The occupational therapist hears a 60-inch turning circle. The grant officer hears a specific line
in the funding agreement. The homeowner meant she wants to be able to shower without her daughter present. Four
visions, one word. The project manager's job at initiation is to surface that gap before the tile goes down.
Vision, objectives, and the layers underneath
A useful way to think about it is a chain, from fuzzy to concrete. Each layer has to trace back to the one
above it, or you are building something nobody asked for.
Business need / benefit: why the organization is spending money at all. For GCHS:
keeping an aging homeowner safely in her own home instead of in a facility.
Project vision: a short, plain statement of the desired end state that a
non-specialist can repeat back. This is what you say at the kickoff.
Objectives: measurable, time-bound expressions of the vision (the SMART idea:
specific, measurable, achievable, relevant, time-bound).
Deliverables and acceptance criteria: the physical things produced, and the conditions
that make them acceptable.
Tasks / backlog items: the day-to-day work.
When someone on the crew asks why are we doing it this way?, a healthy project can walk the chain
upward and answer. When it cannot, that is a signal the vision was never really shared; it was announced.
Key points
Shared understanding is built through dialogue; it is not created by sending a document.
Confirm understanding by having people restate it in their own words, not by asking
any questions? Silence is not agreement.
Alignment decays. Re-confirm it at phase gates, at iteration boundaries, and whenever a new person joins.
On the exam, the answer that gets the parties in a room to reach shared understanding almost
always beats the answer that documents, escalates, or decides unilaterally.
The artifacts that carry the vision
PMI expects you to know which document does which job, and to reach for the right one. Two get confused
constantly: the project charter and the team charter.
Artifact
Who authors it
What it settles
Typical trigger
Project charter
Sponsor (issued to the PM)
Formally authorizes the project, names the PM and their authority, states high-level objectives,
success criteria, key risks, budget envelope
Team formation, and revisited when the team changes
Product vision statement (adaptive)
Product owner with the team and key stakeholders
Who the product is for, what problem it solves, why it beats the alternative
Chartering / release planning
Definition of done (adaptive)
The team
The shared checklist that makes any increment genuinely complete: inspected, cleaned, documented
Team formation; refined at retrospectives
Acceptance criteria
Product owner / customer with the team
What makes this particular deliverable acceptable
Backlog refinement, per item
Notice the pattern: the project charter comes down from the sponsor, while the team charter,
definition of done, and ground rules are built by the team. A PM who writes the ground rules alone
and hands them out has produced a document, not an agreement, and the team will not defend it.
Techniques that actually build shared understanding
These are the moves PMI wants to see you make. Most are cheap and take an hour.
Kickoff meeting. Everyone hears the same words at the same time, with the sponsor
present to say why it matters. In a hybrid project you hold one at project start and a smaller one at each
release or phase.
Facilitated chartering workshop. Instead of presenting the vision, the PM facilitates
the team writing it. Slower, and vastly stickier.
Active listening. Reflect back what you heard (so what I am hearing is that the
ramp has to be usable before the holidays, even if the porch rail comes later, is that right?) before
you respond.
Prototypes, mockups, and walkthroughs. Ambiguity dies fastest when people can point at
something. Taping the wheelchair turning circle on the existing floor settles an argument that three emails
would not.
Personas and user stories.As a homeowner using a walker, I need a threshold no higher than
half an inch so that I can cross without lifting. The so that clause states the intended benefit, the vision in miniature.
Story mapping / release roadmap. Lays the whole journey out visually so people can see
what is in, what is later, and what is out.
Information radiators. A task board, burndown, or impediment list posted where everyone
can see it (including on the job trailer wall) keeps the picture shared without meetings.
Retrospectives and reviews. Adaptive teams re-confirm alignment every iteration; the
review shows real work to real stakeholders and catches drift within weeks, not months.
Common trap
An exam item describes a team that is confused about direction, and one choice is send the team the
project charter again or update the communications management plan. Re-sending a document is
almost never the best answer. Confusion is a comprehension problem, and comprehension is built by
conversation: meet, discuss, confirm understanding, then document what was agreed.
Predictive, adaptive, and hybrid: the same goal, different rhythm
Roughly 60% of the 2026 exam assumes an adaptive or hybrid environment, so know how the same task looks in
each.
Predictive. Vision is captured up front in the charter and scope baseline, then
controlled through change control. Shared understanding is re-confirmed at phase gates and formal reviews.
Adaptive. Vision is captured in a product vision and product goal, and detail emerges.
Understanding is re-built continuously: refinement, planning, daily standup, review, retrospective.
Hybrid. Common on GCHS work. The regulatory and structural scope is baselined
(permits, load paths, funding milestones), while finish selections and non-structural accessibility features
are handled iteratively with the homeowner. The PM must be explicit about which parts are frozen and
which are still open; that boundary itself is part of the shared vision.
Keeping the vision alive on distributed and AI-augmented teams
GCHS runs crews across several counties, a design consultant who works remote, and grant staff in another
office. Distance erodes shared understanding quietly. Countermeasures: a single source of truth everyone can
reach, deliberate overlap hours, video on for anything with disagreement in it, and a written summary of every
verbal decision posted where the whole team can see it.
AI assistants add a newer wrinkle. Teams increasingly use AI to draft scopes, summarize meetings, generate
estimates, or triage inspection photos. Those outputs look authoritative and are not always right. Fold AI use
into the team's ground rules: state where AI-generated content is allowed, require a named human to review it
before it reaches a homeowner or funder, and make sure the vision (not the tool's suggestion) remains the
reference point. An AI meeting summary is an input to shared understanding, never a substitute for confirming it.
Sustainability belongs in the vision when it is real for the project, and on GCHS work it often is:
storm resilience, elevation requirements, envelope and HVAC efficiency that lowers a fixed-income homeowner's
utility bill, and diverting demolition waste from landfill. If a funder's agreement carries ESG or resilience
conditions, those conditions are success criteria, so put them in the vision at kickoff rather than discovering
them at closeout.
Watch for this on the exam
When stakeholders disagree about what the project is for, that is a vision problem, not a scope
change and not a conflict to be arbitrated. The right first move is to bring them together and facilitate a
shared understanding of the objective. Going to the sponsor for a ruling, issuing a change request, or
picking the louder stakeholder's interpretation are all distractors.
Practice Questions
1. At the kickoff for a home elevation project, the project manager finishes presenting the objectives and asks if there are any questions. No one speaks. What should the project manager do NEXT?
Treat the silence as agreement and move to the schedule review
Ask several participants to restate the project objective in their own words
Email the charter to everyone and ask for written confirmation
Ask the sponsor to repeat the objectives with more authority
Answer: b. Silence is not comprehension. Having people paraphrase the objective back exposes mismatched interpretations while they are still cheap to fix. Treating silence as agreement is the classic wrong instinct, and emailing the document again repeats a one-way transmission that already failed to confirm understanding.
2. Which document formally authorizes a project and names the project manager's authority?
Stakeholder register
Team charter
Project charter
Project management plan
Answer: c. The project charter is issued by the sponsor and is the artifact that authorizes the project and grants the PM authority to use resources. The team charter is a different thing entirely; it is written by the team and covers ground rules and working norms, not authorization.
3. A newly formed GCHS rehab team is deciding how it will run meetings, make decisions, and raise disagreements. Who should produce these ground rules?
The PMO, using the organizational template
The project manager, so the rules are consistent across projects
The sponsor, since the sponsor funds the work
The team collectively, facilitated by the project manager
Answer: d. Ground rules that the team creates are ground rules the team enforces. A PM who writes them alone gets compliance at best. The PM's role here is facilitation, not authorship; that is servant leadership in practice.
4. A homeowner, an occupational therapist, and the crew lead each describe the goal of a bathroom modification differently. What should the project manager do FIRST?
Bring the three together to build one agreed definition of the desired outcome
Escalate to the program director for a decision
Proceed with the crew lead's interpretation since they perform the work
Choose the interpretation that fits the current budget
Answer: a. Divergent interpretations of the goal are a shared-understanding problem, and the fix is a facilitated conversation that produces one definition all three recognize. Escalating hands away a problem the PM is equipped to solve, and picking one party's version guarantees rework when the others see the result.
5. In an adaptive project, which artifact defines the shared standard that ANY increment must meet before it can be called complete?
Product vision statement
Scope baseline
Acceptance criteria
Definition of done
Answer: d. The definition of done applies across all work items and is owned by the team. Acceptance criteria are the tempting wrong answer; they are item-specific conditions for one deliverable, not the blanket quality bar.
6. Two weeks into a hybrid accessibility project, crew members are making different assumptions about which parts of the scope are still open to change. What should the project manager do?
Tell the crew to ask the homeowner directly whenever they are unsure about a decision
Add a change control step to every task
Freeze all scope to eliminate the confusion
Clarify which elements are baselined and which are handled iteratively
Answer: d. In a hybrid approach the boundary between the fixed and the evolving parts is itself part of the shared vision and must be stated out loud. Freezing everything discards the flexibility the hybrid approach was chosen for, and sending crew members to the homeowner individually multiplies inconsistent answers.
7. A GCHS program manager wants stakeholders to see, at a glance, what work is planned for this release, what is planned later, and what has been deliberately left out. Which technique should she use?
RACI chart
Team charter
Stakeholder register, updated at each release to show who is affected by each item
Story mapping / release roadmap
Answer: d. Story mapping lays the whole journey out visually so people can see what is in, what is later, and what is out, which is exactly the shared-picture problem described. A RACI clarifies who does the work, not what the work is, and the register tracks people, not scope.
8. An adaptive team has been performing well for months, but two members privately admit they no longer agree on what "done" means for a story. What is the BEST venue for the project manager to surface and resolve this?
The next retrospective
An email restating the definition of done
A change request to the scope baseline
A one-on-one performance review
Answer: a. Adaptive teams re-confirm alignment every iteration, and the retrospective is the standing forum for exactly this kind of drift in shared understanding. An email is one-way transmission, and this is not a scope change, it is a comprehension gap.
9. A GCHS estimator uses an AI tool to draft a scope summary for a homeowner. What must happen before that summary reaches the homeowner or the funder?
The team charter must be updated to mention the tool
A named human reviews and takes accountability for the content
The sponsor must personally approve every AI-assisted document
Nothing, since the tool is generally reliable
Answer: b. AI output is treated as a draft from a fast but inexperienced assistant: a named person must review it and remains accountable before it reaches a homeowner or funder. Skipping review because the tool seems reliable is the trap, and routing every case to the sponsor is unnecessary escalation.
10. On an adaptive GCHS initiative, who should author the product vision statement?
The project management office, from a standard template
The project manager, then distributed for comment
The product owner, together with the team and key stakeholders
The sponsor, alone, before the team is formed
Answer: c. The product vision statement is built by the product owner with the team and key stakeholders, the same collaborative pattern as a team charter. A vision handed down solo by the sponsor or PM is announced, not shared, and will not hold up.
11. A disaster-recovery grant agreement includes resilience and energy-efficiency reporting conditions that were not mentioned at the original kickoff. What should the project manager do?
Treat them as success criteria and fold them into the vision now
Ignore them until the funder specifically asks for a report on resilience or energy use
Wait until project closeout to address them
Reject the grant terms as out of scope
Answer: a. When a funding agreement carries ESG or resilience conditions, those conditions are success criteria and belong in the vision as soon as they are known, not discovered at closeout. Ignoring or rejecting them risks the funding relationship and surprises the team later.
12. A design consultant who works remotely raises a disagreement about a fixture selection over a group text thread. What should the project manager do?
Ask the consultant to put the disagreement in writing instead
Let the thread continue since everyone can read it
Move the discussion to a video call so tone and nuance are not lost
Wait for the next in-person site visit to discuss it, since face-to-face is always better
Answer: c. Distributed teams should use video for anything with disagreement in it, since text loses tone and can let a small disagreement fester. Waiting for an in-person visit delays resolution unnecessarily, and pushing it further into writing removes the interactive element it needs.
13. A user story reads: "As a homeowner using a walker, I need a threshold no higher than half an inch, so that I can cross without lifting." What does the "so that" clause represent?
The definition of done for the increment
The intended benefit, the vision expressed at the scale of one story
A risk statement
The acceptance criteria for the task, written as a testable pass or fail condition
Answer: b. The "so that" clause captures the reason behind the request, the vision in miniature, which is why personas and user stories are listed among the techniques that build shared understanding. It is broader than a single acceptance test and is not the team's blanket quality bar.
14. Which statement correctly contrasts how predictive and adaptive projects capture the vision?
Predictive captures vision in the charter and scope baseline up front; adaptive captures it in a product vision and goal and lets detail emerge
Predictive projects have no vision at all; only adaptive projects do
Adaptive projects fix the vision permanently in the charter at initiation
Predictive and adaptive projects capture vision identically
Answer: a. Predictive work captures the vision up front through the charter and scope baseline and controls it through change control, while adaptive work states a product vision and goal and lets the detail emerge iteratively. Both approaches have a vision; only the rhythm of capturing and re-confirming it differs.
Glossary
Project charter
The document issued by the sponsor that formally authorizes the project and grants the project manager authority to apply resources.
Team charter
Ground rules, values, and working norms built by the team itself, covering meeting conduct, decision-making, and conflict handling.
Product vision statement
A short statement, authored with the product owner, team, and key stakeholders, of who the product is for and why it beats the alternative.
Definition of done
The team's shared checklist that makes any increment genuinely complete, applied across all work items.
Acceptance criteria
The specific, testable conditions that make one particular deliverable acceptable.
SMART objectives
Specific, measurable, achievable, relevant, and time-bound expressions of the project vision.
Information radiator
A visible artifact, such as a task board or burndown chart, that keeps the current picture of work shared without requiring a meeting.
Story mapping
A visual technique that lays out the whole product journey so stakeholders can see what is in, what is later, and what is out.