2 ms·
I do a fair bit of failed-project-rescuing myself, and I concur with most of this. It's good advice. The only thing I'd quibble with is this: Don't think abou
by smacktoward 13y ago
I do a fair bit of failed-project-rescuing myself, and I concur with most of this. It's good advice.
The only thing I'd quibble with is this:
Don't think about the sunk costs.
... not because I think it's bad advice (it isn't), but because if you're a developer it doesn't really matter what you think about the sunk costs. What matters is what management thinks about them. And even though management are supposed to be the numbers people, it can be very, very hard to get them to understand the Econ 101 concept that holding on to bad stuff that's already paid for can cost them more in the long run.
This seems silly, but a lot of the time it just comes down to office politics: someone in management is/was a champion of the project, and a rival in management opposed it, and abandoning sunk costs will give political ammunition to the opponent (who can claim that the champion wasted company money). So the champion becomes irrationally unwilling to let go of parts of the project that clearly aren't working, just to avoid the appearance of "conceding defeat."
- hga 13y agoEchoing both ap22213 about reorgs, and you, after that threshold of official first try failure has been reached, one thing I learned the hard way is that that if the people responsible for the mess are not completely removed from the effort they'll tend to do everything they can to make the new effort fail, since only its failure validates their failure.