3 | 2004
In This Issue:
| Vol. 17, No. 3, March 2004 Printer Friendly PDF version | ||
| IT Project Failure: There's No Excuse The future doom of most failed IT projects is apparent from the very first day. If you move ahead on a project with a missing project charter, or ill-defined user needs, or fixed schedule, scope, and budget, you're committing IT malpractice. IT Project Failure: It's a Good Thing If you're not failing with "nobility" every now and then, you're not staying competitive. Provided the organization learns from it, failure can be the basis for progress. | "Once poorly defined projects get started, they take on a life of their own." - Lynne Nix, Guest Editor
| |
| [ Back to Top ] | ||
The subjects of how to recognize IT projects with no hope of success -- and how to best extract yourself from them -- drew a great response from the CITJ audience in our December 2003 issue. So Guest Editor and Cutter Consortium Senior Consultant Lynne Nix has assembled another distinguished group of experienced IT leaders to deliver more insight and advice on IT projects that are "born to be bad". Reduce your IT project headaches -- don't miss this issue!
