Specific Work Performance Metrics Defined at Project Start

PMBOK v8 Definition

Specific work performance metrics for scope, schedule, budget, and quality are defined at the start of the project as part of the project management plan. Performance data is then collected during the project and compared to the plan and other variables to provide a context for work performance. These metrics establish the baseline against which actual performance is measured throughout the project lifecycle, enabling the project team to identify variances and determine if preventive or corrective action is required.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions related to the Measurement performance domain and the overall Performance Management process. You will encounter it in situational questions where the project manager must interpret work performance data against established metrics, and in definitional questions about the components of the project management plan. The exam tests your understanding that metrics are established upfront, not created during execution.

Key Points to Remember (for the exam)

Timing: Metrics are defined at the start of the project as part of the project management plan—not during execution or after work begins.
Four Core Categories: Metrics specifically cover scope, schedule, budget, and quality—these are the four fundamental performance dimensions.
Purpose: Metrics provide the baseline for comparing actual work performance data against the plan to identify variances.
Decision Trigger: Comparing actual data to variance thresholds (also in the project management plan) indicates if preventive or corrective action is required.
Data Hierarchy: Work performance data (raw measurements) → Work performance information (data with context) → Work performance reports (compiled for decisions).
Context Requirement: Raw data alone is insufficient—it must be compared to the budget, work performed, resources used, and funding schedule to be useful.
Continuous Process: Metrics are defined once at the start, but performance data collection and comparison occur throughout the project.

Typical PMI Exam Example

Situation: A project manager is reviewing monthly cost data showing $50,000 expended. The project is behind schedule with only 60% of planned work completed. The project management plan established a cost variance threshold of ±10%.

PMI Exam Question: What should the project manager do FIRST?

Key Insight: The $50,000 alone is raw data. The manager must compare it to the budget, work performed, and funding schedule to determine if the variance exceeds the 10% threshold before deciding on corrective action.

PMI Exam Traps

Trap: Confusing work performance data with work performance information Reality: Data is raw measurements (e.g., $50,000 spent); information is data with context (e.g., $50,000 spent vs. $45,000 budgeted = $5,000 over budget)
Trap: Thinking metrics are created during the Monitoring and Controlling process group Reality: Metrics are defined at the start as part of the project management plan (Planning process group)
Trap: Assuming scope metrics are separate from quality metrics Reality: The Scope performance domain includes quality—quality is defined by meeting stakeholder expectations and fulfilling project and product requirements
Trap: Believing metrics are static once defined Reality: While defined at the start, metrics may be refined through change control; the key exam point is that the initial metrics are part of the project management plan

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Project Management Plan	Contains the metrics	Metrics are defined within the plan, not as a separate document
Variance Analysis	Uses the metrics	Compare actual data to metrics to determine variance magnitude
Preventive/Corrective Action	Triggered by metrics	Variance exceeding thresholds → action required
Work Performance Reports	Output of measurement	Reports compile information from metrics comparison
Scope Performance Domain	Aligned with scope metrics	Scope metrics ensure only required work is performed

Quick Review Questions

When are specific work performance metrics for scope, schedule, budget, and quality defined in the project?
What document contains these defined performance metrics?
What must be added to work performance data to make it useful for decision-making?
What indicates whether preventive or corrective action is required based on performance metrics?
How does the Scope performance domain relate to quality metrics?

PMBOK v8 Reference

Section 2.2 - Scope Performance Domain
Section 2.5 - Measurement Performance Domain
Section 4.6 - Project Management Plan (Performance Measurement Baseline)