Why Do IT (Information Technology) Projects Fail? (and how to avoid such failures)

This report's objective is to highlight the primary causes that lead to IT project failures and accordingly provides a template of strategies that organizations can adopt to increase the probability of their project successes. Organizations that implement mature software processes and project management and control methods, inherently address the strategies highlighted in this report as part of their processes.

I've been an IT project manager for a while and I have to say this book is really quite disappointing. It's not worth [the money]and certainly not with the time spent reading it.


Excellent information   December 8, 2002
Mike Tarrani (Deltona, FL USA)
13 out of 15 found this review helpful

Like the 1995 "Chaos Report" by the Standish Group, this 30 page document succinctly gives the key reasons for IT project failure. However, this one goes into more detail, although the basic reasons persist.

If you're an experienced project manager your first response to this book will probably be that it states the obvious. However, that isn't necessarily bad since it does so in a clearly presented manner. More importantly, this book does state the obvious and can serve as a benchmark of practices during the preliminary stages of a project. In fact, it should be required reading by every key stakeholder and project team member before a major IT project is initiated.

It's short enough to be read in an hour, and is complete enough to provide a framework for a generic project risk management plan. More importantly, it can be easily understood by both technical and business stakeholders, and will get everyone on the same page during the project planning phase, while exposing the pitfalls that will be encountered along the way.


the essentials that everyone knows about but very few follow   October 22, 2002
31 out of 31 found this review helpful

27 long years in the IS industry and sometimes I wonder about the progress that we have made. We are still pouring money on systems that our users dont want. The truth is that its all very basic stuff. follow those basics and your staff and the users of those systems will be happy.

these 30 pages remind you of all those basics, which IS organizations should have been following long ago, but they are not. we keep repeating those mistakes. you wont find aything in this ebook about programming or proj management methodologies (re - another reviewer's comments)- you will get what this page says in the description. if you still buy it, you wont be disappointed. Once you buy it, post it for constant reminders or get it in your company's processes.


Good coverage of the essentials   October 21, 2002
J. Wright (Ogden, UT United States)
16 out of 16 found this review helpful

Covers the primary points that executives should look for in ensuring project success. Build these issues into your organization.


Good summarized advice   October 18, 2002
12 out of 12 found this review helpful

With so much information out there on project management that keeps changing daily, you can take this peice of advice and minimize your failure rate. But, do not rely on this to become an expert on project management (it is 31 pages long).