April 15, 2007
Topic Notes: Projects that Fail
One of my pet peeves is enterprise software projects that fail. In my opinion, the only possible reason for an IT project to fail is incompetence, either on the technical staff or (far more likely) the project or above management. The most common management incompetence is the inability to say "no". (And as I am fond of pointing out in other contexts, if you have a manager who can't say "no", it's a management problem one level higher.) All of this is just a roundabout way to introduce Karl Gallagher's insightful essay on how excess requirements and misclassification of requirements kill projects.
It's actually a part of a piece I've been thinking on for some time: why it is that non-IT staff produce far more projects that work for end users than IT staff can produce.
By the way, I'll be writing over at Eternity Road as well, per Fran Porretto's gracious invitation. I haven't figured out which stuff I do will go where, except that the political stuff will probably go over there, and the IT stuff will probably be here or cross-posted, depending on depth.
TrackBack URL for this entry: