10 reasons for IT failure

This caught my attention when I received the ZDNet Newsletter. It pointed to the blog of Michael Krigsman with the rather uncommon name : 'IT Project Failures'. He points to the original author of this list, Mike Kavis, who writes about this in his blog on 'Enterprise Architecture'. Here's a summary, but just take same time to read the entire topic. It's really interesting, perhaps somewhat confronting, as you'll recognize a lot. At least I do.

1. Poor Communication
2. Underestimating or ignoring impact of change
3. Lack of Leadership
4. Lack of strong executive sponsorship
5. Poor project management
6. Poor Planning
7. Trying to do it cheap
8. Lack of technical knowledge
9. Lack of sound business case
10. Poor vendor management

How about telling us how we do have to do it ?
Well, he doesn't leave us entirely clueless :

1. Build strong business case
2. Secure executive sponsor and top level buy in
3. Create a Road Map
4. Communicate the Road Map
5. Empower Others to Act on the Road Map
6. Start small, deliver early and often (agile)
7. Expand, leverage reuse
8. Govern

As I always say, just check it out !