ITMPI FLAT 003
Main Menu
Home / Project Management / Risk Management / 10 Reasons Why Projects Fail

10 Reasons Why Projects Fail

If one of your projects has ever failed, then you are already painfully aware of why projects fail. But these dreary topics bear repeating from time to time, because complacency breeds risk. In a post at Project Bliss, Leigh Espy reminds you of 10 reasons why projects fail, so you can stay vigilant about them:

  1. Unclear scope
  2. Not enough customer involvement
  3. Stakeholder disengagement
  4. Poor scheduling
  5. Lack of team input and buy-in
  6. Poorly planned costs
  7. Team accountability
  8. Poor risk management
  9. Poor communication
  10. Lack of monitoring and controlling

Confront Your Challenges

Running a project without clear scope is live driving a car without windshield wipers in a thunderstorm—something is going to explode. Lack of customer involvement creates a similar problem—murky goals, or setting goals that do not actually agree with what the customer needs. By comparison, lack of stakeholder support creates a different problem; it might mean that nobody important ever generates enthusiasm for the project. Morale will run low on a project whose existence solicits shrugs from everyone who hears about it.

Several of the problems Espy addresses ultimately fall under the category of poor planning. Poor scheduling, poor cost calculations, and poor risk management fall into that category at least. Other problems fall under the category of generally poor team management. For instance, you must be able to motivate your team to see the value in a project if you are to expect them to put their best work into it. You must also create equal accountability across the team, and ensure team roles are clear and not unnecessarily redundant.

Finally, about lack of monitoring and controlling, Espy concludes this:

Additionally, there will be times when the team needs support and guidance from you as the project manager due to unforeseen roadblocks or conflicts. For example, if management assigns team members to other projects without giving clear priority, the PM must help resolve this – especially if the workload exceeds team capacity. The project that manager is like an orchestra conductor who needs to ensure everyone continues to play on key and follow the written music.

You can view the original post here: http://projectbliss.net/reasons-why-projects-fail/

About John Friscia

John Friscia is the Editor of Computer Aid's Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

How to Identify and Remove Resistance to Change

Most people don’t like having their workplace rhythm disrupted by change. The uncertain future that …

Leave a Reply

Your email address will not be published. Required fields are marked *