Install Toolbar

Site Map

See Article Categories

Reasons Why Projects Fail

By Tom Carlos, PMP
Chessboard with Checkmate Position

In a perfect world every project would be "on time and within budget." But reality (especially the proven statistics) tells a very different story. It's not uncommon for projects to fail. Even if the budget and schedule are met, one must ask "did the project deliver the results and quality we expected?" True project success must be evaluated on all three components. Otherwise, a project could be considered a "failure."

Have you ever seen a situation where projects begin to show signs of disorganisation, appear out of control, and have a sense of doom and failure? Have you witnessed settings where everyone works in a silo and no one seems to know what the other team member is doing? What about team members who live by the creed "I'll do my part (as I see fit) and after that, it's their problem." Even worse is when team members resort to finger-pointing. Situations similar to these scenarios point to a sign that reads "danger." And if you read the fine print under the word "danger" it reads, "your project needs to be brought under control or else it could fail."

When projects begin to show signs of stress and failure, everyone looks to the project manager for answers. It may seem unfair that the burden of doom falls upon a single individual. But this is the reason why you chose to manage projects for a living! You've been trained to recognise and deal with these types of situations.

There are many reasons why projects (both simple and complex) fail; the number of reasons can be infinite. However, if we apply the 80/20 rule the most common reasons for failure can be found in the following list:

Poorly managed Undefined objectives and goals Lack of management commitment
Lack of a solid project plan Lack of user input Lack of organisational support
Centralised proactive management initiatives to combat project risk Enterprise management of budget resources Provides universal templates and documentation
Poorly defined roles and responsibilities Inadequate or vague requirements Stakeholder conflict
Team weaknesses Unrealistic timeframes and tasks Competing priorities
Poor communication Insufficient resources (funding and personnel) Business politics
Overruns of schedule and cost Estimates for cost and schedule are erroneous Lack of prioritisation and project portfolio management
Scope creep No change control process Meeting end user expectations
Ignoring project warning signs Inadequate testing processes Bad decisions

Even with the best of intentions or solid plans, project can go awry if they are not managed properly. All too often, mishaps can occur (and usually do). This is when the project manager must recognise a warning sign and take action. If you understand the difference between symptoms and problems and can spot warning signs of project failure, your training will help you take steps to right the ship before it keels over. Yes, it's the project manager's responsibility to correct the listing no one else. In addition to applying the processes and principles taught in project management class, you can also use your personal work skills of communication, management, leadership, conflict resolution, and diplomacy to take corrective action.

During the course of managing a project, the project manager must monitor activities (and distractions) from many sources and directions. Complacency can easily set in. When this happens, the process of "monitoring" breaks down. This is why the project manager must remain in control of a project and be aware of any activity which presents a risk of project failure. Yes, this is why "you are paid the big bucks."

Tom Carlos has over 20 years of cumulative experience in business, technical, and training environments. He is a Certified Project Management Professional (PMP) and member of the Sacramento Valley PMI Chapter. For other articles on similar subject, you can visit Thomas Carlos Consulting or contact him at tom@carlosconsulting.com

Speech bubble Don't forget to leave your comments below.

Comments (1)

PMP is ok but...
In my experience as a software developer for a number of years, agile is best suited for software projects. I had been in a company where managers are PMP certified yet software projects fail big-time. Also, look at the FBI's Sentinel project on how Agile saved the project. I am not saying that PMP is bad, but I just feel that in the software development arena, PMP is not the first choice for handling projects.
#1 - asd - Monday 6th January 2014 - 11:00
Name
Email (will not appear online)
Title
Comment

Article Categories

Avoid Failed Projects
The biggest problems that projects face are inadequate definition, scope and planning. How many projects have you been involved in that ran perfectly?

Don't Try This at Home: Seven Rules to Guarantee Project Failure
Looking for a new way to get really famous, or infamous, at the office? Try these seven money-back guaranteed ways to really mess up your next project.

Why Does Project Management Fail?
It must be remembered that project management is first and foremost a philosophy of management, not an elaborate set of tools and techniques.

Reducing Risk and Increasing the Probability of Project Success
IT systems are at the heart of modern business and the development of new software applications and maintenance of existing systems are critical to productivity and profitability.

Information Icon Meeting Challenges

The POST method is a way to give clarity at the beginning of a meeting.

  • Purpose: What is the purpose of the meeting?
  • Objective: What are you trying to achieve in the meeting, what does success look like?
  • Structure: What is the structure of the meeting we are having?
  • Timing: How much time is allocated to the meeting?

Speech bubble Discover our online forum where you can ask questions, find out tips from other people and share your experience.