eCameron, Inc.

  • Increase font size
  • Default font size
  • Decrease font size
Home Blog: Back From Red General Blog Keep Failed Projects Running
E-mail Print
RSS

Keep Failed Projects Running

Red project recovery is a four-step process. One must, however, determine a short-term plan for the project. It takes time to get to a resolution and it is nonsensical to continue spending money at the current rate. Other than doing nothing, there are two remaining options:

  1. Stop the project;
  2. Slow the bleeding.

The preference is the latter.

Stop Sign

Why?

There are three primary reasons the project should continue:

  1. Properly diagnosing a system requires that it is running. Stopping the project stops the errant behavior. It is very difficult finding problems and their root cause when they are not occurring. As with a car, the engine ceases to make that odd noise when the engine is stopped.
  2. Waiting until after the acceptance of the full recovery plan to implement all the changes increases the risk because there are a larger number of changes to implement at one time. Remedial changes can take place while still auditing and analyzing. To continue the automotive analogy, change clogged air and fuel filters. This incurs minimal cost and effort, while few, if any, people will object.
  3. Implementing remedial fixes exercises the system in a new way. Applying new and tightening old processes will uncover other issues to address and often point to some of the problems' root causes. Replacing a dirty fuel filter may solve the problem, have no effect or point to old parts in the car that easily break.

After completion of the audit, revisit this decision to ensure that the degree of the problems on the project is of the magnitude originally anticipated. If they are worse, it is possible that stopping the project, or even canceling it, is a better option.

Slow Sign

Keeping the project running underscores that the first three steps of the recovery (audit, analysis and negotiation) do not necessarily occur sequentially, they may be concomitant. Put simple processes and policies in place during the analysis. Some of the obvious ones are:

  1. Improved team communications;
  2. Limit or eliminate overtime;
  3. Better change management processes;
  4. Improved risk management.

The first of these, improving communications, inadvertently starts with the audit. The unintended improvement is a result of interviewing everyone associated with the project. The downward flow of information is that management is taking this situation seriously. The big positive, however, is listening to the team and valuing their input. The value of this is immeasurable.

Delicious Delicious
Add to Technorati Favorites
To reduce the impact of the analysis time, avoid assigning "gates" to these steps. Gates (requiring one step to complete prior to starting the next) will inhibit the recovery and exacerbate the financial problems. This adds unnecessary overhead to the recovery and could jeopardize its success.

Tags:

Previous Blog Next Blog
 

Add comment


Security code
Refresh


Project Failure Insight:

The following blogs regularly have articles on project failure, recovery and good management practices.
Chris Curran
CIO Dashboard
Michiko Diby
Preventing Project Failure
John Estrella
Dr. John A. Estrella's Blog
Mike Krigsman
IT Project Failures on ZDNet
John F. Moore
Random Thoughts of a Boston-based CTO
Roger Sessions
Simple Architectures for Complex Enterprises

Earn PDUs with the online class Recovering Failing Projects

Suggested Books

Many of these books have reviews in the "Books to Read" section of this site.

Critical Chain
by Eliahu Goldratt

Related Items