Gaining Momentum with Agile at NOPSA

369 views

Published on

Walkthrough of how National Offshore Petroleum Safety Authority (NOPSA) went Agile

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
369
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Gaining Momentum with Agile at NOPSA

  1. 1. Perth - Gaining Momentum with Agile Thursday, 29 April 2010 © ThoughtWorks 2010 Introduction Angela Ferguson, Principal Consultant ThoughtWorks Speakers John Townsend, Chief Information Officer Ian Crawford, Senior Information Officer National Offshore and Petroleum Safety Authority Mike Allen, Senior Project Manager MLC
  2. 2. NOPSA gets Agile Or … how we learned to stop worrying and trust the card wall. © ThoughtWorks 2010
  3. 3. What is NOPSA? © ThoughtWorks 2010
  4. 4. West Atlas and Montara wellhead, August 2009 © ThoughtWorks 2010
  5. 5. No fatalities © ThoughtWorks 2010
  6. 6. Deepwater Horizon, April 2010
  7. 7. 11 Crew missing
  8. 8. Project Survival © ThoughtWorks 2010
  9. 9. Unpredictable Change © ThoughtWorks 2010
  10. 10. © ThoughtWorks 2010 Unpredictable Change
  11. 11. Process Uncertainty © ThoughtWorks 2010
  12. 12. Rapid Feedback © ThoughtWorks 2010
  13. 13. User Acceptance © ThoughtWorks 2010
  14. 14. © ThoughtWorks 2010 User Acceptance
  15. 15. © ThoughtWorks 2010 User Acceptance
  16. 16. © ThoughtWorks 2010 User Acceptance
  17. 17. Fit For Purpose
  18. 18. Flexibility Sliders © ThoughtWorks 2010
  19. 19. Going to the Market
  20. 20. The Sponsor’s View – Scope and Budget © ThoughtWorks 2010
  21. 21. The Burn-Up Chart © ThoughtWorks 2010
  22. 22. Showcases
  23. 23. The Subject Matter Expert’s View
  24. 24. Direct Control © ThoughtWorks 2010
  25. 25. LoFi Prototyping, Rapid Development © ThoughtWorks 2010
  26. 26. Prioritisation and Scope
  27. 27. Focus on the Domain, not Documentation
  28. 28. What characteristics of NOPSA were helpful?
  29. 29. What Worked? •  A bias for good practice © ThoughtWorks 2010
  30. 30. What Worked? •  No legacy to protect © ThoughtWorks 2010
  31. 31. What Worked? •  A preference for discussion over documentation © ThoughtWorks 2010
  32. 32. What Worked? •  Delegated authority © ThoughtWorks 2010
  33. 33. Why is Agile gaining momentum in NOPSA? © ThoughtWorks 2010
  34. 34. Why is Agile gaining momentum in NOPSA? •  incremental delivery © ThoughtWorks 2010
  35. 35. Why is Agile gaining momentum in NOPSA? •  incremental delivery •  design by the SMEs © ThoughtWorks 2010
  36. 36. Why is Agile gaining momentum in NOPSA? •  incremental delivery •  design by the SMEs •  user acceptance © ThoughtWorks 2010
  37. 37. Why is Agile gaining momentum in NOPSA? •  incremental delivery •  design by the SMEs •  user acceptance •  change tolerance © ThoughtWorks 2010
  38. 38. Why is Agile gaining momentum in NOPSA? •  incremental delivery •  design by the SMEs •  user acceptance •  change tolerance •  fewer and earlier surprises © ThoughtWorks 2010
  39. 39. RMS, the movie © ThoughtWorks 2010
  40. 40. WHY? © ThoughtWorks 2010
  41. 41. BENEFITS © ThoughtWorks 2010
  42. 42. CHALLENGES © ThoughtWorks 2010
  43. 43. HIGHLIGHTS © ThoughtWorks 2010
  44. 44. LESSONS LEARNED © ThoughtWorks 2010
  45. 45. MYTHS © ThoughtWorks 2010
  46. 46. OBSERVATIONS © ThoughtWorks 2010
  47. 47. Perth - Gaining Momentum with Agile Thursday, 29 April 2010 © ThoughtWorks 2010 www.thoughtworks.com

×