Act Format Prompt: Project Reporting and KPI Systems in

PMBOK v8 Definition

Project reporting is the act of collecting and distributing project information. Project information is distributed to many groups of stakeholders and should be adapted to provide information at an appropriate level, format, and detail for each type of stakeholder. The format may range from a simple communication to more elaborate custom reports and presentations. Information may be prepared regularly or on an exception basis. Key performance indicators (KPIs) can be part of this system.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about communications management, stakeholder engagement, and monitoring/controlling processes. You will encounter questions testing your ability to select the correct report format for different stakeholder needs, understand when to use regular versus exception-based reporting, and identify how KPIs integrate into the project management information system.

Key Points to Remember (for the exam)

• Main Purpose: Collecting and distributing project information to stakeholders at appropriate level, format, and detail
• Format Range: Simple communication → elaborate custom reports → presentations
• Reporting Frequency: Regularly OR on an exception basis (not both simultaneously)
• KPI Integration: Automated gathering and reporting on KPIs can be part of the PMIS
• Work Performance Reports: Include status reports, progress reports, earned value graphs, trend lines, forecasts, iteration burndown charts, defect histograms, contract performance information, and risk summaries
• Report Representations: Dashboards, heat reports, stoplight charts, or other representations useful for promoting awareness and generating decisions/actions
• Common Confusion: Confusing project reporting (output distribution) with work performance data (raw information captured during execution)

Typical PMI Exam Example

A project manager needs to report schedule progress to senior executives who only want to know if the project is on track, behind, or ahead. The most appropriate format is a stoplight chart (red/yellow/green) because it provides information at an appropriate level and detail for executive stakeholders who need quick awareness and decision-making capability.

PMI Exam Traps

• Trap: Confusing project reporting with work performance data

  • Reality: Work performance data is raw information captured during execution; project reporting distributes compiled information to stakeholders

• Trap: Thinking all stakeholders receive the same report

  • Reality: Information must be adapted to provide appropriate level, format, and detail for each type of stakeholder

• Trap: Assuming reporting is always regular/periodic

  • Reality: Information may be prepared regularly OR on an exception basis (triggered by specific events or thresholds)

• Trap: Confusing KPIs with project documents

  • Reality: KPIs are performance indicators that can be part of the PMIS; project documents include change log, issue log, project schedule, scope statement, requirements documentation, risk register, and stakeholder register

Important PMI Connections

Quick Review Questions

1. What are the two possible frequencies for preparing project information in project reporting?

2. Which types of representations can work performance reports use to promote awareness and generate decisions?

3. What is the difference between work performance data and project reporting?

4. Name three examples of project documents that are distinct from project reports.

5. When a project manager uses a dashboard to show earned value information, what type of output is being produced?

PMBOK v8 Reference

Section 2.4 - Project Management Information System (PMIS) and Project Reporting