Tips For Identifying The Walking Dead

 

We might assume that organizations have well defined criteria that are used to decide which projects should be terminated. Unfortunately, most organizations are haunted by the un-dead corpses of those projects that have survived long past their useful life. A contributing factor to the proliferation of these zombies is the lack of objective criteria as well as inconsistent decision-making regarding project termination.

In this economic climate, the inability to consistently terminate projects is competitive disadvantage as it robs organizations of the ability to focus on high value projects that will help them survive a downturn and come out much stronger on the other side than their competitors.

To improve the consistency of project termination decisions, introduce an impartial project delivery assurance process that gets executed on all active projects (over a certain size) on a quarterly basis. This delivery assurance process could look for the following tell-tale signs of project "rigor mortis":

• The project's business benefits (tangible or not) are not expected until the end of time.
• The project sponsor never existed, is the Invisible Man, or has entered the Witness Protection Program.
• Ask the question of your portfolio steering committee or of all Department heads - will you care if this project gets axed. If no one says "yes" or no one can remember the rationale for the project, get it off the books!
• Ask the question of the sponsor (if you've located him/her) - "Would you initiate this project today?" See if they can look you in the eyes when they answer "Yes"...
• The achievement of the project's business benefits is heavily tied to external factors or to the successful completion of high risk internal initiatives.
• (Re)do a risk/reward evaluation of the project (which had hopefully been done prior to the project being approved) - if the project now looks more like a dead dog than a cash cow, you've found a winner!

Do you see a trend?

None of the questions I've asked are using traditional ways of evaluating project health - this does not mean that we are ignoring earned value management, the triple constraint and your issue logs, but we simply can't afford to have successful operations, but dead (or un-dead) patients!

(Note: this article was originally written and published by me in July 2009 on Projecttimes.com)