Table Performance Check: Governance, Scope, Schedule, and Finance Domains
PMBOK v8 Definition
The Table Performance Check refers to the systematic verification of target outcomes across project performance domains, as documented in PMBOK v8's check results tables (Tables 2-5 through 2-11). Each performance domain—Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk—includes a dedicated check table showing sample target outcomes and potential checks to confirm whether those outcomes are met. These tables provide a structured mechanism for evaluating project health and ensuring alignment with governance expectations.
Why It Matters for the Exam
PMI exam questions frequently test your ability to identify which check outcomes belong to which performance domain. Expect scenario-based questions where you must determine whether a specific outcome check relates to Governance, Scope, Schedule, or Finance. The exam also tests your understanding that Scope, Schedule, and Finance are "closely linked" and changes in any one will likely impact the others.
Key Points to Remember (for the exam)
- Governance Domain (Table 2-5): Focuses on "delicate balance" tailored to industry, organizational structure, and project context. Governance interactions involve executives, PMO leaders, agile practitioners, and project team members.
- Scope Domain (Table 2-6): Directly linked to Schedule and Finance—changes in one impact the others. Scope outcomes must be verified against project charter and scope statement elements.
- Schedule Domain (Table 2-7): Activities are successful only if they contribute to specific outcomes. Schedule performance is inseparable from Scope and Finance considerations.
- Finance Domain (Table 2-8): Financial outcomes must be checked for alignment with scope delivery and schedule performance. Budget variances directly affect project governance.
- Stakeholders Domain (Table 2-9): Operates "in parallel to" and "indirectly connected with" Scope, Schedule, and Finance domains.
- Resources Domain (Table 2-10): Resource allocation decisions must balance against scope, schedule, and financial constraints.
- Risk Domain (Table 2-11): Risk responses must be evaluated for their impact on the three closely linked domains.
Typical PMI Exam Example
A project manager reviews the Schedule Performance Domain check outcomes (Table 2-7) and notices that schedule variances exceed the threshold. According to PMBOK v8, what is the immediate implication? The project manager must assess how these schedule changes will impact the Scope and Finance performance domains, as they are "closely linked to one another" and changes in any one will likely impact the others.
PMI Exam Traps
-
Trap: Confusing Governance check outcomes with Scope check outcomes Reality: Governance (Table 2-5) focuses on "tailoring to industry and organizational structure"; Scope (Table 2-6) focuses on deliverable verification and scope baseline adherence
-
Trap: Treating performance domains as independent silos Reality: Scope, Schedule, and Finance are "closely linked"; changes in one domain require immediate evaluation of the other two
-
Trap: Assuming all stakeholders participate equally in governance checks Reality: Governance approaches should be contemplated by "various stakeholders (from executives to PMO leaders as well as agile practitioners to other project team members)"—different roles have different involvement levels
-
Trap: Thinking schedule success is measured by activity completion alone Reality: Schedule performance domain activities are "considered successful only if they contribute to specific outcomes"—outcomes, not activities, define success
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Governance Performance Domain | Overarching framework | Governs all other domains; Table 2-4 addresses interactions with Scope, Schedule, and Finance "first and foremost" |
| Project Charter & Scope Statement | Input to check tables | Table 4-1 lists elements of both documents; used to verify scope outcomes |
| Tailoring (Table 3-1) | Application context | Governance approaches require "delicate balance tailored to industry, organizational structure, and specific project context" |
| Insourcing vs. Outsourcing (Table 2-3) | Governance decision | Advantages comparison directly impacts how governance checks are implemented |
Quick Review Questions
-
According to PMBOK v8, which three performance domains are described as "closely linked to one another" such that changes in any one will likely impact the others?
-
What is the primary focus of Table 2-5 (Check Outcomes—Governance Performance Domain), and who should be involved in contemplating governance approaches?
-
How does the Schedule Performance Domain (Table 2-7) define success for its activities?
-
A project experiences a significant scope change. According to the PMBOK v8 check outcomes framework, which performance domains must be immediately evaluated?
-
What distinguishes Governance performance domain check outcomes from Scope performance domain check outcomes?
PMBOK v8 Reference
Section 2.1.9 - Check Results (Governance Performance Domain) Section 2.3.5 - Check Results (Schedule Performance Domain) Table 2-4 - Governance Interactions With Other Performance Domains Table 2-5 - Check Outcomes—Governance Performance Domain Table 2-6 - Check Outcomes—Scope Performance Domain Table 2-7 - Check Outcomes—Schedule Performance Domain Table 2-8 - Check Outcomes—Finance Performance Domain Table 2-9 - Check Outcomes—Stakeholders Performance Domain Table 2-10 - Check Outcomes—Resources Performance Domain Table 2-11 - Check Outcomes—Risk Performance Domain