Project failures have become a common term that every project manager or business executive wants to separate themselves from. We tend to point the finger at one reason or the other being the cause of the failure. No one wants to take responsibility for the failure as it may tarnish their performance records. Would it? If it did, then most project managers and other managers would be in the hot seat for bad performance. As a matter of fact, you would be hard-pressed to find a project manager who has not had their fair share of project failures.
A study recently done by the Standish Group 2015 Chaos report (based on the criteria of on time, on budget with a satisfactory result for 50,000 projects around the world, ranging from tiny enhancements to massive systems re-engineering implementation) indicated that only 29% of all projects were successful, 52% were challenged, and 19% failed (1). It is important to note that smaller and moderate sized projects, as well as those that took an agile approach, had a higher rate of success. Larger projects, on the other hand, had a very high rate of failure.
Additionally, based on PMI's 2016 Pulse of the Profession report, "organizations waste US$122 million for every US$1 billion invested due to poor project performance." (2)
These numbers are quite scary and beg the question: what is causing all these project failures? And why is it that project organizations just can’t seem to get their arms around these failures and improve results? Is the problem tied to projects by nature? Or do PMs and their organizations have something to do with the outcome?
To answer the above question, we need to first understand what project failure is, then what contributes to project success or failure, and finally how we can attempt to eliminate or reduce project failure and increase the level of success.
What is Project Failure?
To state it simply, we can say that a project has failed if it did not meet its intended objectives. As stated above, the Standish Group in 2015 measured projects on being delivered on time, on budget with a satisfactory result. Projects are typically initiated to satisfy a business objective, which, in turn, could be part of a larger organizational strategy. At the same time, the project must also meet most stakeholder expectations. If the project can meet both the business objectives and all stakeholder expectations, then we can consider it a success. However, the picture is not as clear as we wish it could be. Most of the times, we do not have clear objectives (scope) to go by. In other instances, we work in a culture where stakeholders are constantly changing their expectations and adding more as the project progresses. Sometimes, perception plays a role. Consider a surgery where the surgical procedure is successful, but the patient still dies. Did the surgery fail? In the realm of projects, this might be a project that satisfies all the criteria of success but still carries the sense of failure because that's what people think it is. People in business have been saying "perceived" equals "real" for many years, and we can’t change that.
So if stakeholders, business people, financial managers, end users, peers and superiors all think your project has failed, it surely has. Late projects, projects over budget, projects that don't deliver the business value they promise, and obviously projects that deliver the wrong product...these are all failed projects.
Project Success Contributors
According to the 2015 Standish Chaos report, the following are key factors (in order of importance) that contribute to a project’s success:
- Executive Support: by providing financial and emotional backing.
- Emotional maturity: the team’s behaviors, skills and the weakest link within.
- User Involvement: in the project decision-making and information and requirements gathering process.
- Optimization: improving business effectiveness and optimizing a collection of many small projects or major requirements. Optimization starts with managing scope based on relative business value.
- Skilled staff: is highly proficient in the execution of the project’s requirements and deliver the project or product.
- SAME is Standard Architectural Management Environment. The Standish Group defines SAME as a consistent group of integrated practices, services, and products for developing, implementing, and operating software applications.
- Agile proficiency means that the agile team and the product owner are skilled in the agile process.
- Modest execution is having a process with few moving parts, and those parts are automated and streamlined. It also means using project management tools sparingly and only a very few features.
- Project management expertise is the application of knowledge, skills, and techniques to project activities in order to meet or exceed stakeholder expectations and produce value for the organization.
- Clear Business Objectives is the understanding of all stakeholders and participants in the business purpose for executing the project. Clear Business Objectives could also mean the project is aligning to the organization’s goals and strategy.
Here, we could easily state that lack of presence of the success factors above would lead to project failure by default. However, I am going to take a different approach and explain the causes the way I see them. This is because research on this topic will yield many results, and although there are many causes of project failure, I will focus on the most common, yet critical factors that result in project failure.
Organizational Culture – This is at the heart of most project failures. Very few organizations have the infrastructure, education, training, or management discipline to bring projects to successful completion. Since the organization sets the company policies by which the project team will have to abide, a lack of knowledge about project management will result in a lack of consideration for what projects need in order to succeed. The end result of this is inefficient authority systems and gaps in approval processes and weak support for the project team within the organization. The best solution is to look into creating and setting a Program Management Office (PMO) that can control the project management efforts centrally and provide the needed support for the project teams.
Inadequately Trained and/or Inexperienced Project Managers – This is very widespread, and especially in developing countries where business grew faster than the organizational infrastructure itself. So, we find companies that have grown to over 100 employees, with about 20 project managers who have taken on such roles from engineering or other departments. These project managers are clearly not prepared to handle projects that require intricate dependencies, planning, estimating and collaboration amongst project teams. They also lack the proper knowledge and certifications that should be expected for them to perform their tasks successfully. Professional training should be provided and, at a minimum, there should be a few PMP certified professionals amongst the team. This will ensure that they at least know what the best practices are.
Lack of Project Governance – Organizations that grow from operational and functional to projectized can only succeed if they set the proper governance for their project management. Project Governance is the rules and regulations or standards under which projects function. It covers the mechanisms put in place to ensure compliance with those standards. Governance requires buy-in from senior management to empower PMO’s and program managers so that policies can be enforced. Here again, a PMO would do a lot of good to bring projects into control.
Inadequate Tools and Methods - As many organizations grow, they tend to make do with what resources and processes they have in order to deal with project challenges. However, each resource may be working on a different wavelength and using different tools. This results in many documents being created, several procedures for the same task, and multiple software and manual tools being used to plan and estimate projects. Most of these software tools could be quite outdated and need to catch up with the times. A good start to repairing this problem is to look to project management software solutions that the team can adopt.
Poor Requirements Management – This should actually be almost at the top the list. Poor requirements management can be attributed to one out of each three project failures. Poor requirements gathering could mean that we either did not collect complete requirements or we left out some key stakeholders. This means that either we will deliver the wrong product, miss out some important features and functions that should have been there, have to make constant changes in the scope, or even drop the project once the true scope and feasibility is clear. Poor requirements are like a cancer that will most likely kill any project’s chance of success. Boston Management Consulting International offers training for business analysts in requirements gathering and can also help them attain certification from the IIBA. (http://bostonmc.com/)
Poor Planning and Estimating – Planning and estimating require the necessary knowledge and expertise. Poor planning can lead to underestimations of efforts and budgets, as well as fatal oversights. Planning should be practiced by well-trained and certified planners. Get them trained and certified!
Inadequate Communication and Reporting – Poor communication can break anything, whether it’s your project, operation, or even your family life. Without all communication and reporting being properly planned for, we could be executing in the dark. Develop a communications plan. Talk to consultants if you don’t know how to develop the plan.
Poor Risk Management – Most organizations do not want to deal with risks. There have been instances where project managers even hid the risks in order to keep their projects alive. The general perception is that if the risks are brought to light, the project could be looked upon as a failure and an expensive and risky one. However, poor risk management can result in huge losses and even in companies going under. It is strongly advisable that risk management is incorporated into the methodology of each project organization. Additionally, there is specialized software for Risk Analysis, as well as risk management certification training that can prepare a risk professional to take on such important tasks.
Misalignment between Projects and Organizational Strategy – If all the right ingredients for success are there, but we go and initiate the wrong projects, what good would it do? It is essential that an organization implement an enterprise view of all their project portfolios and group investments in ways that can help them identify where the efforts should be applied. Additionally, proper program management must be in place so that related efforts are grouped into programs to gain the most benefits. There is certification training for portfolio and program managers endorsed by PMI that could be a great start.
1 2015 Standish CHAOS Report
2 http://www.pmi.org/-/media/pmi/document ... n-2016.pdf