I froze the feature set, implemented a strict change-control process, and reworked some buggy code. We released the software eight weeks later. Of course, that anecdote makes rescuing a project sound easy. It's actually a slow, methodical process that requires flexibility and innovation. Becoming a project recovery expert is, unfortunately, a matter of experience, but any manager can rescue a failing project.
Troubled projects suffer from at least one of six basic flaws.
Once you've identified the culprits, a ten-step plan can get you back on track. Identifying your project's problems can be difficult. The project team may know what's wrong but be hesitant to admit it openly. Some may think you're on a witch-hunt, so you must be open. Your first problem list is likely to be symptoms of the problems, not the root problems themselves.