Twelve Most Common Reasons Why Projects Fail - PM 360 Consulting
17010
post-template-default,single,single-post,postid-17010,single-format-standard,wp-custom-logo,theme-bridge,woocommerce-no-js,ajax_fade,page_not_loaded,,qode-content-sidebar-responsive,columns-4,qode-theme-ver-11.0,qode-theme-bridge,wpb-js-composer js-comp-ver-5.1.1,vc_responsive

Twelve Most Common Reasons Why Projects Fail

12 Reasons Why Projects Fail

24 Mar Twelve Most Common Reasons Why Projects Fail

Posted at 22:23h in Project management Simplified by
0 Likes

12 Reasons Why Projects Fail

 

“Life is 10% what happens to you and 90% how you react to it.” ― Charles R. Swindoll

 

“If the project gets into trouble its becasue somebody got the plannning wrong”

 

  1. The goal of the project isn’t defined properly
  2. The goal of the project is defined properly, but then changes to it aren’t controlled (Scope Creep)
  3. Not all of the project stakeholders are identified
  4. Stakeholders are identified but win conditions aren’t
  5. The project isn’t planned or estimated properly
  6. The project isn’t led properly (Lack of a Project Manager)
  7. The project is planned / estimated properly but then it isn’t resourced as was planned
  8. The project is planned and there is no contingency in place (15% to 20%)
  9. The expectations of project participants aren’t managed
  10. The project is planned properly but then progress against the plan is not monitored and controlled properly
  11. Project reporting is inadequate or non-existent (Lack of accountability and responsibility amongst project team)
  12. When projects get in to trouble, people believe the problem can be solved by some simple action e.g. work harder, extend the deadline, adding more resources (Brooks Law)

 

(Fast Projects – Fergus O Connell)