Why Web Projects Fail

1,352 views

Published on

Graham Oakes: Why web project fails, and what we can do about it (J Boye), november 2009 (Cascadis Congres, Arnhem)

1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total views
1,352
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
27
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

Why Web Projects Fail

  1. 1. Why web projects fail… … and what you can do about it Why info projects fail Oct 2009 1
  2. 2. Why info projects fail Oct 2009 2 hendriko
  3. 3. Projects Fail Why info projects fail Oct 2009 4 pri.studio360
  4. 4. Failure can be ambiguous Why info projects fail Oct 2009 5 Bitman
  5. 5. Poor link to organisational objectives Why info projects fail Oct 2009 8 lsie esq.
  6. 6. Unclear scope and requirements Why info projects fail Oct 2009 9 Green-Ghost
  7. 7. Lack of executive commitment / involvement Why info projects fail Oct 2009 10 jurvetson
  8. 8. Unmanaged change Why info projects fail Oct 2009 11 Hamed Saber
  9. 9. Unmanaged risks (often undiscussables) Why info projects fail Oct 2009 12 qmnonic
  10. 10. Poor communications (internal and external) Why info projects fail Oct 2009 13 aturkus
  11. 11. Unrealistic estimates, schedules, staffing, tools Why info projects fail Oct 2009 14
  12. 12. Complex stakeholders Deal with intangibles High visibility Immature foundations Web Projects Merge into operations Anyone can build a “website”… …Why infonot one that scales, runs reliably, etc but projects fail Oct 2009 15 pri.studio360
  13. 13. We lose touch with reality as we estimate, negotiate, track progress, … Project failures become apparent when we run into reality Note: The failure actually happened long before it became apparent. To avoid disaster, identify the failure while it can be remedied and learned from. Complexity, optimism, power games, cognitive biases, fear all exacerbate the problem Much project management is about building mechanisms to Why infokeep fail touch with reality projects in Oct 2009 16 Simon Schoeters
  14. 14. Because projects are run by people… Why don’t we recognise failures earlier? Why info projects fail Oct 2009 17 Marcin Wichary
  15. 15. Overconfidence Why info projects fail Oct 2009 18 jack_spellingbacon
  16. 16. Oversimplification Why info projects fail Oct 2009 19 futureatlas.com
  17. 17. Avoiding pain Why info projects fail Oct 2009 20 annia316
  18. 18. Confirmation bias Why info projects fail Oct 2009 21 Antoaneta
  19. 19. Why info projects fail Repetition bias Oct 2009 22 Madzik
  20. 20. Perceptual biases Why info projects fail Oct 2009 23 condour
  21. 21. Why info projects fail Oct 2009 24 lostajy
  22. 22. Control parameters Baseline Criteria Reference Feedback Models to improve reference models Review execution Inputs Outputs Artefacts & other Analysis Loop items to review, plus Go / No -go Improved supporting details. decision. artefacts. Recommendations to improve review artefacts Reviews Why info projects fail Oct 2009 25 AlphaGeek
  23. 23. Iterations Why info projects fail Oct 2009 26 oskay
  24. 24. Metrics Why info projects fail Oct 2009 27 kakutani
  25. 25. Plan for change (Plan as guide, not crutch) Why info projects fail Oct 2009 28 sidstamm
  26. 26. Separate project from Why info projects fail operations Oct 2009 29
  27. 27. Communicate Why info projects fail Oct 2009 30 ky_olsen
  28. 28. Summary Two types of failure a) Failure you can learn from b) Failure that kills you  We engage with risks to achieve rewards  Sometimes the risks win  Complexity and intangibility exacerbate the risks  We recognise failure when we run into reality  If we keep in touch with reality, the bump is less dramatic  Watch reality, not the plan Why info projects fail Oct 2009 31
  29. 29. Thank You Why info projects fail Oct 2009 32
  30. 30. Graham Oakes Ltd  Making sense of technology…  Many organisations are caught up in the complexity of technology and systems.  This complexity may be inherent to the technology itself. It may be created by the pace of technology change. Or it may arise from the surrounding process, people and governance structures.  We help untangle this complexity and define business strategies that both can be implemented and will be adopted by people throughout the organisation and its partner network. We then help assure delivery of implementation projects.  Clients…  Cisco Worldwide Education – Architecture and research for e-learning and educational systems  Council of Europe – Systems for monitoring compliance with international treaties; e-learning systems  Dover Harbour Board – Systems and architecture review  EUMETSAT – ECM Roadmap  MessageLabs – Architecture and assurance for partner management portal  National Savings & Investments – Helped NS&I and BPO partner develop joint IS strategy  The Open University – Enterprise architecture, CRM and product development strategies  Oxfam – Strategy for content management, CRM, e-Commerce  Thames Valley Police – Internet Consultancy  Sony Computer Entertainment – Global process definition  Amnesty International, Endemol, tsoosayLabs, Vodafone, … Why info projects fail Oct 2009 33

×