- Insufficient planning
- Abandonment of planning under pressure
- Subcontractor mismanagement
- Lack of effective sponsorship (at executive level)
- Outsourcing to reduce costs
- Unclear project vision
- Switching development tools in the middle of a project
- Lack of automated source code control
I admit to mixed feelings about McConnell and this survey doesn't help reduce them -- he and his books are written as if no one but developers are involved in building software, which alienates me as a designer. His discussions of requirements, planning, and design don't seem to allow for the involvement of user researchers or even product managers, let alone interface designers who may have to write the specs. One "classic mistake" I see is to leave all the interaction design, visual design, requirements collection, and user testing to developers who also need to be writing code; may not know how to do the non-coding work well; and may not want to do it "all" themselves.
Software is and has been a multi-disciplinary effort for a long time now. McConnell has a huge readership, but hasn't helped spread that word, which set us all back a bit, I think.