What is system failure? An information system that does not preform as expected, is not operational at a specific time and cannot be used in a way it was intended. Failure varies from a range of 50-80% and sometimes higher as many people are not willing to publicise their losses only their winnings. Software projects often fail due to poor engineering principles which are key to success in software projects. Engineering principles need to be examined critically just as they should be when building an element of construction. According to Sauer, actual failure finally and irreversibly occurs when a project organization is unable to sustain sufficient support to continue work on the system, including development, maintenance, and operation; and the cessation of work leaves users dissatisfied with what the system has done for them.
Top 10 Ways To Guarantee Failure:
1.Don’t use a specific methodology because coding is all that is really important.
2.Create the project plan by working backwards from a drop-dead system completion date.
3.Dont bother with a data model, just build whatever tables you need.
4.Use a technical lead that has never built a similar system.
5.Hire forty developers to make coding go faster.
6.Build the system in Java, eventhough you have no intention of deploying to the web.
7.A few months before the system goes live, assign a junior developer to handle the data migration.
8.Skip the testing phase because the project is way behind schedule.
9.Change the system to support new requirements.
10.Buy a commercial off the shelf package and customize it.
“You stop working because you fail… but you fail because you stop working.”
Sources: Dr. Paul Dorsey, Dulcian Inc. (2005), Sauer, C. (1993) Why Information Systems Fail: a Case Study Approach, Alfred Waller, Henley-on-Thames.