Monthly Project Reporting
- Former user (Deleted)
- Shawn Pappelbaum
The best project status reports create accountability and ownership within your team. They communicate issues, mitigate risks, and most of all – ensure you’re on track towards your project goals.
At a minimum, project record status in ITS-Pro must be updated once a month (on or around 24th of month), as the data from the records are pulled into status reports. If there are significant changes to a project at other times in the month, please make a point to update the ITS-Pro Project (PR) record.
A project status report includes all technical and business-critical efforts, progress and risk associated with a single project. This is a monthly snapshot where the project is at.
Step-by-step guide
Find active project records - Project Record: https://its-pro.ucsd.edu/secure/RapidBoard.jspa?rapidView=141
Utilize quick filters or expand your name in the list to find your projects
Please keep updates at a high level
FIELDS TO UPDATE: Executive Project Update Progress Since Last Month (include “Update for month ending mm/dd/yy:)
Activities for next month (include “Planned for month starting mm/dd/yyyy::) OTL Status Please see project health (RYG) definition below Project Health Schedule Health Resource Health Risk Health
Project Go-Live date and project end date |
|
Review and score your project using the project rubric: https://collab.ucsd.edu/display/PPMO/Project+Rubric
If your project scores low and needs improvement, please do what is necessary to improve the score
Save the monthly rubric in your project’s collab space
RYG Status Definition
Traffic Light | RYG Status Definition | Action |
|---|---|---|
Red | There are significant issues with the project.
The project requires corrective action to meet business objectives. The issue cannot be handled solely by the project manager or project team. One or more aspects of project viability — time, cost, scope — exceed tolerances set by the project board. | The matter should be escalated to the project sponsor and program manager immediately. |
Yellow | A problem has a negative effect on project performance but can be dealt with by the project manager or project delivery team.
Action is taken to resolve the problem or a decision made to watch the situation. One or more aspect of project viability — time, cost, scope — is at risk. However, the deviation from plan is within tolerances assigned to the project manager. | The project governance should be notified using a progress report or scheduled briefing with the sponsor. |
Green | The project is performing to plan.
All aspects of project viability are within tolerance. However, the project may be late or forecast to overspend. | No action needed. |
Related articles