Sooner or later, every IT organization experiences the unpleasant phenomenon of the "doomed" project. For obvious reasons, it's better to find out about these sooner rather than later, because it's better to kill the project before too many careers have been ruined and too much money has been wasted. Unfortunately, it's not always easy to tell whether the project has developed a fatal case of gangrene, and organizational politics often prevent a frank and open discussion of the situation.