---
reference_type: Performance Domain
reference_id: PD8-01
name: Governance
version: "1.0.0"
status: Active
edition: PMBOK8
pmbok8_source: "PMBOK8 Guide §2.1 — Governance Performance Domain"
authority: PMI-derived
file_path: "reference/performance-domains/PD8-01-governance.md"
last_updated: "2026-06-07"
---

# PD8-01 — Governance Performance Domain
**Type:** Performance Domain  
**Edition:** PMBOK 8th Edition (2025)  
**PMBOK 8 Source:** PMBOK8 Guide §2.1 — Governance Performance Domain  
**Version:** 1.0.0  

## Definition
The **Governance Performance Domain** addresses the framework, functions, and processes that guide project management decisions and activities to optimize the project's value delivery (PMBOK8 §2.1). This domain integrates elements of project integration management related to strategic alignment, decision-making, change control, and project success criteria. It coordinates various processes and documents as an integrated system for value delivery.

## Desired Outcomes
Per PMBOK8 §2.1, effective execution of the Governance Performance Domain results in:
- **Strategic alignment** of the project or phase with organizational goals, portfolio priorities, and business strategies.
- **Appropriate decision-making frameworks** tailored to project complexity, protecting project investments and resource allocations.
- **Robust change control mechanisms** that evaluate scope, schedule, and cost impacts against the project's value proposition.
- **Project success criteria** that are defined, measured, and validated throughout the project lifecycle.
- **Effective sourcing strategies** aligned with the project's delivery approach and organizational policies.

## Key Processes and Activities
This domain encompasses the following 9 canonical processes (PMBOK8 §2.1.6):
1. **Initiate Project or Phase** (§2.1.6.1) — Formally authorizes the work, establishes the business case, and identifies initial boundaries.
2. **Integrate and Align Project Plans** (§2.1.6.2) — Consolidated coordination of all sub-plans and baselines into a unified project management plan.
3. **Plan Sourcing Strategy** (§2.1.6.3) — Determines whether to buy, rent, or build resources and details the procurement approach.
4. **Manage Project Execution** (§2.1.6.4) — Directs and carries out the work defined in the plans to achieve deliverables and outcomes.
5. **Manage Quality Assurance** (§2.1.6.5) — Audits quality requirements and the results from quality control measurements to ensure appropriate processes are followed.
6. **Manage Project Knowledge** (§2.1.6.6) — Fosters a learning environment to share and generate knowledge throughout the project.
7. **Monitor and Control Project Performance** (§2.1.6.7) — Tracks, reviews, and regulates project progress against baselines.
8. **Assess and Implement Changes** (§2.1.6.8) — Reviews and decides on change requests, evaluating their impact on value.
9. **Close Project or Phase** (§2.1.6.9) — Finalizes all activities to formally archive data, release resources, and transition benefits.

## Relationship to Principles
| Principle | Connection |
|---|---|
| P8-01 — Holistic View | Governance acts as the integrative system that connects all other domains, ensuring cascading impacts are evaluated systemically (§2.1, §3.3.3). |
| P8-02 — Focus on Value | Governance frameworks protect and maximize value realization, ensuring project decisions are guided by the business case (§2.1.1, §3.4.3). |
| P8-04 — Accountable Leader | Governance formalizes authority boundaries, decision rights, and accountability escalation paths (§2.1.2, §3.6.3). |

## Artifact Connections
| Artifact | Connection |
|---|---|
| A01 — Business Case | The primary strategic justification document detailing value proposition and success criteria. |
| A04 — Project Charter | Authorizes the project manager and defines decision rights and governance boundaries. |
| A14 — Integrated Project Management Plan | Integrates all domain plans and baselines into a single, cohesive operating system. |
| A35 — Governance and Decision Authority Record | Documents the steering committee charters, decision logs, and escalation paths. |

## Skill Connections
| Skill ID | Skill Name | Connection |
|---|---|---|
| SKL-01-01 | Establish Governance Framework | Sets the boundary for decision rights, authority limits, and escalation rules. |
| SKL-02-01 | Develop Project Charter | Formulates and obtains approval for the formal chartering of the project or phase. |
| SKL-05-02 | Manage and Control Changes | Operationalizes the change request, impact assessment, and CCB approval processes. |

## Questions to Ask in Practice
1. Is our governance model "right-sized" to support value delivery without creating unnecessary bureaucracy?
2. Are project decisions and baselines regularly checked against the strategic objectives in the Business Case?
3. Do all team members and stakeholders know the correct escalation path for critical risks or scope changes?
4. Are we capturing lessons learned and project knowledge continuously, or only at project closure?

*Authority: PMBOK8 Guide §2.1 — Governance Performance Domain · Source type: PMI-derived*
*Repository: https://github.com/fakhruldeen/PMOSkills*
