Difference between revisions of "Project sharing dashboard"

Revision as of 12:56, 29 January 2014

Template:Complete

Template:Consolidation stage

Definition

Project sharing dashboard is A tool used to identify learning and sharing opportunities across a range of comparable projects

Summary

A knowledge sharing dashboard periodically plots expected values for project performance indicators against actual values for these indicators and does so for a portfolio of projects. Those projects that exceed expected values may have access to good practice from which projects that under-perform against expectation (on the same indicator) can learn.

Using a knowledge sharing dashboard, Learning between projects can be targeted and projects that perform above expectation can be paired to those projects that under-perform and knowledge transfer between the two sets can be facilitated. It should be noted that a difference between expected and actual values may not always be due to a knowledge advantage. Other factors could play a role, including external factors that cannot be influenced by the project.

Description

Purpose

To identify learning and sharing opportunities across a range of comparable projects.

Beneficiaries and other stakeholders

Skill requirements

No special skills are required. What is important is an understanding of those project indicators that are good representations of project performance.

Instructions

1. Agree a set of project performance indicators and agree the frequency of reporting values (baseline values, period expected values and period actual values). In longer-term projects, a frequency of once or twice a year is often sufficient;
2. Set up a reporting infrastructure, with which projects can report their data to the dashboard. Make sure that differences between expected and actual values are highlighted (e.g. use a red/amber/green scheme). In some cases a positive difference (i.e. actual value is higher than expected value) can be interpreted to be a good achievement, whereas in other cases, this may be an underachievement (e.g. in the case of cost-related indicators);
3. Agree which data are accessible to which stakeholders. In some cases, it may be necessary that only aggregated data (e.g. ranges or averages) for certain indicators can be shared across projects. Make provisions for ensuring that no data is disseminated to stakeholders that are not entitled to them;
4. Develop standard reports for various stakeholder groups. Project-only reports that position an individual project within their peer group (anonymously, if required), project portfolio reports that provide the full detail and external reports that are aligned with the knowledge sharing terms agreed;
5. Periodically analyse the dashboard to identify who can learn from whom (and conversely, who should be invited to share with whom).

Examples

An example of a knowledge sharing dashboard is shown below. In this particular case, a series of Carbon Capture and Storage projects are compared, against a multitude of indicators. The entire set of indicators counted to over one hundred and reporting frequency was set to twice per year.

Case studies:

Critical success factors

Hints and tips

FAQ

Templates

Other related documents

Training materials

References

Related articles