J. Frank Carr provides these 7 steps to recover projects that are failing. Carr — writing from the experiences of a programmer — provides matter-of-fact arguments for each step, citing personal experience and veteran know-how. Listing steps including reviews of project feasibility, importance and cost, Carr’s 7 steps are a good reminder that failing projects don’t necessarily need to become failed projects.
Comment ID: 261
Comment Date: 2011-11-17 08:47:15
Comment Author: James Kemp
Author Email: firstname.lastname@example.org
Author IP: 126.96.36.199
The nice thing about articles like these is that their application is not limited to IT projects. I inherited a large conduit and cable construction job some years ago that I should have stopped on the spot for design issues. At the time, I let the construction manager talk me out of it. Never again…