Governance Domain
ECO Domain: Process Domain — Task 1: Develop an integrated PM plan Related principles: Adopt a Holistic View, Focus on Value, Be an Accountable Leader
Definition
Project governance is applicable across all project management approaches, including predictive, adaptive, and hybrid, with variations based on industry, organizational context, and project specifics. Governance consists of the framework, functions, and processes that guide project management decisions and activities to optimize the project’s value delivery. This governance framework is holistic and integrative, considering all other performance domains.
Project governance is shaped by the performing organization’s governance model as well as stakeholders such as customers and regulatory bodies. The Governance performance domain includes elements of project integration management related to strategic alignment, decision-making and change, and project success criteria. It also integrates risk and opportunity management, helping ensure proactive identification and mitigation of potential issues while leveraging opportunities for added value.
Governance can be tailored: lightweight for adaptive methods; moderate or combined for hybrid projects; and comprehensive for large, predictive portfolios, programs, and projects. Feedback loops are incorporated into the governance framework, allowing for periodic reviews, lessons learned, and iterative adjustments.
Key Concepts
Leading Indicators
Leading indicators indicate upcoming changes or reveal trends in the project. If the change or trend is unfavorable, the project team should evaluate the root cause and take corrective actions to address the trend. Leading indicators can be quantifiable (e.g., backlog size, items in progress) or qualitative (e.g., lack of a risk management process, disengaged stakeholders, poorly defined success criteria). Using leading indicators is preferable whenever possible because they can prevent future problems that may require rework.
Lagging Indicators
Lagging indicators measure project deliverables or events after the fact. They reflect past performance and are easier to measure than leading indicators. Examples: number of deliverables completed, schedule or cost variance, amount of resources consumed. Lagging indicators can also reveal correlations between outcomes and environmental variables (e.g., schedule variance correlating with team member dissatisfaction).
SMART Criteria
SMART criteria are guidelines used to set clear, attainable, and meaningful goals: Specific, Measurable, Achievable, Realistic, and Time-bound. These criteria help ensure that objectives are well defined and reachable within a certain timeframe, making them more effective and easier to track. Project metrics should adhere to SMART criteria to be effective.
Sourcing Strategy
Project resources can be insourced, outsourced, or both. A project’s sourcing strategy should consider impacts to schedule, scope, finances, resource capacity, and risks. Key questions: Does organizational culture and proximity favor internal resources? Does the project need specialized skills favoring outsourcing? How does use of external resources affect the overall risk profile and value proposition? Procurement management — selecting, contracting, and supervising vendors — is a complementary discipline to project management.
Project Governance Models
Two primary governance model types:
- Structured governance — often used on predictive projects; composed of executive sponsor, PMO leader, governance board, and project manager providing project-level oversight.
- Self-governance — often used on adaptive projects; project management responsibilities are distributed among the team; requires clear, measurable common objectives, leading indicators, and effective feedback mechanisms to avoid fragmented decision-making.
Metrics and Mechanisms for Effective Governance
Effective governance requires three core components: (1) target metrics clearly aligned to strategic goals; (2) clear signaling mechanisms/alarm systems (typically leading indicators) for those metrics; and (3) effective feedback mechanisms that allow decision-makers to assess, learn, and improve. Key metrics include ROI indicators, due-date performance indicators, and indicators of whether the integrated project baseline carries the highest possible value proposition.
Additional Considerations for Predictive Environments
Predictive environments may call for two additional components:
- Escalation — useful in hierarchical organizations where decision-making includes individuals outside the project team, or where higher-ranking individuals can remove persistent obstacles.
- Investment control — required in environments calling for formal stewardship of project investment funding (public corporations, government agencies, financial entities). Frequently includes thorough risk evaluation to analyze possible returns and reduce potential risks.
Processes
Initiate Project or Phase
Officially authorizes the start of a project by creating a project charter or similar document that establishes a link between the project, the business case, and the organization’s strategic goals.
| Field | Detail |
|---|---|
| Key inputs | Business Case, Benefits Management Plan, agreements, EEFs, OPAs |
| Key tools | Expert judgment, data gathering (brainstorming, focus groups, interviews), interpersonal & team skills (conflict management, facilitation, meeting management), meetings, responsibility assignment matrix, project canvas |
| Key outputs | Project charter, assumption log |
Integrate and Align Project Plans
Consolidates and aligns all performance domain plan components into a unified project management plan that details how the project will be executed, monitored and controlled, and closed.
| Field | Detail |
|---|---|
| Key inputs | Project charter, outputs from other processes, EEFs, OPAs |
| Key tools | Expert judgment, data gathering (brainstorming, checklists, focus groups, interviews), interpersonal & team skills, meetings, project canvas |
| Key outputs | Project management plan (including Change Management Plan, configuration management plan, development approach, and life cycle) |
Plan Sourcing Strategy
Documents project sourcing decisions, specifies the source selection approach, determines the scope of work for external sourcing, and selects appropriate contracts. Establishes source selection criteria (cost, technical capability, past performance, financial stability, compliance, alignment with organizational values).
| Field | Detail |
|---|---|
| Key inputs | Project charter, project management plan (scope, quality, schedule, financial, resource management plans), project documents (requirements docs, Risk Register, stakeholder register), EEFs, OPAs |
| Key tools | Expert judgment, market research, make-or-buy analysis, source selection analysis, document analysis |
| Key outputs | Sourcing strategy plan (insourcing/outsourcing decisions, source selection criteria) |
Manage Project Execution
Leads and performs the work defined in the project management plan and implements approved changes to meet project objectives. Includes allocating resources, managing their efficient use, and implementing corrective actions, preventive actions, and defect remediation.
| Field | Detail |
|---|---|
| Key inputs | Project management plan (any component), project documents (change log, lessons learned register, schedule, risk register), approved change requests, EEFs, OPAs |
| Key tools | Expert judgment, project management information system (PMIS), meetings (daily coordination) |
| Key outputs | Deliverables, work performance data, issue log, change requests, project management plan updates, project document updates (activity list, assumption log, lessons learned register, requirements documentation, risk register, stakeholder register) |
Manage Quality Assurance
Ensures project processes are performed in a manner consistent with stakeholder expectations. Implements planned and systematic activities defined in the quality management plan. Distinction: quality assurance = process effectiveness (audits, compliance); quality control = deliverable conformance (testing, defects).
| Field | Detail |
|---|---|
| Key inputs | Project management plan, all project documents, OPAs (policies, procedures, regulations) |
| Key tools | Audits, checklists, data representation (affinity diagrams, cause-and-effect diagrams, flowcharts), decision-making, problem-solving, process improvement |
| Key outputs | Quality reports, change requests, project management plan updates, project document updates |
Manage Project Knowledge
Uses existing knowledge and creates new knowledge to achieve project objectives and contribute to organizational learning. Manages both explicit knowledge (codifiable: manuals, procedures, documented processes) and tacit knowledge (personal, experience-based, difficult to articulate and transfer).
| Field | Detail |
|---|---|
| Key inputs | Project management plan (all components), project documents (lessons learned register, team assignments, stakeholder register), deliverables, EEFs, OPAs |
| Key tools | Knowledge management, information management, after-action reviews, in-progress postmortems, storytelling, Retrospectives, interpersonal & team skills (active listening, facilitation, leadership, networking, political awareness) |
| Key outputs | Lessons learned register, project management plan updates (any component), OPA updates |
Monitor and Control Project Performance
Tracks, reviews, and reports overall project progress to meet performance objectives defined in the project management plan. Involves collecting and analyzing leading and lagging indicators, identifying potential problems early, and taking corrective or preventive action.
| Field | Detail |
|---|---|
| Key inputs | Project management plan (any component), project documents (assumption log, basis of estimates, cost/schedule forecasts, issue log, quality reports, risk register/report), work performance information, agreements, EEFs, OPAs |
| Key tools | Expert judgment, data analysis (Earned Value Management (EVM), root cause analysis, trend analysis, variance analysis), decision-making, project dashboards, visual controls, information radiators |
| Key outputs | Work performance reports, change requests, project management plan updates (any component), project document updates (cost/schedule forecasts, issue log, lessons learned register, risk register) |
Assess and Implement Changes
Manages project changes from project start through completion. Uses integrated change control (predictive) or backlog management (adaptive). A Change Control Board (CCB) may review, evaluate, approve, defer, or reject changes. Approved change requests may require new cost estimates, schedule adjustments, resource requirements, and risk assessments.
| Field | Detail |
|---|---|
| Key inputs | Work performance reports, change requests, project management plan, EEFs, OPAs |
| Key tools | Expert judgment, change control tools, data analysis (alternative analysis, cost-benefit analysis), decision-making (voting, autocratic, multicriteria), meetings, integrated change control, Backlog Management |
| Key outputs | Approved change requests, project management plan updates (change mgmt plan, config mgmt plan, scope/schedule/cost baselines), project document updates (change log, requirements traceability matrix, risk report) |
Close Project or Phase
Finalizes all activities related to the project or phase — archiving knowledge, completing planned work, and releasing resources. Confirms the extent to which value or capability to deliver value has been achieved. Includes satisfying exit criteria, contractual agreement completion, collecting and auditing records, and managing knowledge transfer.
| Field | Detail |
|---|---|
| Key inputs | Project charter, project management plan (all components), all project documents, accepted deliverables, Business Case, Benefits Management Plan, agreements, procurement documentation, OPAs |
| Key tools | Expert judgment, data analysis (document analysis, regression analysis, trend analysis, variance analysis), meetings |
| Key outputs | Project document updates (lessons learned register), final product/service/result transition, final report, OPA updates |
Tailoring Considerations
- Organizational governance — Governance should be understood from the perspective of other functions and projects within the larger organization. Identify control boards, committees, and stakeholders that are part of the project; define project status reporting requirements.
- Guided self-governance — Agile/adaptive projects are designed to be self-governing with autonomy, light governance, and clear boundaries/guardrails. Daily coordination meetings serve as a self-governing mechanism. Adaptive teams leverage iterative planning and collaborative decision-making.
- Project life cycle adaptations — Tailoring is a continuous and iterative process adapting approach, governance, and processes for predictive, adaptive, or hybrid life cycles. Use “just enough” processes, methods, templates, and artifacts. Factors: business environment, regulatory requirements, innovation need, market conditions, team size, uncertainty, project complexity.
Worked examples from PMBOK8:
Example 1 — Small organization without PMO: The project manager makes governance decisions with other key leaders, focusing on maximum value delivery without the overhead of a formal PMO structure.
Example 2 — Rapid innovation project: A self-governing approach is adopted with no external governance body; the team manages all value delivery, outputs, quality, etc., through typical agile processes.
Example 3 — Large multinational: Governance must integrate across domains to ensure compliance with regulations across agencies and countries; some multinational compliance may require program- or portfolio-level governance with regional variations.
Domain Interactions
The Governance performance domain is interrelated with all other project management performance domains, ensuring alignment of project scope, schedule, and financial resources to maximize value delivery while balancing trade-offs.
| Direction | Domain | Nature of interaction |
|---|---|---|
| Governance ↔ | Scope Domain | Most important interaction — scope is where core value lies; governance decisions determine the formality of scope control (extensive formal controls vs. informal) |
| Governance ↔ | Schedule Domain | Value proposition is often time-sensitive; well-applied governance may increase speed and effectiveness; poorly applied governance slows execution |
| Governance ↔ | Finance Domain | All projects are investments; governance impacts cost overruns/underruns; budget decisions require governance approval; cost baseline changes need CCB |
| Governance ↔ | Stakeholders Domain | Well-applied governance ensures stakeholders are engaged at the right time; stakeholder vantage points inform governance decisions |
| Governance ↔ | Resources Domain | Project work is heavily dependent on right resources allocated to right priorities at right times; resource allocation decisions flow through governance |
| Governance ↔ | Risk Domain | All projects have inherent risks; risk mitigation/opportunity seizing should align with strategic objectives under clear governance; risk mitigation may incur additional expenditures but can enhance safety, compliance, and risk-adjusted ROI |
Check Outcomes
Table 2-5 from PMBOK8 §2.1.9:
| Outcome | How to check |
|---|---|
| Projects have an appropriate level of oversight by leadership and third-party stakeholders | Confirm agreed-upon processes, protocols, team agreements, or other governance forms are documented and aligned with organizational governance artifacts (policies, standards, procedures) |
| Project governance processes are in place, effective, and continuously improved throughout the project | Verify teams have awareness of governance structure, internal/external auditing/compliance, and customer governance requirements; governance of interactions integrates organizational and third-party governance |
| Effective signaling mechanisms tied to target project outcomes are in place | Use compliance audits or checklists (predictive); governance checklist used regularly, timeboxing in place, meetings held (adaptive); select signaling mechanisms aligned to maximizing value proposition |
| Lessons learned / retrospectives are managed throughout the project | Confirm project and organizational knowledge/learning are combined to manage deliverables and value; lessons learned incorporated during ongoing processes, not only at project end |
| Key management members are kept apprised of the project | Verify project metrics tracked regularly; teams focus on: operational status, resource requirements, known risks & response plans, assumptions, benefits realized, decision criteria, change control, compliance, communications, issues, and financial performance |
Exam angle
- Structured vs. self-governance trap: A team making all governance decisions internally is valid self-governance for adaptive projects, not a governance failure — wrong answers escalate to a PMO that doesn’t exist or require formal CCB in an agile context
- Lagging vs. leading indicators: Schedule variance (CPI, SPI) are lagging — useful but reactive; leading indicators (backlog size, stakeholder engagement level, undefined success criteria) are preferred because they prevent problems before tolerance thresholds are crossed
- CCB authority in predictive projects: Changes impacting a baseline require CCB review; CCB approves, defers, or rejects — PM does not unilaterally approve baseline changes; sponsor/customer approval may be required after CCB approval unless they are CCB members
- Adaptive change management: In adaptive approaches, changes go to the backlog — there is no formal approval process; lower priority = deferred; removed from backlog = rejected; wrong answers apply formal change request language to agile contexts
- Measurement pitfalls: Hawthorne effect (measuring behavior changes it), vanity metrics, demoralization from unachievable goals, confirmation bias — exam scenarios test whether PM focuses on actionable SMART metrics rather than gaming the numbers
- Knowledge management nuance: Tacit knowledge (experience, intuition) cannot be captured in a lessons learned register alone — wrong answers assume all knowledge transfer is document-based; correct answers include mentoring, retrospectives, collaborative environments