Reporting project performance

Project iinformation Distribution

 Manage the Project Team

 

We can distinguish the following components of project performance appraisal:

  • identification of the performance areas and of of the the indicators; this is usually done while deciding the methodology during the project detailed planning phase;

  • performance measurement,  (i.e. project monitoring),

  • reporting project performance,

  • project performance management (or Manage CSSQ).

Project monitoring and reporting project performance are tasks pertaining to the project execution and control phase of project management.
 

Reporting the project performance is to review the project progress against expected milestones, timelines and costs.

The purpose of reporting is to share the information required to manage issues and Manage CSSQ (Cost, Scope, Schedule, and Quality).

It is functional to the objective of delivering the project outputs with the expected quality and within the time and cost constrains defined in the project plan document. (see also the project triangle).

 

Reporting project performance is a component of project information distribution and is a specific responsibility of the project manager

The deliverable of project appraisal is the Project Status (or progress) report (see project execution templates).

Guideline: how to report project performance

 

 

Attention: do not confuse project monitoring with project evaluation. 

Project evaluation is not a part of project execution but is a different phase of the programme cycle Project evaluation is not done by the project manager but by the project sponsor (e.g. the Programme Manager, etc.) or by someone supporting her/him. It requires Project Status reports as a fundamental inputs. Its outputs are projects evaluation reports  and  program lessons learned.

 

 

Attention: do not confuse project performance with employee performance!

When monitoring and reporting the project performance you are comparing:

  • what the team  implementing a project plan has achieved (in terms of reaching the expected milestones and deliver the expected project outputs within the decided schedule and budget definitions) and

  • the expected achievements as stated in the project plan document.

When monitoring and reporting the employee performance  you are comparing

  • what the individual employee has achieved and

  • what the individual was supposed to achieve (on the basis of the agreed employee performance objectives.

Reporting project performance is also a component of project information distribution and is also an essential component for the following features of project execution.

Guideline: how to report project performance

 

The monthly reporting method

One simple and popular communications method is called the monthly reporting method: every employee composes an e-mail report, once a month, including information on their activities in the preceding month, their plans for the following month, and any other information deemed relevant to the larger group, bearing in mind length considerations. Reports are sent to managers, who summarize and report to their own managers.

The purpose of the review process is to make sure that all your initial goals were met, and to make sure that no new problems have come up as a result of the solution.

The amount of time spend in review will vary from project to project.

As a rule, it should last as long as it takes to ensure that you are getting consistent results from whatever new process or procedures put in place to solve the original problem.

 

Advantages of gathering project performance data

Regular project performance reporting keeps your stakeholders informed of the progress of the project.

The data that you collect for reporting also alerts you to possible trouble before it derails your project. Reporting your data to the project team helps keep them informed and motivated as well as helping you gain the cooperation and support of management and project owners.

Finally, when you close a project, the data you gathered throughout the process becomes a valuable source of lessons learned that can help you plan for successful future projects.

 

Seven  Areas a Status Report should Track

  • Schedule and scope status

  • Major Issues / Challenges

  • Highlights / Achievements (Quality of interim/final deliverables)

  • Risks (new risks or changes in the risks identified earlier)

  • Spending (versus the planned amounts)

  • Staff effort (versus the planned time)

  • Changes to the plan

 

Templates:

 

 

See other templates in

 

Guidelines 

 

See also

Other resources: