Project Rescue and Recovery Services

Everyone has been there. Unfortunately projects, programs, and sometimes entire initiatives fail. As opposed to the normal first reaction of finding someone to blame, what is needed is immediate action. Here are some common symptoms that cause projects to fail:

• Scope is increasing rapidly causing both the cost to increase and the project to slide.
• The users are unhappy with the systems performance or there are too many bugs.
• Risks that were never imagined are slowing the progress.
• The project sponsor or other executives are not engaged.
• The customer is not helping define the solution or they are not using it.

However, failing projects are only symptoms of larger problems in the organization that need to be fixed and these are rarely the real issues. Root causes are more likely:

• The concept of the product being built does not match the company goals.
• There are unrealistic deadlines or budgetary constraints placed on the project.
• The company is over their head and trying to do projects that too complex for their skillsets.
• Leadership does not understand how they need to support the project.
• The project is trying to address non-project issues, such as maintenance and executives do not understand the issue.

What Can Be Done