PROJECT FAILURE

Reasons of Project Failure

Reasons of Project Failure

Project Failure

At the end of a project, especially when there is a failure, we try to analyze what worked well and what could be improved. In many companies, it is primarily the search for culprits. That explains why sometimes people do not want to do post-mortem. It's a sign of a bad environment for project management and is proof that they have understood nothing. Achieving consensus on the definition of failure seems unlikely. In my opinion, failure is not due to technology, is due to people and process side. Mismatch is a material failure which will not achieve its design goals; failure process is related to the budgetary and time constraints, the system above its cost and deadlines. Interaction error is due to insufficient communication between users and system. Failure is expected that the SE does not meet the expectations of stakeholders, lack abandonment occurs when the project is completely discarded (Olsson, 2007).

Reasons

The lack of consideration of organizational issues in system development can lead to project failure. Failures can occur in many ways without foundation and gold standard for achieving it. Most research has explained that the organizational aspects play an important role in determining the system failure. According to Sauer (1993) all types of technical and organizational systems also suffer failure, Lucas (1975) says that it is our argument that has failed because they have ignored the organizational design and process-based computer IS. Therefore, I firmly believe there is a serious need to discuss aspects of organization and management of failure. This essay considers the managerial and organizational aspects, keeping the position that technology is neutral (Gardiner, 2005).

Suboptimal performance

Often, objective or objectives set designed before the implementation of institutional strengthening project, but as the project runs during that time shows that there is a difference between real and desired outcomes that lead to failure project. The developers of the system, either on purpose or unfortunately do not pay attention to user needs. Unfortunately due to the negligence designers and intentionally due to criticize the management of user demand and design the system for their own needs. Thus, the contradiction between the intentions of the developers and users may ultimately result in the devastation of the system.

According to Dutton et al (1995) even though the system works as they see the failure bleeding can occur. A U.S. company called TELECO had hired consultants to implement Business Process Reengineering in the company. Management's intention was to reduce the number of employees and reduce costs. Users are not aware of the downsizing, but were under the impression that the new system implemented to ensure improved quality, speed and value to the existing working environment. The organization was passionate about the reduction in cost after downsizing and did not consider the needs of the user. The management has made the designer to change their exercise. Later, when this communication was left open employees reached, there was a lack of trust between ...