1. Miscalculated Time and Budget Frames
Clients are always eager to have their projects rolled-out on time and even before the stipulated time at throw away prices. In most cases, this keenness of the client leads to developers agreeing to a rather shorter or unrealistic and non-negotiable time frame for the project delivery at meager rates. As a result, programmers are not able to deliver the project on time, but being pushed to the wall under cumbersome expectations to ensure faster rollouts, software experts focus more on coding and less on designing, compromising user experience and usability in return.
– As per the report by a leading MNC, only 40% of the software projects meet schedule, budget and quality goals.
2. Was it Needed At All?
This is rather a surprising reason which attributes to a software project failure, primarily in low-consensus and non-evaluative organizations that lack in leadership. A classic example as depicted in a report by a leading Consulting firm shows how resource-gulping these projects could be.
– The FAA Advanced Automation System (1981-1994) : Cost of $3.7 billion; peak staffing of 2000; maximum run rate of $1 million/day; 14 years duration of development
– Nothing was delivered; no code was ever used. The reason: nobody wanted it in the first place or in other words there was no business case for it
3. Lack of Communication
Another key aspect is the failure to set up effective communication channels and participative environment. Due to this, ideas or process flows get adrift and leads to lack of previews and interactions between the active project promoters and developers. At times standardized assumptions during communication may lead to misunderstanding as standards may vary from industry to industry leading to business software failure.
4. No End-user Involvement
If the user’s point of view is not taken into consideration while developing the IT project you are definitely calling in for trouble. So failure to find and engage the right users to participate in the software development process is extremely disastrous.
– As per the Standish Group, it was the lack of user involvement that caused the large-scale federal government project to fail. The group also says that user involvement is 23% of the true cost of a project.
5. Unfocused Executive Sponsors
Inactive leadership through non-effective executive sponsors is why IT projects fail. They are the people who keep the process ignited and are primarily responsible for the success or failure of the project. So in most cases lack of time spent by these executive sponsors or the complete lack of it, leads to project failures.
6. Failing to See the Bigger Picture
This is a classic example of a failed project, which failed to see the big picture ahead. You can downsize this to even smaller projects, where lack of foresight or stakeholders confidence is in question.
– In UK, officials called off what was considered to be the largest public IT project of all time. It was a project which was intended to provide electronic health records for all of its citizens. After 10 years and costing an estimated around 19 billion USD the authorities concluded that the project was not fit to provide the modern services it was intended to.
In hindsight this also tells us the importance of reviewing failure of a software project before starting a new project.
7. Chasing Technology
Some managers are lured into the benefits of the latest available technology, and try to use it for their ongoing projects. This forces them to gravitate from the planning done at the design stage. This leads to the failure of the whole system, change in objectives, or failing to complete the project on time. Moreover, these latest technologies may not even be mature or robust enough to have been used in the first place.
8. Development Downtime
Development downtime is one of the primary contributors to challenged or failed projects. Major factors that lead to software project failure are – application bug or error, environmental factors, infrastructure or software failure, virus, hacker, network/hardware failure and operator error.
The chart shows application bugs to be the leading cause of downtime apart from other factors.
9. Lack of Periodic Assessment
Lack of client induced and developer mandated assessments, and failure in smartly establishing milestone points leads to improper assessments, which leads to irreparable or catastrophic failures.
10. Lack of Quality Testing
In most projects, the importance given to coding isn’t given to testing. Honestly speaking testing calls for a greater integrity and role in the entire software development lifecycle. Casual testing, testing under non-real time environments contribute to testing failures. Bolder companies test their projects under live production environments in order to service disasters.