Contents
Introduction- PROBABLE REASONS FOR A PROJECT FAILURE
- POOR COMMUNICATION
- TOO MANY PLANS AND NOT ENOUGH PLANNING
- POOR LEADERSHIP BY THE PROJECT MANAGERS
- FAILURE TO DIFFERENTIATE BETWEEN THE BUDGET AND THE ESTIMATES
- POOR CHANGE CONTROL PROCESS
- SETTING UP UNREALISTIC DEADLINES
- POOR TESTING
- FAILURE TO UNDERSTAND THE PROJECT GOALS
- SYSTEM DISASTER
- UNREALISTIC DEADLINES
- IMPROPER TESTING
- IMPROPER COMMUNICATION
- POOR PLANNING
- RESISTANCE TO CHANGE MANAGEMENT
- FAILURE TO UNDERSTAND THE GOALS OF THE PROJECT
- REFERENCING
Description
In a perfect world, where every activity is supported by skill and technology, it is expected that all projects should have been completed within time and budget. But in reality, it is astonishing to know that most of the projects fail due to a variety of reasons. To begin with, let us discuss what we mean by the success and failure of a project. The following are the parameters which can be considered to see whether a project is a successful one or not –
Whether the project has been able to satisfy the business requirements of the stakeholders
Were the required results produced on time and within budget?
Has the project been able to deliver the business value as promised?
Are the stakeholders and the users happy with the project results?
The failure of any project can also be measured across a spectrum. They can be categorized as follows:
• There has been no value for money delivered and the entire investment has gone into the drains.
• The delivery was so late that the product was of no use
• The product or service quality is quite poor and hence the users are not at all satisfied with the product.
• The project cost exceeded the estimated budget so much that the product was no longer financially viable.
