
Work Performance Information and Change Request Outputs
PMBOK v8 Definition
Work performance information is a key output from the Monitor and Control Project Work process, which belongs to the Monitoring and Controlling Process Group in the Project Integration Management Knowledge Area. It represents analyzed work performance data that provides meaningful insights about project status, progress, and performance against the project management plan. Change requests are formal proposals to modify any document, deliverable, or baseline, and they appear as outputs from multiple processes including Direct and Manage Project Work, Monitor and Control Project Work, and Perform Integrated Change Control.
Why It Matters for the Exam
These concepts appear frequently on the PMI exam because they represent the fundamental flow of project performance measurement and control. Questions test your ability to distinguish between work performance data, work performance information, and work performance reports, as well as identify which processes produce change requests as outputs. Expect situational questions asking what output is generated when a variance is detected or what document is updated after a change is approved.
Key Points to Remember (for the exam)
-
Work Performance Information vs Data: Work performance data is raw observations (output of Direct and Manage Project Work), while work performance information is analyzed data (output of Monitor and Control Project Work). Work performance reports are consolidated summaries (output of Monitor and Control Project Work).
-
Main Outputs of Monitor and Control Project Work: Work performance reports, change requests, project management plan updates (any component), project document updates (cost forecasts, issue log, lessons learned register, risk register, schedule forecasts).
-
Main Outputs of Direct and Manage Project Work: Deliverables, work performance data, issue log, change requests, project management plan updates (any component), project document updates (activity list, assumption log, lessons learned register, requirements documentation, risk register, stakeholder register).
-
Change Request Sources: Change requests appear as outputs from Direct and Manage Project Work, Monitor and Control Project Work, Manage Team, Manage Stakeholder Engagement, and Monitor Risks processes.
-
Project Management Plan Updates: Any component of the project management plan can be updated, including the risk management plan, quality management plan, resource management plan, scope baseline, schedule baseline, and cost baseline.
-
Common Project Document Updates: The assumption log, issue log, lessons learned register, risk register, and risk report are frequently updated across multiple processes.
-
Approved Change Requests: These serve as inputs to Direct and Manage Project Work for implementation and to Monitor and Control Project Work for verification.
Typical PMI Exam Example
During a project status review, the project manager analyzes earned value data and identifies a significant cost variance. The project manager prepares a variance analysis report and recommends corrective action. What is the primary output of this activity? Answer: Work performance reports, with change requests as a secondary output for the corrective action.
PMI Exam Traps
-
Trap: Confusing work performance data with work performance information
-
Reality: Work performance data is raw (output of Direct and Manage Project Work), while work performance information is analyzed (output of Monitor and Control Project Work)
-
Trap: Thinking change requests only come from Monitor and Control Project Work
-
Reality: Change requests are outputs from Direct and Manage Project Work, Monitor and Control Project Work, Manage Team, Manage Stakeholder Engagement, and Monitor Risks
-
Trap: Assuming project management plan updates are limited to specific components
-
Reality: The PMBOK explicitly states "any component" can be updated, including baselines, management plans, and performance measurement baselines
-
Trap: Confusing the issue log with the risk register
-
Reality: The issue log tracks problems that have occurred, while the risk register tracks potential future events. Both are frequently updated documents across processes
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Direct and Manage Project Work | Predecessor process | Produces work performance data and change requests that feed into Monitor and Control Project Work |
| Perform Integrated Change Control | Successor process | Receives change requests from multiple processes; approved change requests are inputs back to Direct and Manage Project Work |
| Monitor Risks | Related process | Also produces change requests and updates risk register, risk report, issue log, and lessons learned register |
| Work Performance Reports | Output relationship | Created from work performance information; used for decision-making and stakeholder communication |
Quick Review Questions
-
What is the difference between work performance data and work performance information in terms of which process produces each?
-
A project manager identifies a risk that requires a change to the cost baseline. Which process produces the change request, and which document is updated?
-
After a change request is approved, which process receives it as an input for implementation?
-
List three project documents that are commonly updated as outputs from both Direct and Manage Project Work and Monitor and Control Project Work.
-
A team member reports a technical issue during a daily coordination meeting. Which output of Direct and Manage Project Work captures this information?
PMBOK v8 Reference
Section 2.6 - Monitor and Control Project Work (Figure 2-9) Section 2.4 - Direct and Manage Project Work (Figure 2-6) Section 2.15 - Monitor Risks (Figure 2-49)