Health Check 1 – Maximising value from the Project Health Check

Projects continue to be delivered late, over budget, incomplete, requirements omitted, delivered but never used or worse, benefits never realised.  Progress monitoring, reports, metrics and dashboards only provide a snapshot, they may inform stakeholders a milestone has been missed or budget exceeded, but they do not highlight whether it could be a systemic problem.  This level of reporting can also reinforce the notion that a project is in control, facilitating a tendency by project managers and sponsors to assume everything is OK.

The Project Health Check can mitigate these risks and provide real value but only when:

  1.  The right check is completed at the right time(s);
  2. Processes & procedures are well defined;
  3. Those completing the review have the necessary skills, knowledge and approach;
  4. There’s an action plan to put things right after the review
Realised - Project Health Check

1. The right time to complete a Project Health Check

Two occasions when you may be required to complete a Project Health Check:

i. Planned

As part of a standard project review process, often at a predefined governance gate or stage.

These planned checks are in place to ensure all the steps are complete in the current stage before governance permission is given to move to the next stage.  Unfortunately, they are often tick the box exercises with missing or incomplete tasks excused as not important, fudged as complete in another process or quickly thrown together without substance or due care.

To add real value pre-planned Project Health Checks must:

  • Be completed by resource which are trained to complete the process consistently and accurately
  • Include at least one reviewer independent of the project and programme office
  • Have a defined scope, effort and budget, to complete each Project Health Check, included in the Project Charter
ii. Ad hoc

When the project is showing signs it may be in trouble (example matrix below), to identify what needs to be fixed to quickly bring it back on track.  The project contingency plan should include effort and budget to complete ad hoc Project Health Checks

Note:

  1. Project Health Checks are not designed for use after a project fails, they are not “the ambulance at the bottom of the cliff”, however a Project Health Check may be used in conjunction with a project review for a failed project.
  1. The cost of correcting an issue is many times the cost of preventing it. The longer you leave it the greater the cost.

2.   Well defined processes and procedures.

The Project Health Check must have well defined and documented processes & procedures.  The process must have the buy-in of the programme office and the commitment of all involved to deliver & follow-up on the Project Health Check

The process must include a well-documented (including names and contact details) procedure to select the most appropriate independent assessors, free from internal politics of the project and programme office, who can provide a balanced view.  The assessor will need to be sufficiently trained to follow the structured approach while taking the organisation’s unique nature and project management methodologies into account.

A good Project Health Check will encompass:

  • A well-documented, easily available and precise knowledge of the project methodology used in the Company
  • Review process which enables a common interpretation, understanding of the substance of the Project Health Check questions
  • A process which enables the identification of common problems and solutions to be applied to future projects and programs.

The terminology is as neutral as possible so it can be adapted ad hoc to certain projects and situations.

 3.   Skills, knowledge and approach

The application of the Project Health Check is not always a focus of the typical project management training courses, Prince2, PMI, etc.  It is critical therefore to develop training, classroom or on-line, for your organisation’s Project Health Check.  The initial and ongoing training effort is reduced if your processes and procedures are well documented and available on-line (company intranet).

Getting the approach right, to avoid the “tick in the box” syndrome is critical to the success of the review.  Prior to a minor Project Health Check (see matrix below) the review team confirm the scope & objectives, and for the comprehensive Project Health Check the team will review the stakeholders and sponsor agreed scope.  This preparation activity, along with a brush-up of the review processes and procedures, will guide and focus the team.

The minor Project Health Check document will have a formal process checklist to ensure the self or peer reviewers are similarly focused with the right approach.

4.   The action plan

The Project Health Check doesn’t end at the review, the review will include options and recommendations for improving and moving forward with a healthy project.  The agreed actions will be prioritised with timescale for implementing changes and owners identified for completing each action.

There’s always risk involved with change and changing the way projects are managed is no different. An important step is to identify risks resulting from implementing new ways of working.  For example, improving change management by implementing a new process will require training and they may be resistant to doing things in a new way. The review risks plan will include mitigations to support improvement efforts.

Realised Project Health Check

 Applying the right level of Project Health Check at the right time

 

