The principal aim of this article is to identify and explore multiple dimensions of project failures during the entire life of project execution.
Many projects fail. The only way that companies can get better at performing projects is by learning from projects they have carried out. There are small things that can decide the fate of the project.
These all in project management practice and research has been to see it as a threat and as something that should, if possible, be neutralized, reduced and followed.
Question – “Did the project deliver the results and quality we expected?“
Answers to this question could be different from a different perspective. There is no single method or organizational structure that can be used to manage projects to success. Project failure can happen in any organization.
There are many reasons why projects (both simple and complex) fail; the number of reasons can be infinite and can fit into a different phase of SDLC (Software Development Life Cycle), initiation through go live. Sometimes it’s out of the control of a project manager and/or the team members. Sometimes failure is controllable.
Here are some of the common reasons why the project fails.
1. Incompetent Project Manager — A manager who helps steer the project in a timely fashion and provides sound, inspiring leadership can go a long way toward bringing about a successful project.
2. Less Involvement of Project Managers — Even the biggest project depends on the success of the smallest components. On relatively inexperienced teams, managers must be involved in the details for key activities.
3. Unavailability to Skilled Resources — Managers always struggle for the right skilled resources; leadership must provide planned/skilled resources on time to avoid project delay or failure.
4. Lack of Proper Planning — Without a clear focus at the earliest stage of the project, you make things harder on yourself, leading to inappropriate estimations and half-cooked planning.
5. Lack of Management Support/Leadership Alignment — Senior management must remain fully engaged throughout the project life cycle.
6. Missing Communication — A clear communication plan with stakeholder details, distribution methods, and frequency is essential to save your project from failure.
7. Ignoring Change Management Process — Every project must have a change control process, and every change request, however small, must go through it.
8. No-Risk Management Process — Many projects fail because there is no risk management process as an integral part of the management process.
9. Inadequate Quality Assurance — Managers often fail to plan appropriate reviews, tests, or checkpoints where quality can be verified.
10. Missing Management Tools/Framework — The right methodology and management tools help managers stay on top of the project.
11. Company/Culture — A political culture unsupportive of competency and transparency will leave team members unmotivated.
12. Inappropriate Prioritization — Managers should lead prioritization exercises with all relevant stakeholders, weighing value, cost, and risk.
13. Inaccurate Stakeholder Analysis — Identify your stakeholders, understand their influence and interest, and develop a plan to win their support.
14. Use of Unfamiliar Tools — Unfamiliar tools can cause severe problems as teams deal with a learning curve on top of usual duties.
15. Always Saying “Yes” to the Customer — Change is a major cause of project failure; before committing to something, analyze the pros and cons.
16. Bonding Between Team Members — It is the manager’s job to unite the team through forming, storming, norming, performing and adjourning.
17. Unrealistic Expectations — Set realistic expectations for every team member early so they don’t lose clarity and focus.
18. Talking Through Problems — Stakeholders have a vested interest in the project’s success and have a right to know about developments impacting the outcome.
19. Guesstimates on Effort — Inaccurate “gut feel” estimates can leave a team slogging to meet a deadline with a huge effort overrun.
20. Avoiding Code Reviews — Code review helps produce a stable, quality deliverable and catches issues testing alone may miss.
21. Skipping Prototyping — A sketch, wireframe, mockup, or prototype keeps expectations aligned and communication clear between stakeholders.








