Tips for Rescuing a Troubled or Failing Project
Background to the Problem – Why have you been called to support or help rescue the project– what is the nature of the problem or problems? – have the issues been defined? What was the trigger that caused the client to take action?
What is the project problem statement?
Has the issue been clearly understood? What has lead the client to recognize that there are problems with the project?
How is it known that there are problems? What evidence is available? Assume nothing here.
When did the issue first occur?
When did the project stake holders officially recognize that the project is failing and needed help? When posing this question, it is important to understand the difference between the symptom and the underlying cause. A symptom is the effect of the problem and although related to the problem, the focus should remain on the reasons behind or the cause of the symptom.
The first symptom may have manifested itself sometime after the root cause event that triggered the symptom. Therefore – How did the problem first manifest itself? What evidence is available to substantiate the claims?
Looking at the key performance indicators of most projects – these include:
Is the project late on a number of key milestones?
Is the project greatly over budget?
Has the scope of the project changed?
What controls are in place to monitor these KPIs? When were they first flagged and by whom and why?
Previous Action Taken – What action has been taken so far? What has been done by whom and when in the initial stage of the investigation into the failing project? This needs to be understood because early action without research or careful thought my have made the issue worse. Has someone recorded what they have done and recorded the impact of what they have done?
Impact – What is the impact of the project problems to the business? Where should the project be now in terms of progress? Where is the project now in terms of percentage complete? Is there are metric available on Earned Value against Planned Value? Are these figures reliable?
Review the Original Objectives and Scope – Are the original Objectives and Scope of the project still valid? Have the objectives and goals of the project changed? Has the scope changed enough to significantly derail the project?
Review the Project Performance to Date in Detail – List all of the key deliverables and milestones and assess:
- Where should they be in terms of completion / delivery?
- Where are they actually in terms of completion / delivery?
e.g. – assess the original plan against current status in detail – there is no shortcut here – this will take time and the devil is in the detail. There can be huge number of deliverables in a large project so this process is not for the faint hearted.
It is recommended to be as binary (yes or no and complete or not complete answers) as possible during this review so that the results are honest. It is important to note that you will not make any friends during this process so try to take the emotion out of discussions by focussing on the facts. Some clients may hire in external resources with no personal history on the site in order to get to the facts and remove the possibility of any personal influence.
If a task is late or has had to be repeated has this resulted in an increased cost? Is this substantial? How is this being measured on an hourly/daily basis?
The resulting report from this review process will arm you with the factual data from which you can get to the root cause of the problem(s) and re-plan the project to get back on track for a successful outcome.
Project Risks – Review the original project risks to assess if they are still valid. Have the project risks been updated? Are there any new risks that need to be assessed? How will they affect the project? Have any of the original or new risks been realised? Have they had any impact on the project delivery?
Analyse the Data – Are there any patterns emerging from the review data. Using these results – look for patterns such as consistent issues with departments, people, vendors – that are consistently late or repeating tasks not completed correctly.
If there is an obvious pattern with a delivery and this is identified back to a person or a department, look for further evidence. Is the person experienced enough? Are they the right person for the job? Is there role in the project clear to them and everyone else? Are they doing other work that is preventing them from focusing on project work? Are they capable of the work assigned to them? How was this person or department originally assessed for capability? How was individual performance being monitored?
Are there other factors influencing delivery -e.g. personal behaviours, interdependent service inefficiencies, process issues, system issues, late equipment/software material delivery, procurement issues?
Are operations based resources being allocated enough time to work on the project? Has the client prioritised the project to reflect the required delivery times?
The purpose of this analysis should not be a witch hunt but an honest review of the data recorded in order to get to the real issues.
Do not overlook here to review the controls processes if they fail to capture an issue early enough to control the issue.
Report – Produce a report of your work that should include but not be limited to:
- Background to the Problem
Utilising the data that you have collected and the conclusions that you have drawn, based on evidence -communicate the results and recommendations to your main point of contact at the client site on a 1:1 basis.
Present the raw facts to them on confidence and seek their advice on:
- What they would prefer to do next?
- How should this information be released to the wider audience?
This will be a good measure of the politics on site and how it should be managed. Remember this is the client’s choice on how they wish to manage the situation.
Although it is rare -it is not unknown for clients not to do anything following such an investigation as corporately the “right thing to do” would step on too many toes and may not be the politically correct course of action.
Take Action – In order to get the project back on track you will need to do the following based on what you have learned:
- Define the Scope
- Perform a Project Risk Assessment
- Re-plan the activities with new milestones
- Re-work the budget to reflect the new plan
- Select the project team (typically some original -some new members)
- Create a proposal outlining the Project be delivered and what will be different his time in order to prevent a recurrence of issues.
- Make this presentation to the key stake holders and seek support and approval to move forward.
- Kick off the project and implement the necessary controls.
For further support book an online session with one of our project specialists here
Leave a ReplyWant to join the discussion?
Feel free to contribute!