We had all the necessary talent to successfully complete the task. We had time, money and a reasonable schedule, even if it was ambitious. We had a great software product, and it had high visibility and support with top brass.
But, it failed due to poor communication about staff changes during a "right-sizing" (read: layoffs). Even though the reorganization brought equally qualified replacements to the team, the changes completely disrupted flow of information and collaboration. No one knew exactly who was in charge of what. With so much confusion came chaos. Soon, in the rush to meet deadlines, everyone stopped talking. The ultimate goal was lost, and the project was deep-sixed within a week of the gold software build.
What happened? Looking over IT Business Edge's "Eleven Reasons IT Projects Fail," I figured out what applies to this situation:
Avoid or rectify these common mistakes before your project is in jeopardy.