When to kill (and when to recover) a failed project

The project is behind schedule. The pilot has failed to meet expectations. Several key team members have already said good-bye. An important vendor has just discontinued an essential component.

The decisive moment has arrived. Is it time to kill the project or press forward in a new direction?

That’s a simple question. An equally simple answer, however, can be elusive. As economist Paul Samuelson once remarked, “Good questions outrank easy answers.”

[ Find out why IT projects still fail and beware the most common project management mistakes to avoid. | Get the latest insights by signing up for our CIO newsletter. ]

To read this article in full or to leave a comment, please click here

The project is behind schedule. The pilot has failed to meet expectations. Several key team members have already said good-bye. An important vendor has just discontinued an essential component.

The decisive moment has arrived. Is it time to kill the project or press forward in a new direction?

That's a simple question. An equally simple answer, however, can be elusive. As economist Paul Samuelson once remarked, "Good questions outrank easy answers."

[ Find out why IT projects still fail and beware the most common project management mistakes to avoid. | Get the latest insights by signing up for our CIO newsletter. ]

To read this article in full or to leave a comment, please click here