PROJECT FAILURE
The Official list as to why systems fail:
-
Poor management
-
Lack of user involvement
-
Ineffective team work by project team
-
Inadequate project plan
-
Insufficient monitoring
-
Lack of standards
-
Loss of control
To give a little more insight, here are some points you can expand on:

-
Lack of full Management support/Poor management decisions have been made
-
Management of the project are not prepared for serious setbacks
-
Not Visible and Vocally behind the project all the way
-
Lack of High level objectives
-
Lack of a schedule – know what would be done by when and when physical evidence would be available
-
-
Lack of sound Methodology
-
Built with little thought to process – lack of attention to details – undefined business goals and objectives
-
Large portions of client requirements are ignored, therefore leading to rewriting code.
-
Inadequate testing
-
Methodology is not tightened with development tools
-
Lack of project plan
-
​
-
Lack of solid leadership or of anyone who has completed a similar project before
-
Technical leader has not had experience in the specific area before
-
The technical leader is not in charge of the data model and application design
-
The technical leaders authority is not respected and recognised by everyone
-
-
Lack of employee instructions
-
-
Failure to perform careful analysis
-
-
Hiring too many people to work on the project at the same time
For more stuff about failure of ICT solutions go to http://www.slideshare.net/rossmccafferty/unit-3-ict-revision there's some more information there on pages 101 and 102