IT Management - Baseline
Home arrow IT Management arrow 10 Steps to Pulling the Plug on an IT Project
10 Steps to Pulling the Plug on an IT Project
( Page 1 of 12 )

A poorly implemented or misaligned IT project can be like a millstone around a CIO's neck. Unfortunately, sometimes the only way for IT leaders to get on with their work is to remove the weight of those millstones altogether.

Pulling the plug on an IT project before completion is never easy, but it is often the right thing to do when all signs point to eventual failure.

“The problem when you bury, ignore or lie about the state of a project is that you either look dishonest or incompetent,” says Bruce Webster, an IT management expert, author and founder of Webster & Associates. “It is far better to tell the truth and look for another job than have the project come down in burning ruins about you.”

We asked Webster and other project management experts such as Mike Sisco, president of MDE Enterprises, an IT consultancy and IT management training firm based in Columbia, Tenn., and Steve McConnell, president of the Bellevue, Wash.-based software-development best practices firm Construx Software for their best tips on how to kill the stinkers as gracefully as possible. Here is their collective best advice for pulling the plug on an IT Project.



 
 
>>> More IT Management Articles          >>> More Slideshows
 

 
     Slideshow Archive
Play Next      Slideshow Archive
Slideshow Index:
  1. 10 Steps to Pulling the Plug on an IT Project
  2. Build in Ways to Cheaply Pull the Plug
  3. Set Risk Tolerance in Advance
  4. Don't Delay the Inevitable
  5. Hone the Business Case for Cancellation
  6. Get Your Resume Together
  7. Get Senior Management On Board
  8. Articulate Reasons for Cancellation to Project Team Members
  9. Tie Up Loose Ends
  10. Look for Salvageable Intellectual Property
  11. Do a Post-Mortem
  12. Check Out These Slideshows