Introduction |
|---|
| Performance reporting involves
collecting and disseminating project performance
information in order to provide stakeholders with
information about how resouces are being used to achieve
project objectives. This includes:
|
10.3.1 Inputs |
|---|
|
|
|
|
The project plan contains the various baselines that will be used to assess project performance.
Work results - which deliverables have been fully or partially completed, what costs have been incurred, or committed, etc. - are an output of project plan execution. Accurate, uniform information on work results is essential to useful performance reporting.
In addition to the project plan and the project's work results, other project documents often contain information that should be considered when assessing project performance.
Performance reviews are meetings held to assess project status or progress and are used in conjunction with one or more performance reporting tools and techniques.
This involves comparing actual project results to planned or expected results. Cost or schedule variances are the most frequently analyzed, but variances from plan in the areas of scope, quality, and risk are often of greater importance.
Trend analysis involves examining project results over time to determine if performance is improving or deteriorating.
Earned value analysis integrates scope, cost and schedule measures to help the project management team assess project performance. Earned value involves calculating three key values:
These three measures can be used to provide the following variances:
Performance reports are distributed using these tools and techniques.
Performance reports organize and summarize the information gathered and present the results of any analysis. Reports should provide the kinds of information and the level of detail required by various stakeholders as documented in the communications management plan.
Common formats for such reporting are bar charts (Gantt charts), S-curves, histograms and tables.
Analysis of project performance often generates a request for a change to the project. These change requests are handled by the different change control processes.