Are you too pussy-footed to pull the plug on projects that will inevitably fail? If so, you're not alone. Whether through fear, denial, or ignorance, many organizations don't kill their doomed projects fast enough. It's a darn shame because these lousy things can drive everyone crazy while burning scarce resources.
- See also: Killing project vampires
Baseline has assembled a set of ten solid steps to help you kill IT failures mid-stream:
- Build in Ways to Cheaply Pull the Plug. Canceling bad projects is much easier when there's already an evaluation and chartering process in place.
- Set Risk Tolerance in Advance. If the tolerance level has been breached, the project gets canned.
- Don't Delay the Inevitable. CIOs should try to pull the plug as soon as possible after imminent failure makes itself apparent.
- Hone the Business Case for Cancellation. [T]ry to collect hard figures on costs and benefits to make your case.
- Get Your Resume Together. [T]hese situations can get ugly.
- Get Senior Management On Board. [K]illing a project is as critical as [convincing the board] to release project funds in the first place.
- Articulate Reasons for Cancellation to Project Team Members. [A]void finger pointing when breaking the news to a project team....
- Tie Up Loose Ends. [C]lean up documentation before reassignment....
- Look for Salvageable Intellectual Property. [A]nalyze everything to see if components can be made useful.
- Do a Post-Mortem. [H]ire an independent third party to conduct confidential interviews and present their findings.
Don't be a victim: kill the failures before they kill you.