about 3.3% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Governance is the set of rules about who decides what. It is not the work of the project: it is the framework that says which decisions belong to the project manager, which belong to a sponsor, which
belong to a committee, and which belong to the board. On a GCHS accessibility-modification job, governance is
what tells you that you can move a subcontractor from one house to another on your own authority, but you cannot
increase the grant-funded budget for a ramp without going to someone else.
PMI tests this heavily because most wrong answers on the exam are wrong for a governance reason: the project
manager decided something that was not theirs to decide, or escalated something that was.
Decision authority widens at the bottom, where the project manager handles routine calls, and
narrows toward the top, where portfolio governance decides whether the project exists at all. Escalating
past the level that actually owns a decision, or deciding something above your own level, is the error
the exam tests most often.
What a governance framework actually contains
A governance framework is usually documented in the organization's project management methodology, the
project charter, and the project management plan. It defines:
Decision rights and authority thresholds: the dollar amount, schedule slip, or scope
change a PM may approve alone before it must go up. GCHS might set this at, say, a 10% cost variance on a
single unit.
Roles: sponsor, steering committee, PMO, product owner, project manager, functional
managers, and who owns the business case.
Stage or phase gates: defined checkpoints where the project must be reviewed and
formally authorized to continue.
Reporting and escalation paths: what gets reported, to whom, how often, and what
triggers an out-of-cycle escalation.
Standards and controls: required templates, audits, quality gates, procurement rules,
and compliance checkpoints.
Three related terms get confused. Organizational governance is enterprise-wide. Portfolio
governance decides which projects get funded and how they align to strategy. Project
governance is the framework inside a single project. When an exam question asks whether a project should
exist at all, that is a portfolio-level decision: the PM does not make it.
Sponsor, steering committee, and the PM
The sponsor is a single accountable individual who funds the project, owns the business case,
champions it politically, and is the PM's first escalation point. The sponsor signs the charter, which is what
gives the PM authority to spend organizational resources.
A steering committee (sometimes called a project board or governance board) is a group of
senior stakeholders who make decisions that exceed the PM's authority: approving major change requests, resolving
cross-department conflicts, approving phase-gate passage, and deciding whether to continue or terminate. The PM
normally attends, presents data and recommendations, and answers questions, but does not vote on their own
project's major changes.
Key points
On the exam, the PM's job at a governance body is to bring a complete impact analysis and a
recommendation, not to bring a bare problem. An answer that says "escalate the issue to the steering
committee" is usually weaker than "analyze the impact, then present options and a recommendation to the steering
committee." The exception is a genuine compliance, legal, or safety matter, where prompt escalation is itself
the correct first action.
PMO types: supportive, controlling, directive
A project management office (PMO) standardizes project practice. The three classic types
differ by how much control they exert, and the exam tests the difference constantly.
PMO type
Degree of control
What it does
Who manages the project
Supportive
Low
Provides templates, training, lessons learned, coaching, a repository of best practice. Acts as a consultant.
The project manager, with little PMO oversight
Controlling
Moderate
Requires compliance: mandated methodology, templates, governance forms, tool use, and audits to confirm compliance.
The project manager, but must comply with PMO requirements
Directive
High
Takes over management of the projects. Project managers are assigned by and report to the PMO.
A PM supplied by and reporting to the PMO
Two newer forms appear in modern material. An agile center of excellence (or value delivery
office) focuses on coaching, removing organizational impediments, and enabling teams rather than enforcing
documents. An enterprise PMO sits at the strategy level and connects the portfolio to
organizational objectives.
Organizational structure and PM authority
How the company is organized determines how much authority a PM has and whether team members answer to the PM
or to a functional boss. This is a favorite exam table.
Structure
PM authority
PM role
Resource control
Functional (organic)
Little or none
Part-time coordinator or expediter
Functional manager controls the budget and the people
Weak matrix
Low
Part-time; often titled coordinator
Functional manager controls the budget
Balanced matrix
Low to moderate
Full-time PM, shared authority
Mixed: PM and functional manager negotiate
Strong matrix
Moderate to high
Full-time PM, often with a manager of project managers
PM controls most of the budget
Projectized
High to almost total
Full-time PM; team is dedicated
PM controls the budget and the team
In a matrix, the classic problem is two bosses: a crew lead reports to you for the project and
to a functional manager for their day job. When the functional manager pulls the person off, the PMI-correct move
is to talk with the functional manager directly and negotiate, referring to the resource commitments in the
charter or resource management plan, not to complain to the sponsor first, and not to work around them.
Phase gates and other governance checkpoints
A phase gate (stage gate, kill point, gate review) is a scheduled decision point at the end of
a phase. At a gate, leadership compares actual results against the business case and decides one of: continue,
continue with changes, hold, return to a prior phase, or terminate. A gate is a governance decision, not a status
meeting, and yes, "kill the project" is a legitimate outcome even when the work is going well, if the business
case no longer holds.
Related checkpoints include the benefits realization review (did the promised benefit actually
materialize?), quality audits, and procurement gate approvals. For GCHS, a
HUD-funded rehab program has its own gates: environmental review clearance before construction commitment,
inspection sign-offs, and a final draw approval.
Governance in agile and hybrid environments
Agile does not mean no governance. It means governance is lighter, more frequent, and evidence-based.
Instead of a document-heavy gate every six months, an agile environment governs through working product reviewed
at short intervals.
The sprint review is a governance event: stakeholders inspect real increments and
influence what comes next.
The product owner holds decision authority over scope and priority; the team is
self-organizing on how the work gets done.
Scrum of Scrums coordinates dependencies across multiple teams; a representative from each
team raises cross-team impediments.
Definition of done functions as a quality gate applied to every increment rather than once
at the end.
Disciplined agile governance emphasizes lightweight milestones (stakeholder vision,
proven architecture, continued viability, sufficient functionality, production ready, delighted stakeholders)
and choosing the way of working that fits the context.
Hybrid projects often keep formal phase gates for regulated or funded deliverables while
running the build iteratively inside a phase.
Tailoring warning
Tailoring governance means adjusting how much process to apply, based on project size, risk, funding
source, and regulatory exposure. Tailoring never means dropping a control that a law, a contract, or a funding
agreement requires. You can simplify a status report; you cannot simplify a HUD environmental review.
Emerging governance: AI and sustainability oversight
Two new areas now sit inside governance discussions and are fair game on the 2026 exam.
AI governance: organizations increasingly require an approved-use policy for AI tools,
covering which tools may be used, what data may be entered into them, whether AI-generated output must be reviewed by a
human, and how AI use is disclosed. If a team member starts feeding client records into an unapproved AI
assistant, that is a governance and data-privacy matter, not a personal-preference matter.
Sustainability and ESG oversight: many funders and boards now require environmental,
social, and governance reporting. For GCHS this shows up as energy-efficiency standards on rehabs, lead-safe
and asbestos handling, contractor diversity or Section 3 hiring goals, and reporting on those metrics as a
condition of funding.
The governance question to ask in both cases is the same: who approved this, against what standard, and
who is accountable for reporting it?
Practice Questions
1. A project manager is asked whether a proposed project should be funded at all, given three competing initiatives. At which level is that decision made?
Project governance, which sets the PM's authority thresholds
Team governance, which covers how the crew organizes its daily work
Sprint planning, which sequences work for the next iteration
Portfolio governance
Answer: d. Deciding which initiatives get funded and how they align to strategy is portfolio governance. Project governance only frames decisions inside an authorized project: it cannot decide whether the project should exist.
2. Which PMO type assigns project managers to projects and has those PMs report directly to the PMO?
Directive
Controlling
Advisory
Supportive
Answer: a. A directive PMO takes over management of projects and supplies the PM, who reports to the PMO. A controlling PMO mandates compliance with methods and templates but the PM still reports elsewhere.
3. A PMO provides templates, lessons-learned archives, and coaching, but does not require teams to use them. This is which type of PMO?
Controlling
Supportive
Enterprise
Directive
Answer: b. Supportive PMOs act as consultants: low degree of control, resources offered rather than mandated. If compliance were required with audits to verify it, it would be controlling.
4. In a functional organization, who typically controls the project budget?
The functional manager
The project manager
The steering committee chair
The project coordinator
Answer: a. In a functional structure the functional manager controls the budget and the staff; the PM has little or no authority and often works part-time as a coordinator or expediter. Only in strong matrix and projectized structures does the PM control the budget.
5. A project manager has high authority, a full-time dedicated team, and control of the budget. Which organizational structure is this?
Functional
Projectized
Balanced matrix
Weak matrix
Answer: b. Projectized structures give the PM high to near-total authority with a dedicated team. A balanced matrix would give shared authority and shared resource control with functional managers.
6. At the end of a design phase, senior leaders meet to decide whether the project continues, changes, or stops. What is this event called?
Daily standup held to coordinate the next 24 hours of work
Quality audit of process compliance by an independent reviewer
Retrospective held by the team to improve its process
Phase gate review
Answer: d. A phase gate (stage gate or kill point) is a governance decision point comparing results against the business case, with termination as a legitimate outcome. A retrospective is a team improvement event, not an authorization decision.
7. In a balanced matrix, a functional manager pulls a crew member off a GCHS project to cover an urgent departmental need. What should the project manager do?
Escalate straight to the steering committee
Discuss it directly with the functional manager and negotiate, referring to the resource commitments in the charter or resource management plan
Complain to the sponsor immediately without speaking to the functional manager
Have the crew member work unofficial overtime to cover both roles
Answer: b. The classic two-bosses problem in a matrix is resolved by direct negotiation with the functional manager, grounded in the resource commitments already documented in the charter or resource management plan. Going over the functional manager's head first, or working around them informally, skips the level that actually owns the decision.
8. A project manager needs the steering committee to approve a major change. What is the PMI-preferred way to bring it to them?
Avoid the steering committee and decide it unilaterally
Present the bare problem and let the committee work out the options from scratch
Analyze the impact first, then present options and a recommendation
Vote alongside the committee members to speed up the decision
Answer: c. The PM's job at a governance body is to bring a complete impact analysis and a recommendation, not a bare problem; the committee decides, but on information the PM prepared. A genuine compliance, legal, or safety matter is the exception, where prompt escalation itself is the correct first action.
9. What document gives the project manager the authority to spend organizational resources on a project?
The project charter, signed by the sponsor
The business case, which justifies the investment
The project management plan, once the baseline is approved
The resource management plan, which lists team assignments
Answer: a. The sponsor signs the charter, and that signature is what grants the project manager authority to apply organizational resources to the work. The project management plan and resource management plan are developed afterward, under the authority the charter already established.
10. A project manager wants to skip the mandated HUD environmental review to save time, calling it "tailoring the process." Is this acceptable?
Yes, as long as the sponsor informally agrees
Only if the project is already behind schedule
No, tailoring adjusts how much process to apply, but never removes a control required by law, contract, or funding agreement
Yes, tailoring allows dropping any control that seems unnecessary for a small project, because tailoring overrides funder requirements
Answer: c. Tailoring governance means adjusting how much process applies given size, risk, funding source, and regulatory exposure, not dropping a control that a law, contract, or funding agreement requires. A status report can be simplified; a mandated environmental review cannot.
11. In an agile governance model, who holds decision authority over scope and priority, and who decides how the work gets done?
The scrum master decides both scope and method
The steering committee sets sprint priorities directly
Scope authority is shared equally by the whole team with no single owner
The product owner holds authority over scope and priority; the team self-organizes on how the work gets done
Answer: d. The product owner is the named decision authority for scope and priority in agile governance, while the team is self-organizing on the mechanics of doing the work. This is lighter governance, not an absence of governance.
12. A team member begins entering client income and disability records into an unapproved AI assistant to speed up report writing. How should this be treated?
A personal productivity choice with no organizational concern, provided the finished reports are proofread before release
A governance and data-privacy matter, since the tool's vendor terms may retain or train on the submitted data
Acceptable as long as the reports come out faster
A matter for the IT department alone, unrelated to project governance
Answer: b. AI governance requires an approved-use policy covering which tools may be used and what data may enter them, precisely because vendor terms can allow retention or training on submitted content, which can itself be the breach. This is a governance and compliance issue, not a personal workflow preference.
13. How does an agile center of excellence typically differ from an enterprise PMO?
An enterprise PMO coaches teams and removes impediments, while an agile center of excellence sets enterprise strategy
They are identical, interchangeable terms for the same function
An agile center of excellence focuses on coaching and removing organizational impediments, while an enterprise PMO sits at the strategy level connecting the portfolio to organizational objectives
An agile center of excellence assigns project managers and controls budgets, while an enterprise PMO only supplies templates
Answer: c. The agile center of excellence (or value delivery office) enables teams through coaching rather than enforcing documents, while the enterprise PMO connects the portfolio to strategic objectives. Both are newer forms alongside the classic supportive, controlling, and directive PMO types.
14. A funder requires GCHS to report quarterly on Section 3 local-hiring goals for a rehab program. From a governance perspective, what question matters most?
It only matters for publicly traded companies, not nonprofits
It replaces the need for a steering committee on this project
Who approved the requirement, against what standard, and who is accountable for reporting it
This is unrelated to governance and belongs to compliance alone
Answer: c. Funder-required reporting, whether on Section 3 hiring or ESG metrics, sits inside project governance, and the governance question is always the same: who approved this, against what standard, and who is accountable for reporting it. Framing it as purely a compliance checkbox misses that governance assigns the accountability behind the reporting.
Glossary
Governance framework
The documented rules defining who decides what on a project: authority thresholds, roles, gates, and escalation paths.
Sponsor
The single accountable individual who funds the project, owns the business case, and signs the charter.
Steering committee
A group of senior stakeholders who approve decisions beyond the project manager's authority, such as major changes and phase-gate passage.
PMO (project management office)
An organizational structure that standardizes project practice; supportive, controlling, or directive by degree of control.
Phase gate
A scheduled decision point where leadership compares results to the business case and decides to continue, change, hold, or terminate.
Portfolio governance
Enterprise-level decisions about which projects are funded and how they align to strategy.
Tailoring
Adjusting how much process to apply based on project size, risk, and funding, without dropping a legally or contractually required control.
AI governance
Organizational policy on which AI tools may be used, what data may be entered into them, and how AI-generated output is reviewed and disclosed.