Showing posts with label Performance Reporting. Show all posts
Showing posts with label Performance Reporting. Show all posts

Sunday, July 22, 2012

Never Underestimate The Power Of A Project Dashboard




In 2003, the Virginia Department of Transportation (VDOT) introduced a web based Dashboard for their construction projects. 

This Dashboard became a powerful tool for VDOT Executive and Project Managers, showing instantly whether projects were on track, falling behind schedule or going over budget.



The Dashboard was soon made public, and citizens were invited to view the Dashboard online and share their comments.  The performance improvement achieved by all VDOT projects was dramatic.

Prior to the introduction of the Dashboard in 2003, less than 20% of all projects were on time. By 2005, this number had improved to 75% and currently, as you can see from the VDOT Dashboard above, 97% of all projects are on time - an outstanding improvement in a very complex and challenging construction project environment.  Similar improvements were achieved in the other areas measured by the Dashboard.

As you can see from the VDOT example, a Project Dashboard can indeed be a very powerful and effective project management tool.

To be effective, a Project Dashboard should follow these following eight principles:
  • Use a standard dashboard format across all projects - in this way, the performance for all projects can be fairly and effectively compared.
    Information displayed should include the Project Schedule, Project Budget, Client Satisfaction Index, Project Resourcing Index and Project Health Check Index metrics.  A summary of the key Project Milestones and Project Risks and Issues should also be displayed.  (See the sample AlphaPM Project Dashboard tool layout above)
  • Ensure the dashboard is easy to understand - it should be easy to determine the performance of the project by using Green/Yellow/Red icons to show the performance of the project through the various key metrics.  Avoid clutter, and keep metrics and information displayed to the minimum useful set.
  • Ensure the dashboard is easy to complete - the metrics on the dashboard should be easy to measure, collect and present
  • Provide background information through a "drill down" capability - detailed information (such as the project schedule, risk register, project health check detailed results, project repository, status reports and change requests) should be linked to the dashboard, so that they can be referenced as needed. 
  • Make sure all information is timely and updated at least weekly - if it is not, it will be ignored.
  • Provide maximum visibility of the dashboard to all stakeholders - this will motivate the project team to keep on track and also ensure that the Executive and all other project stakeholders know if a project is in trouble, so that they can promptly assist in addressing problem areas. 
  • Show the project's business goals and objectives -  add a short section with a few bullets on the business goals and objectives for the project.  This helps to reinforce the importance and value of the project and keep all stakeholders focused on meeting the project's business goals. 
  • The organization must have a supportive culture
    Now here's the most challenging part of ensuring that Project Dashboards are indeed successful.  The organization culture (starting with your Executive and Client Management) must be proactive and constructive in their support of projects who show red or yellow metrics on the dashboard.

    For example, say your Executive meets you in the hallway and has noticed that your project has some red metrics on your Project Dashboard.
    Bad:  Executive says to you "Why is your project in such a mess and when are you going to have it fixed?"
    Good:  Executive says to you "I see you are having some challenges on your project.  Is there anything I or my management team can do to help you get back on track?"

    Without a supportive and collaborative executive and organization culture, project managers will resent having visible dashboards, and start to fudge metrics and cover up issues and problems, thus making them even more difficult to eventually solve.

Let us know your experiences and best practices with Project Dashboards.


Webinar:  APM13 Project Dashboards
If you are interested in learning more about Project Dashboards, and would like the AlphaPM Excel based Project Dashboard tool, sign up for our one hour APM13 "Project Dashboards" webinar at www.alphapm.com/webinars


For further information on Client Satisfaction metrics and Project Dashboards, please see these previous posts:
Client Satisfaction Surveys the Easy Way
Six Best Practices For Managing Multiple Projects

Sunday, June 17, 2012

Six Best Practices For Managing Multiple Projects


In this struggling economy, project managers are often required to manage many projects. It is usually a challenge to manage just one project, so it is inevitable that managing multiple projects will pose even more challenges.

How many projects can a project manager manage?
Now there are so many factors that affect this determination (e.g. project size, type and complexity, resources and skills available, number of clients, location and duration of projects etc.), that it is impossible to quote any useful number.  I think it will be fair to say, however, that you can manage more than you might have believed possible, if you apply the following six best practices.


Management Support
1.  Ensure the support and trust of your management and client management.
Perhaps the most valuable of all best practices is to ensure you have the support and trust of your management, client sponsor and client management.  Their proactive support is essential for the timely resolution of many activities (e.g. scope definition, project budget, resourcing, issue resolution, project prioritization etc.).  Be open about the need for their support, and take advantage of every opportunity to gain it (for example, through your project kickoff meetings, risk reviews, regular status meetings and steering committee meetings).

Resourcing
2.  Ensure you have the appropriate level of skills and resources.
This is easier said than done, but it is essential if you are to be successful in managing your many projects. Identify up front the specific skills and resources that you need for your projects, and persevere until you get them. Look for people who are team players, adaptable and willing to work in many different capacities.

Resources should ideally be dedicated to your projects and co-located.  If you cannot get fully dedicated resources, at least make sure they are co-located on specific days each week. so that you can count on their availability and support.

Performance Reporting
3.  Establish a Project Dashboard for all your projects.


Use a simple dashboard like the one shown here, to  give clear visibility to the status of your projects.

The projects can be sorted by client, so that each client sees the status for only their projects.


A Dashboard is an extremely powerful tool for soliciting the support of your project stakeholders, so ensure that the "Comments" shown for each project reflects the actions you are taking and/or the support you need to address the "yellow" and "red" areas that need resolution.  



Time Management
4.  Ensure you and your team members practice good time management.
Establish with your project team the most effective ways you can maximize your team productivity and build these into your Team Operating Agreement and practice them.
For example:
-  Keep meetings short and focused.  Take individual issues offline rather than trying to solve them at team meetings.
-  Ask your team members to let you know early if they are going to be late on an activity, so that you can take any corrective action necessary to keep the activity from being delayed.


Delegation
5.  Delegate to the max.
When managing many projects, there is quite often a tendency for project managers to take on more work themselves, since they feel their team members are already overloaded.  Wrong approach! They should delegate all activities, so that they can free themselves to work with their team leads to address issues and provide support, as opposed to being locked away trying to do activities that can and should have been delegated.
Establish a project lead for each project, or set of projects, so that you can act as the overall program manager to ensure all projects are successfully completed.


Methodology
6.  Apply a methodology that is scalable and adaptable to your project needs.
The methodology that your organization has established may not work well with your set of projects.  It is important that you adapt and scale the key elements of the organization's methodology to fit your many projects.
For example:
-  Use the simple Project Dashboard shown above for all your projects, rather than a one page Dashboard for each project.  This Dashboard can act as your Status Report for all your projects.
-  Do a combined Risk Assessment for all your projects, rather than one for each project.

Are there any other best practices for managing multiple projects that you can recommend?


Webinar:  APM13 Project Dashboards

If you are interested in learning more about Project Dashboards, and would like an Excel based Project Dashboard tool, sign up for our one hour APM13 "Project Dashboards" webinar at www.alphapm.com/webinars