It may not be necessary to complete an in-depth Project Health Check every time there is an issue.  It may be appropriate to apply differing levels of checks for differing situations.  For example, the following levels could be applied:

  • Based on a few key questions around risk, team, commercials, requirements, sponsor, management and scope
  • Should complete in 30 minutes
  • May be a peer review / interview
  • For low risk profile and small projects
  • 20 to 40 key questions, dependent on the project stage
  • Up to an hour for the initial review
  • Group round table review may include an independent moderator
  • May include key project resource, stakeholders and sponsor representative
  • For high risk profile and large projects
  • 100 to 150 questions
  • 2 x 3 – 4 hours
  • Moderation is mandatory
  • Review scope and objectives defined and signed off by the sponsor & key stakeholders
  • Will include key stakeholders and sponsor at some stage of the review process

Engaging an independent External Moderator

While many project managers may view periodic Project Health Checks as an unnecessary distraction, assessments conducted by an outside expert add both value to the project implementation and added protection against the high cost of failure.  An independent and experienced third party will recognise the subtle issues and intervene to build consensus amongst project team members developing a collaborative approach to complete the Project Health Check.

The cost of project delays and peace of mind that the project is on the right track easily out way the incremental costs incurred for an additional resource to periodically support your Project Health Check.

About the author

Bruce Swain started his project management with IBM in the United States in the late 90s.  Over the last 25 years he’s has worked with both global and SME companies in most continents.  Now home residing in Auckland he has project management experience and qualifications in PMI, Prince2, Agile and variations of each.

Health Check 2 – Areas of Concern for an investigation?

My experiences confirm every Project Health Check is different dependent on the maturity of the organisation, programme office and driver for the review, planned or ad hoc (project at risk).

The following is a list I have gathered from various organisation and Google.  It’s not exclusive and I’m always interested in the views of my peers.

What’s the one check you would add that’s not on this list?

  • Strategy: The project is in line with the organisational strategy and IT road map
  • Scope: initial definition, variation, adjustment of the plan. Clearly understood by the customer / sponsor
  • Success Factors: Critical success factors identified and agreed with the customer / sponsor
  • Business Case: A strong business case has been developed and approved
  • Cost: tracking processes, reconciliation, projections and variations.
  • Time: schedule suitability, currency, reflection of scope, use of milestones, tracking, and action plans. Project timescales accurate, realistic and achievable.
  • Quality: existence of quality plan, quality review actions, testing, resourcing.
  • Resources: sufficiency, appropriateness, time allocation, co-operation, team management, efficiency, team morale.
  • Stakeholders: Level of stakeholder engagement
  • Communication: existence of communications plan, stakeholder identification and engagement, issues arising, expectation management and monitoring.
  • Procurement: use of external resources, contract negotiation and management.
  • Risks: existence of risk plan, stakeholder involvement, mitigation strategy effectiveness, review process, issues log, resolution, mitigations identified and escalation processes.
  • Contingency Planning: existence of contingency plan, contingency testing, robustness of contingencies.
  • Benefits: review of projected benefits, changes in relevance, measurement of benefits, delivery ownership.
  • Change Management: Completion of a Change Management Plan, engagement strategy
  • Business Process: impact on business processes, implementation, planning and testing.
  • Training: existence of training plan, time to produce materials, trainer availability, staff availability, pilot and review.
  • Implementation: existence of a detailed implementation / project plans, milestones, launch support, authorisation, delivery criteria, testing.
  • Governance: existence of management review checkpoints, meeting standards, Steering Group, progress through ‘gates’, tools, skills and process adequacy, compliance monitoring, company methodology.
  • Roles and Responsibilities: definition, accuracy, team support, executive support, responsibilities not covered in definition, team members understands their role and are committed to the cause
  • Documentation: availability, organisation, easy location, version control, construction, meeting agendas and minutes, signatures, glossary, decision register.
  • Requirements: documentation, tracking of changes, documentation of changes and approval.
  • Deliverables: A clear set of project deliverables has been identified.
  • Confidence:  Confident the project has every chance of success