When Bad Things Happen to Good Projects

The Wisconsin Technology Network has an article titled "Consultant says beware hidden costs of bad IT projects". Generally, the premise of the article is correct, that there are lots of hidden pitfalls that can cause serious damage to a project. As examples, the article talks about the need to ensure adequate end-user training, prioritize requirements, and so on.

Poor communication is given a special place in the hall of deadly sins:

The number one cause of what  [Robert Balon, a principal in Clerestory Consulting in Chicago], called "frequent yet avoidable project surprises," ones that compromise project success, is poor communication. Communication is a process, and Balon suggested targeted communication plans for employees, customers, and suppliers, and regular status and stakeholder meetings. Communication events should provide forums for challenging the impact of scope changes, and they should be designed with the intent of informing, gaining input, or achieving some kind of action, he added.

Most project failures are rooted in the business domain, rather than in bad technology, and the article does make that point.