Why Projects Fail: Obstacles and Solutions
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Why Projects Fail: Obstacles and Solutions

on

  • 14,294 views

Presented as part of a governance and IT failures work at Babson College - Center for Information Management Systems (CIMS).

Presented as part of a governance and IT failures work at Babson College - Center for Information Management Systems (CIMS).

Statistics

Views

Total Views
14,294
Views on SlideShare
12,971
Embed Views
1,323

Actions

Likes
18
Downloads
1,269
Comments
2

17 Embeds 1,323

http://blogs.zdnet.com 442
http://www.zdnet.com 359
http://spf13.com 252
http://pontogp.wordpress.com 114
http://www.enterpriseirregulars.com 51
http://www.slideshare.net 43
http://davepress.net 30
http://gestionprojetauto.wordpress.com 13
http://translate.googleusercontent.com 6
http://www.iweb34.com 3
https://www.linkedin.com 2
http://localhost 2
http://www.linkedin.com 2
http://1.1.hidemyass.com 1
http://webcache.googleusercontent.com 1
http://lorenaticlorena.blogspot.com 1
https://twitter.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Mike, thanks for another great resource. I like the point about increasing collaboration capabilities. We are evaluating Google Wave as a new tool for this, as we currently use Google sites and docs across the organization. Also excited about Salesforce chatter for our internal initiatives in the future.

    Have a great day!

    Garry AKA @darthgarry
    Are you sure you want to
    Your message goes here
    Processing…
  • I like it very much ! Thank you!
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Why Projects Fail: Obstacles and Solutions Presentation Transcript

  • 1. Why Projects Fail: y j Obstacles and Solutions Michael Krigsman Asuret, Inc. 617-905-5950 mkrigsman@asuret.com k ig @ t Twitter: @mkrigsman © Copyright 2009 Asuret Inc. All rights reserved.
  • 2. Failure is common: 30-70% of projects are late, over-budget, or don’t meet expectations. © Copyright 2009 Asuret Inc. All rights reserved.
  • 3. Total failure worldwide: trillions of dollars (SWAG*) *silly wild ass guess based on independent research wild-ass http://blogs.zdnet.com/projectfailures/?p=6142 © Copyright 2009 Asuret Inc. All rights reserved.
  • 4. Failures persist despite millions invested in i prevention. Wh ? ti Why? © Copyright 2009 Asuret Inc. All rights reserved.
  • 5. We ignore warning signs © Copyright 2009 Asuret Inc. All rights reserved.
  • 6. Cost to projects is high high. Impact on the business is higher higher. © Copyright 2009 Asuret Inc. All rights reserved.
  • 7. Nightmare Ni ht Scenario Levis can’t fill orders for one week = 98% decline in quarterly profits http://blogs.zdnet.com/projectfailures/?p=917 http://blogs.zdnet.com/projectfailures/?p=935 © Copyright 2009 Asuret Inc. All rights reserved. Image © LS&CO
  • 8. Understanding failure
  • 9. Project management is not enough © Copyright 2009 Asuret Inc. All rights reserved.
  • 10. Process is not enough  Failures persist despite ITIL, PMI, CMM, and other methodologies  Project management tools do not stop failure  Nor does Project Portfolio Management  Projects f d d ith t b i P j t funded without business case, executive ti sponsorship and so on  Distortions: poor j g p judgment, p , politics, silos, , , and personal agendas  Extreme case: “Successful” process / failed outcome © Copyright 2009 Asuret Inc. All rights reserved.
  • 11. Three root causes of failure  Business vulnerabilities  Alignment mismatches  Devil’s Triangle relationships © Copyright 2009 Asuret Inc. All rights reserved.
  • 12. Business vulnerabilities, not technology, cause the problems © Copyright 2009 Asuret Inc. All rights reserved.
  • 13. Case study: Oak Park, IL  Change management  Project management  Third party relationships © Copyright 2009 Asuret Inc. All rights reserved.
  • 14. Oak Park: Complete abandonment  Cost: $2M  Time frame: complete abandonment after 5-year project  Software vendor: PeopleSoft  Project goal: Replace payroll and financials  Failure: Accounting and finance errors, such as vendors paid twice  Causes: C  Lack of Oak Park sophistication regarding enterprise software process, scope, costs over time, management, and so on  Low-skill finance employees, lacking basic computer skills, did not enter data into system  Insufficient change management and user training http://blogs.zdnet.com/projectfailures/?p=1304 http://blogs.zdnet.com/projectfailures/?p=1358 © Copyright 2009 Asuret Inc. All rights reserved.
  • 15. Alignment mismatches drive poor decisions Poor communication, hidden agendas, and conflicting measures of success create gaps  Information silos  IT / lines of business  Internal / external groups  Business needs become disconnected from strategy and planning t t g d l i g  Execution then suffers © Copyright 2009 Asuret Inc. All rights reserved.
  • 16. Management vs. vs IT and testing © Copyright 2009 Asuret Inc. All rights reserved.
  • 17. © Copyright 2009 Asuret Inc. All rights reserved.
  • 18. J.Crew: Management accepts blame  Cost: $3M plus lost sales and dissatisfied customers  Failure: Impaired ability to capture, process, ship, and service orders  Causes:  Aggressive i A i internal planning and schedule l l i d h d l  Insufficient testing of new system before replacing old  Management accepted responsibility  Plausible scenario: management pressured IT to accept aggressive schedule http://blogs.zdnet.com/projectfailures/?p=1015 © Copyright 2009 Asuret Inc. All rights reserved.
  • 19. Devil’s Triangle Dysfunctional industry structure creates overlapping and conflicting agendas g g
  • 20. Devil’s Triangle Conflicts of interest are embedded in the enterprise software industry (customer gets fleeced) Confused buyers Silos and internal conflicts Wacky system integrators Customer success vs. consulting revenue Schizophrenic software vendors Loyalties split between customers and integrators © Copyright 2009 Asuret Inc. All rights reserved.
  • 21. [W]hen you’re marching through hell, you re hell just keep marching. Charles Burbridge g LAUSD’s CFO (LA Times, 3/19/07) © Copyright 2009 Asuret Inc. All rights reserved.
  • 22. LAUSD payroll broken: teachers suffer  Budget: $95M; Expected: $135M  System integrator: Deloitte Consulting  Software vendor: SAP  Goal: Replace payroll system  Failure: Teachers not paid  Causes:  School payroll is inherently complex  Roll out and testing were likely flawed (Union: system not run in parallel)  Complicated work rules  Deloitte did not press LAUSD for complete information  SAP did not want to interfere with Deloitte’s account http://blogs.zdnet.com/projectfailures/?p=130 http://blogs.zdnet.com/projectfailures/?p=436 http://blogs.zdnet.com/projectfailures/?p=576 © Copyright 2009 Asuret Inc. All rights reserved.
  • 23. Preventing failure
  • 24. Observe warning signs  Ambiguous or diffuse project ownership  Stakeholder complexity  Who’s calling the shots?  Conflicts of interest  Inconsistencies (hardest t discern i advance) I i t i (h d t to di in d )  Are stakeholders engaged?  Is management in denial? g  Business case clear? © Copyright 2009 Asuret Inc. All rights reserved.
  • 25. Governance beyond IT  What problem does the project solve?  Who is the project champion?  Are stakeholders committed?  What PM toolbox are you going to use and what drives it (procurement i ( t issues)? )?  How will the project be governed (who, how, when)?  How will the project be controlled (planning monitoring, (planning, monitoring reporting)?  How will success be judged or measured? (who when, how) © Copyright 2009 Asuret Inc. All rights reserved.
  • 26. Extending into the enterprise…  Share knowledge and lessons learned to improve success rates  Embed innovation around IT project success in the organization  Evaluate your organization’s collaboration capabilities organization s © Copyright 2009 Asuret Inc. All rights reserved.
  • 27. And beyond  Increase appropriate communication to reduce information silos  Connect social networks to support continuous organizational improvement  Facilitate rapid effective and ethical decision-making rapid, effective, decision making  Align IT with measurable business results  Change p j g project culture, not corporate culture , p © Copyright 2009 Asuret Inc. All rights reserved.
  • 28. Which all sounds good…
  • 29. Talk T lk is cheap
  • 30. Preventing failure Is easier said than done
  • 31. First, recognize that vulnerabilities exists
  • 32. Factual data is essential © Copyright 2009 Asuret Inc. All rights reserved.
  • 33. Facilitate consensus across silos Use non-threatening techniques to:  Avoid bias  Remove emotion and political pressures e o e e ot o a d po t ca p essu es  Create organizational consensus and enhance collaboration  Leverage collective intelligence inside the organization © Copyright 2009 Asuret Inc. All rights reserved.
  • 34. Key drivers of success © Copyright 2009 Asuret Inc. All rights reserved.
  • 35. Measure indirectly Simple questions, range of responses, and importance © Copyright 2009 Asuret Inc. All rights reserved.
  • 36. Evidence-based planning  Raise profile of success factors  Target specific issues for focus a get spec c ssues o ocus  Create concrete plans  Coordinate action against plan  Rinse and repeat as needed
  • 37. Simulation and Analysis © Copyright 2009 Asuret Inc. All rights reserved.
  • 38. Key Lessons  Governance: people, collaboration, and responsibility  Measurement and diagnosis are prerequisites for future success  Consolidating / aggregating lessons learned is essential to achieve continuous improvement  Pinpoint specific recommendations  Drive toward consensus  Long-term solution  Look beyond project management  Raise awareness of real vulnerabilities  Engage stakeholders and sponsors © Copyright 2009 Asuret Inc. All rights reserved.
  • 39. For more information contact: Michael Krigsman, CEO Email: mkrigsman@asuret.com Web: http://asuret.com Blog: http://blogs.zdnet.com/projectfailures Twitter: http://twitter com/mkrigsman http://twitter.com/mkrigsman + 1 (617) 905-5950 © Copyright 2009 Asuret Inc. All rights reserved.