101 Common Causes
There are many causes of project failure and every failed project will have its own set of issues. Sometimes it is a single trigger event that leads to failure, but more often than not, it is a complex entwined set of problems that combine and cumulatively result in failure. Generally these issues fall into two categories. Things the team did do (but did poorly) or things the team failed to do.
Based on reviews of the projects in the Catalogue of Catastrophe and discussion with more than 500 people involved in real life projects, the following list documents 101 of the most common mistakes that lead to, or contribute to, the failure of projects:
Goal and vision
- Failure to understand the why behind the what results in a project delivering something that fails to meet the real needs of the organization (i.e. failure to ask or answer the question “what are we really trying to achieve?”)
- Failure to document the “why” into a succinct and clear vision that can be used to communicate the project’s goal to the organization and as a focal point for planning
- Project objectives are misaligned with the overall business goals and strategy of the organization as a whole (e.g. Sponsor has their own private agenda that is not aligned with the organization’s stated goals)
- Project defines its vision and goals, but the document is put on a shelf and never used as a guide for subsequent decision making
- Lack of coordination between multiple projects spread throughout the organization results in different projects being misaligned or potentially in conflict with each other.
Leadership and governance
- Failure to establish a governance structure appropriate to the needs of the project (classic mistake award winner)
- Appointing a Sponsor who fails to take ownership of the project seriously or who feels that the Project Manager is the only person responsible for making the project a success
- Appointing a Sponsor who lacks the experience, seniority, time or training to perform the role effectively
- Failure to establish effective leadership in one or more of the three leadership domains i.e. business, technical and organizational
- The Project Manager lacks the interpersonal or organizational skills to bring people together and make things happen
- Failure to find the right level of project oversight (e.g. either the Project Manager micromanages the project causing the team to become de-motivated or they fail to track things sufficiently closely allowing the project to run out of control).
Stakeholder engagement issues
- Failure to identify or engage the stakeholders (classic mistake award winner)
- Failing to view the project through the eyes of the stakeholders results in a failure to appreciate how the project will impact the stakeholders or how they will react to the project
- Imposing a solution or decision on stakeholders and failing to get their buy-in
- Allowing one stakeholder group to dominate the project while ignoring the needs of other less vocal groups
- Failure to include appropriate “change management” type activities into the scope of the project to ensure stakeholders are able to transition from old ways of working to the new ways introduced by the project
- Failure to establish effective communications between individuals, groups or organizations involved in the project (classic mistake award winner).
- Lack of clear roles and responsibilities result in confusion, errors and omissions
- There are insufficient team members to complete the work that has been committed to
- Projects are done “off the side of the desk” (i.e. team members are expected to perform full time operational jobs while also meeting project milestones)
- The team lacks the Subject Matter Expertise needed to complete the project successfully
- Selecting the first available person to fill a role rather than waiting for the person who is best qualified
- Failure to provide team with appropriate training in either the technology in use, the processes the team will be using or the business domain in which the system will function
- Lack of feedback processes allows discontent in the team to simmer under the surface
- The Project Manager’s failure to address poor team dynamics or obvious non-performance of an individual team member results in the rest of the team becoming disengaged
- Practices that undermine team motivation
- Pushing a team that is already exhausted into doing even more overtime
- Adding more resources to an already late project causes addition strain on the leadership team resulting in even lower team performance (Brooks law).
- Lack of formality in the scope definition process results in vagueness and different people having different understandings of what is in and what is out of scope
- Vague or open ended requirements (such as requirements that end with “etc”)
- Failure to address excessive scope volatility or uncontrolled scope creep (classic mistake award winner)
- Failure to fully understand the operational context in which the product being produced needs to function once the project is over (classic mistake award winner)
- Requirements are defined by an intermediary without directly consulting or involving those who will eventually use the product being produced (see also lack of stakeholder engagement above)
- Individual requirements are never vetted against the project’s overall objectives to ensure each requirement supports the project’s objective and has a reasonable Return on Investment (ROI)
- The project requirements are written based on the assumption that everything will work as planned. Requirements to handle potential problems or more challenging situations that might occur are never considered
- Failure to broker agreement between stakeholders with differing perspectives or requirements.
- Those who will actually perform the work are excluded from the estimating process
- Estimates are arbitrarily cut in order to secure a contract or make a project more attractive
- Allowing a manager, sales agent or customer to bully the team into making unrealistic commitments
- Estimates are provided without a corresponding statement of scope
- Estimation is done based on insufficient information or analysis (rapid off-the-cuff estimates become firm commitments)
- Commitments are made to firm estimates, rather than using a range of values that encapsulate the unknowns in the estimate
- The assumptions used for estimating are never documented, discussed or validated
- Big ticket items are estimated, but because they are less visible, the smaller scale activities (the peanut list) are omitted
- Estimation is done without referring back to a repository of performance data culled from prior projects
- Failure to build in contingency to handle unknowns
- Assuming a new tool, process or system being used by the team will deliver instant productivity improvements.
- Failure to plan – diving into the performance and execution of work without first slowing down to think
- The underestimation of complexity (classic mistake award winner)
- Working under constant and excessive schedule pressure
- Assuming effort estimates can be directly equated to elapsed task durations without any buffers or room for non-productive time
- Failure to manage management or customer expectations
- Planning is seen as the Project Manager’s responsibility rather than a team activity
- Failure to break a large scale master plan into more manageable pieces that can be delivered incrementally
- Team commitments themselves to a schedule without first getting corresponding commitments from other groups and stakeholders who also have to commit to the schedule (aka schedule suicide)
- Unclear roles and responsibilities led to confusion and gaps
- Some team members are allowed to become overloaded resulting in degraded performance in critical areas of the project while others are underutilized
- Requirements are never prioritized resulting in team focusing energies on lower priority items instead of high priority work
- Failure to include appropriate culture change activities as part of the project plan (classic mistake award winner)
- Failure to provide sufficient user training when deploying the product produced by the project into its operational environment (classic mistake award winner)
- Failure to build training or ramp up time into the plan
- Change requests are handled informally without assessing their implications or agreeing to changes in schedule and budget.
- Failure to think ahead and to foresee and address potential problems (Classic mistake award winner)
- Risk management is seen as an independent activity rather than an integral part of the planning process
- Risk, problems and issues become confused as a result team isn’t really doing risk management.
Architecture and design
- Allowing a pet idea to become the chosen solution without considering if other solutions might better meet the project’s overall goal
- Teams starts developing individual components without first thinking through an overall architecture or how the different components will be integrated together. That lack of architecture then results in duplication of effort, gaps, unexpected integration costs and other inefficiencies
- Failure to take into account non-functional requirements when designing a product, system or process (especially performance requirements) results in a deliverable that is operationally unusable
- Poor architecture results in a system that is difficult to debug and maintain
- Being seduced into using leading edge technology where it is not needed or inappropriate
- Developer “gold plating” (developers implement the Rolls Royce version of a product when a Chevy was all that was needed)
- Trying to solve all problems with a specific tool simply because it is well understood rather than because it is well suited to the job in hand
- New tools are used by the project team without providing the team with adequate training or arranging for appropriate vendor support.
Configuration and information management
- Failure to maintain control over document or component versions results in confusion over which is current, compatibility problems and other issues that disrupt progress
- Failure to put in place appropriate tools for organizing and managing information results in a loss of key information and/or a loss of control.
- Quality requirements are never discussed, thereby allowing different people to have different expectations of what is being produced and the standards to be achieved
- Failure to plan into the project appropriate reviews, tests or checkpoints at which quality can be verified
- Reviews of documents and design papers focus on spelling and grammar rather than on substantive issues
- Quality is viewed simply in terms of testing rather than a culture of working
- The team developing the project’s deliverables sees quality as the responsibility of the Quality Assurance group rather than a shared responsibility (the so called “throw it over the wall” mentality)
- Testing focuses on the simple test cases while ignore the more complex situations such as error and recovery handling when things go wrong
- Integration and testing of the individual components created in the project is left until all development activities are complete rather than doing ongoing incremental ingratiation and verification to find and fix problems early
- Testing in a test environment that is configured differently from the target production, or operational environment in which the project’s deliverables will be used.
Project tracking and management
- Believing that although the team is behind schedule, they will catch up later
- The project plan is published but there is insufficient follow up or tracking to allow issues to be surfaced and addressed early. Those failures result in delays and other knock-on problems
- Bad news is glossed over when presenting to customers, managers and stakeholders (aka “Green Shifting“)
- Dismissing information that might show that the project is running into difficulties (i.e. falling prey to the “confirmation bias”)
- Schedule and budget become the driving force, as a result corners are cut and quality is compromised (pressure to mark a task as complete results in quality problems remaining undetected or being ignored)
- Project is tracked based on large work items rather than smaller increments
- Failure to monitor sub-contractor or vendor performance on a regular basis
- Believing that a task reported by a team member as 90% done really is 90% done (note often that last 10% takes as long in calendar time as the first 90%)
- Believing that because a person was told something once (weeks or months ago), they will remember what they were asked to do and when they were supposed to do it (failure to put in place a system that ensures people are reminded of upcoming activities and commitments).
Decision making problems
- Key decisions (strategic, structural or architectural type decisions) are made by people who lack the subject matter expertise to be making the decision
- When making critical decisions expert advice is either ignored or simply never solicited
- Lack of “situational awareness” results in ineffective decisions being made
- Failure to bring closure to a critical decision results in wheel-spin and inaction over extended periods of time
- Team avoids the difficult decisions because some stakeholders maybe unhappy with the outcome
- Group decisions are made at the lowest common denominator rather than facilitating group decision making towards the best possible answer
- Key decisions are made without identifying or considering alternatives (aka “First Option Adoption“)
- Decision fragments are left unanswered (parts of the who, why, when, where and how components of a decision are made, but others are never finalized) resulting in confusion
- Failure to establish clear ownership of decisions or the process by which key decisions will be made results in indecision and confusion.