Failure is part of development and progression. Failure in Information Systems is caused by defects in the design, process or quality of the system. At the root of most of this failure is human error. Part of this is the fact that system analysts do not listen properly to the needs of the user as well as the user changing requirements. Often 20-50% of the original requirements change due to miscommunication between the two parties. One example is a system that was supposed to take only 3 months to implement; the project has now been ongoing for nearly 2 years just because the user keeps altering requirements. The aim of a systems analysts is to gather user requirements and turn those into working software. Gathering requirements requires an understanding of the organisation, of management and the information technology that is shaping the system. Difficulties can again arise here due to:
- Complex problems
- Unknown domains
- Non-technical customers
30% of systems are cancelled before they are fully implemented and many are not even used once they are completed as they fail to provide the benefits expected. Worse than a killed project is a system that exceeds its budget – 51% of projects exceed budgetary limits by 189% but only deliver 74% of their functionally that is needed.