A key characteristic of a good report is that it contains just the right amount of information–not too much, and not too little. However, what is “just right” depends on the context. This status report has an interface to select the right information and configure the content, depending on the audience for the report.
Use the graphics on this page to explore examples of the flexibility of the RPM ENG348 Status Report for updating status to different users. Each organization or project might have different reporting requirements.
For 1st or 2nd-Line Delivery Manager
Information need:For 3rd-line Portfolio Manager
Information need:
High-level summary only, with enough detail to flag if there is a need for more detailed information.
Report suggestions:
Configure the content as one-line displays for all information and focus on critical issues, changes, risks, and actions. Do not include details on defects.
For Client
Information need:
Financial, milestone, and deliverables status.
Report suggestions:
Configure the content to identify milestones, financials revenue only (no costs), and deliverables (no work products). Include any critical issues, changes, risks, and actions.
For Project Team (Team Leaders)
Information need:
Entire set of project information.
Report suggestions:
The Project status report can be used for recording complete “point in time” information about the overall state of the project.
