Overview
Governance has five tasks. You define and establish a governance model with its structure, such as a governance board or steering committee, its policies, and the roles, rights and authorities for decisions. You set portfolio management standards, protocols, rules and best practices, define or modify portfolio processes such as benefits realization, performance, risk, resource and change management, create the portfolio management plan, and make recommendations and obtain approval for portfolio decisions.
The domain exists because a portfolio crosses departmental lines, so no single manager has natural authority over it. Governance supplies that authority in a documented form. Strategic Alignment produces recommendations that need a decision maker, Portfolio Performance needs escalation paths and thresholds, Portfolio Risk Management needs risk tolerances, and Communications Management needs approved communication procedures. All of them are defined here.
How it's tested
Questions present a decision that needs to be made, or a breakdown such as conflicting approvals, unclear authority or inconsistent practices, and ask what the portfolio manager should do or which governance element is missing. Expect BEST and MOST appropriate wording, and options that differ mainly in who decides and through which documented path.
-
Who holds the decision
A decision about components, budget or roadmap is pending. The right answer routes it through the decision makers defined in the governance model, at the authority level the plan sets.
-
Missing governance element
Teams apply rules inconsistently or approvals conflict. You trace the problem back to an undefined standard, process, threshold or role and fix that element.
-
Within or above threshold
A variance or change is described with numbers. You compare it to the governance thresholds in the plan to decide whether the portfolio manager acts or escalates.
Two business units each received approval from their own vice president to start overlapping components, and both now claim the same specialists. Options include ranking them yourself, escalating to the CEO, or letting the units negotiate. The pattern points to a governance gap: approvals happened outside the portfolio governance body. The best answer brings both decisions to that body and clarifies decision rights so future approvals follow one path.
Tasks 5
Official tasks from the PMI outline, in outline order.
2.1 Define and establish a governance modelStructure, policies, and who holds which decision rights.
- What it means
- You design the portfolio governance structure, such as a governance board, steering committee or investment committee, along with policies and the roles, responsibilities, rights and authorities for each kind of decision.
- What to understand
- The model answers who decides, on what, at what level and through which forum. It must fit the organization's structure and be agreed by executives, or decisions will keep bypassing it.
- How it shows up
- Departments approve their own initiatives without portfolio review; the fix is establishing a governance model with clear decision rights, not ranking the work yourself.
- Common confusion
- Treating the PMO as the governance body; a PMO supports and administers governance but decision rights usually sit with a board or committee.
2.2 Determine portfolio management standards, protocols, rules, and best practicesSet the consistent rules every component follows.
- What it means
- Using organizational assets such as information systems and subject matter experts, and industry standards, you define the standards, protocols and rules for how portfolio work is proposed, assessed, reported and reviewed.
- What to understand
- Consistency is the goal: without common templates, reporting rules and definitions, component data cannot be compared or aggregated. Standards are tailored from industry practice, not copied wholesale.
- How it shows up
- Component status reports use different definitions of on track, so roll-up reporting is meaningless; the expected fix is a portfolio reporting standard.
- Common confusion
- Expecting each program or project to choose its own reporting rules, which defeats portfolio-level comparison.
2.3 Define and/or modify portfolio processes and proceduresDesign the processes that run the portfolio.
- What it means
- You define or adjust portfolio processes such as benefits realization planning, information management, performance, communication, risk, stakeholder engagement, resource and change management.
- What to understand
- Processes are improved over time from performance data and lessons learned. When a recurring problem appears, the governance-level fix is often to modify a process, not to handle each case manually.
- How it shows up
- The same resource conflict recurs every quarter; the best response is to modify the resource management process rather than resolve each conflict one at a time.
- Common confusion
- Treating a process change as a one-off decision; process changes are themselves governed and documented.
2.4 Create the portfolio management planDocument how the portfolio will be managed.
- What it means
- The portfolio management plan records roles and responsibilities, the governance model, escalation paths, risk tolerances, governance thresholds, change control, key performance indicators (KPIs), the prioritization model and communication procedures.
- What to understand
- The plan is the reference when anyone asks who decides or what happens when a limit is crossed. It defines the method, while the roadmap and component list describe the content.
- How it shows up
- A component manager is unsure whether a 6% cost overrun needs board approval; the portfolio management plan's thresholds and escalation rules answer it.
- Common confusion
- Confusing the portfolio management plan with the portfolio roadmap or the portfolio strategic plan.
2.5 Make recommendations and obtain approval regarding portfolio decisionsTurn analysis into authorized decisions.
- What it means
- You present recommendations on components, plans, budget and the roadmap to the decision makers defined in the governance model and obtain their approval before execution.
- What to understand
- Approval is what authorizes execution. Good recommendations show options, trade-offs, risks and alignment so the body can decide quickly; decisions and rationale are then recorded.
- How it shows up
- The portfolio manager has a strong case to reallocate funds; the right step is to obtain approval through the governance body before moving any money.
- Common confusion
- Assuming informal agreement from a senior sponsor substitutes for approval by the defined governance body.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Portfolio governance
The framework of structures, policies, roles and decision rights that directs and oversees portfolio investment decisions so they serve the organization's strategy.
- Remember
- Governance decides and oversees; management executes within the limits governance sets.
- Tested as
- Many stems hinge on whether an action belongs to the governance body or the portfolio manager.
- Trap
- Treating governance as paperwork rather than as the source of authority for decisions.
-
Governance model
The documented design of governance bodies, membership, meeting cadence, policies and decision rights for each category of decision.
- Remember
- Without defined decision rights, approvals happen informally and conflict across units.
- Tested as
- Expected answer when departments approve overlapping work independently.
- Trap
- Escalating each conflict to an executive instead of fixing the model that let it happen.
-
Decision rights
The specific authority assigned to a role or body to make a defined type of decision, for example approving components above a cost limit.
- Remember
- Decision rights are tied to thresholds: the same type of change may be decided at different levels depending on size.
- Tested as
- Options often differ only in who makes the decision.
- Trap
- Choosing the most senior person as decision maker regardless of what the governance model assigns.
-
Governance thresholds
Numeric limits in the portfolio management plan, such as cost or schedule variance, beyond which a decision or issue must move to a higher authority.
- Remember
- Within threshold, the portfolio manager acts; beyond it, escalate through the defined path.
- Tested as
- Numeric stems compare a variance to a stated threshold.
- Trap
- Escalating small variances that the plan already authorizes the portfolio manager to handle.
-
Portfolio management plan
The document that specifies how the portfolio will be managed: roles, governance model, escalation, risk tolerances, thresholds, change control, KPIs, prioritization model and communication procedures.
- Remember
- It is the method; the roadmap and the component list are the content.
- Tested as
- Root-cause stems trace inconsistent decisions to a missing plan element.
- Trap
- Looking for component schedules or detailed risk entries in it.
-
Portfolio governance board
A decision-making body, often of senior executives, that approves portfolio composition, funding and major changes based on the portfolio manager's recommendations.
- Remember
- The board decides; the portfolio manager prepares analysis and recommendations for it.
- Tested as
- Appears as the correct destination for decisions beyond the portfolio manager's authority.
- Trap
- Assuming the board manages day-to-day component issues.
-
Portfolio management office (PMO) role
A function that supports governance by maintaining standards, data, tools and reporting, and sometimes coordinating the governance cycle.
- Remember
- A PMO can support or administer governance without holding the decision rights itself.
- Tested as
- Distractors give the PMO authority to approve or cancel components.
- Trap
- Equating the PMO with the governance board.
-
Change control at portfolio level
The governed process for evaluating and approving changes to portfolio composition, funding or roadmap, as defined in the portfolio management plan.
- Remember
- Changes are assessed for strategic impact, then decided at the authority level the thresholds require.
- Tested as
- Tested when a sponsor wants to add or reprioritize work outside the normal cycle.
- Trap
- Accepting a change because a senior sponsor requested it, without impact assessment.
-
Key performance indicators (KPIs)
The measures defined in the plan, such as strategic contribution, benefits realized, resource utilization or cost variance, used to judge portfolio health.
- Remember
- KPIs are chosen during governance so that Portfolio Performance measures the same things every cycle.
- Tested as
- Appears when reporting is inconsistent or does not show strategic progress.
- Trap
- Choosing only component delivery metrics such as on-time percentage, which say nothing about strategic value.
-
Benefits realization planning
A portfolio process that defines how benefits will be identified, measured, tracked and attributed after components deliver.
- Remember
- The ECO lists it among the processes governance defines, so benefits are planned before delivery, not after.
- Tested as
- Stems where nobody can show whether completed work delivered value point to a missing benefits process.
- Trap
- Assuming benefits are measured automatically when a project closes.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Governance vs. portfolio management
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Portfolio governance | Directing and overseeing portfolio decisions | Holds decision rights; approves composition, funding and major change | Expecting it to manage day-to-day issues |
| Portfolio management | Running the portfolio processes within governance limits | Analyzes, recommends, monitors and acts within thresholds | Making decisions reserved for governance |
Portfolio management plan vs. portfolio roadmap vs. portfolio strategic plan
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Portfolio strategic plan | How the portfolio will support strategic objectives | States the why and the strategic intent | Using it for escalation or threshold questions |
| Portfolio management plan | How the portfolio will be managed and governed | Roles, thresholds, escalation, change control, KPIs | Expecting it to sequence components over time |
| Portfolio roadmap | High-level sequence of components over time | Shows timing and dependencies | Looking in it for decision rights |
Governance board vs. PMO
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Governance board | Executive body that decides on portfolio matters | Holds approval authority | Bringing it issues the plan lets the portfolio manager resolve |
| PMO | Function that supports standards, data and reporting | Supports governance; authority depends on its mandate | Assuming it can approve or cancel components by default |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Decisive unilateral action
- What candidates pick
- Reallocate funding or cancel a component directly because the data supports it.
- Why it looks right
- It looks efficient and evidence-based.
- Why it's wrong
- Composition and funding decisions belong to the decision makers in the governance model; the portfolio manager recommends and obtains approval.
Clue to watch for The decision affects budget, components or the roadmap, and an option mentions the governance board or steering committee.
-
Escalate everything
- What candidates pick
- Send every variance or conflict to executives.
- Why it looks right
- Escalation feels safe and respectful of authority.
- Why it's wrong
- Governance thresholds exist so small matters are handled at the right level; over-escalation clogs the governance body and slows decisions.
Clue to watch for The stem gives a variance that is inside the threshold stated in the portfolio management plan.
-
Senior sponsor equals approval
- What candidates pick
- Proceed because a senior vice president verbally approved the change.
- Why it looks right
- Seniority looks like authority.
- Why it's wrong
- Only the body defined in the governance model holds the decision right; informal approvals create conflicting commitments.
Clue to watch for The approval came from an individual outside the defined decision path.
-
Fix the case, not the process
- What candidates pick
- Resolve each recurring conflict manually as it arises.
- Why it looks right
- It solves the immediate problem quickly.
- Why it's wrong
- A recurring problem signals a missing or weak standard or process, which task 2.3 expects you to define or modify.
Clue to watch for Words such as again, every quarter or repeatedly in the stem.
-
PMO decides
- What candidates pick
- Ask the PMO to approve or reject the proposed component.
- Why it looks right
- The PMO owns the portfolio process and data.
- Why it's wrong
- Unless its mandate says so, a PMO supports governance with standards and reporting; approval sits with the governance body.
Clue to watch for The stem names both a PMO and a governance board or investment committee.
-
Copying a standard wholesale
- What candidates pick
- Adopt an industry framework unchanged as the portfolio standard.
- Why it looks right
- Industry standards are authoritative and ready to use.
- Why it's wrong
- The ECO expects standards built from organizational assets and industry practice together; an untailored framework often clashes with existing structures and is ignored.
Clue to watch for The stem stresses organizational culture, existing systems or resistance to new rules.
Answer framework
When a Governance scenario asks what to do, work out where the decision belongs before choosing any action.
- Identify the decision or breakdown in the stem: a pending approval, conflicting authority, inconsistent practice or a recurring problem.
- Check the governance model and portfolio management plan for who holds that decision right and at what threshold.
- If the matter is within your documented authority, act and record it; if it exceeds a threshold, escalate through the defined path.
- If the governing element is missing or unclear, define or modify the model, standard, process or plan section rather than resolving each case by hand.
- Present recommendations with options, trade-offs and alignment evidence, obtain formal approval from the defined body, and record the decision and rationale.
Practice question
Want more like this? The PfMP practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the governance model, because every other task in this domain assumes you know who decides. Draw a simple model for an organization you know: the bodies, their members, the decisions each one makes and the thresholds that move a decision up a level. Then list what a portfolio management plan would need to contain to make that model work day to day.
The highest-priority concepts are decision rights, governance thresholds and the difference between recommending and approving. Practice with numeric stems: given a stated threshold, decide whether to act or escalate. Most errors in this domain come from ignoring a threshold the stem quietly provides.
Candidates commonly underestimate tasks 2.2 and 2.3 because standards and processes sound administrative. Expect stems where reporting cannot be rolled up or the same conflict keeps recurring, and the answer is a standard or process change rather than another manual fix.
Afterwards, move to Portfolio Performance, which applies the escalation paths, KPIs and change control defined here, then revisit Strategic Alignment to connect recommendations with the approval step. Finish with mixed sets where the only difference between options is who makes the decision.
FAQ
How much of the PfMP exam is Governance?
PMI weights Governance at 20% of the exam, across five tasks. PMI does not publish a fixed number of questions per domain.
What is the difference between governance and portfolio management?
Governance holds decision rights and oversees the portfolio. Portfolio management runs the processes, analyzes, recommends and acts within the limits governance sets.
What goes into the portfolio management plan?
The ECO lists roles and responsibilities, the governance model, escalation, risk tolerances, governance thresholds, change control, KPIs, the prioritization model and communication procedures, among other content.
Is the PMO the governance body?
Not by default. A PMO usually supports governance through standards, data and reporting; approval authority sits with the governance body unless the PMO's mandate explicitly grants it.
What question style does this domain use?
Situational questions where options differ in who decides or which documented path is followed. Many give a threshold and a variance and test whether you act or escalate.
How long should I study this domain?
Our planning estimate is about 20 to 30 hours, based on its 20% weight and a 120-hour overall plan. Add time if you have not worked under a formal investment or portfolio board.
How does Governance connect to the other domains?
It approves what Strategic Alignment recommends, sets the escalation and change rules Portfolio Performance follows, defines the risk tolerances and reserve approval for Portfolio Risk Management, and sets communication procedures.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- CompTIA Project+ Same subject: Domain 4: Basics of IT and Governance (18%)
- Program Management Professional Same subject: Domain 5: Governance (14%)
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- PRINCE2 7 Foundation Study guide
- Certified Associate in Project Management Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 2 knowledge
You have worked through governance models, decision rights, standards, the portfolio management plan and the approval path. Check whether you can tell when to act within thresholds and when to escalate.