So why dev ops? - john clapham

641 views

Published on

Agile Business Conference Talk
http://www.agileconference.org/programme/october-10th-2013/

Published in: Technology, Sports
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
641
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

So why dev ops? - john clapham

  1. 1. Question: Agile's got it covered - so why DevOps? It seems like agile has it all –with only 8 to 14 guiding principles, it offers the promise of better utilisation of creative resource, clarity for stakeholders, faster delivery and happier customers. Over a decade old and agile is all grown up, so why is this DevOps upstart getting so much attention? Drawing on experiences at Nokia Entertainment, this talk looks at what DevOps is and what it brings to business. It looks at how DevOps compliments agile methods, and encourages attention on areas that could easily be overlooked.
  2. 2. Agile's got it covered, so why DevOps? John Clapham Nokia Entertainment
  3. 3. Is this even worth answering?
  4. 4. To grow something you need to understand it’s preferred conditions…
  5. 5. If DevOps is valuable, and different to Agile, understanding will help nurture it.
  6. 6. Step 1: The What of DevOps. Step 2: The Why of DevOps. Step 3: DevOps’ relationship to Agile.
  7. 7. Step 1: The What Of DevOps…
  8. 8. Utah 2001…
  9. 9. DevOps on the other hand…
  10. 10. “A single day to change, two months to Deploy”
  11. 11. “The site is unresponsive - this blatantly hasn’t been tested”
  12. 12. Tensions separate IT Operations and Development…
  13. 13. Tensions separate IT Operations and Development… Stability vs Change
  14. 14. Tensions separate IT Operations and Development… Stability vs Change Ops Culture vs Dev Culture
  15. 15. …not to mention a few technical challenges.
  16. 16. Culture Automation Monitoring Sharing
  17. 17. Towards a culture of collaboration and trust.
  18. 18. Automation, of almost everything.
  19. 19. Monitoring of code, integration, systems, and progress.
  20. 20. Sharing; of knowledge, feedback and responsibility.
  21. 21. Step 2: The Why Of DevOps…
  22. 22. Time to Market.
  23. 23. Stability AND change.
  24. 24. Quality.
  25. 25. Cost and Efficiency.
  26. 26. Stealth Benefits?
  27. 27. Motivation.
  28. 28. Autonomy, Mastery, Purpose
  29. 29. Talent – attraction, retention.
  30. 30. Step 3: DevOps’ relationship to Agile…
  31. 31. You can tackle anything with agile…
  32. 32. A genuine need, or a sales gimmick?
  33. 33. Lean and Flow
  34. 34. Does it scale?
  35. 35. Patterns for common problems.
  36. 36. Community & Enthusiasts
  37. 37. Reflections…
  38. 38. Agile’s got it covered - so why DevOps?
  39. 39. Agile is ultimately about learning…
  40. 40. Confucius: “By three methods we may learn wisdom: First, by reflection, which is noblest; Second, by imitation, which is easiest; Third by experience, which is the bitterest.”
  41. 41. DevOps is a neat package
  42. 42. It covers what…
  43. 43. It covers what…and how
  44. 44. It hints at scale
  45. 45. …and focuses on culture
  46. 46. DevOps gets results*
  47. 47. *( Apply judiciously, not to be taken at meal times, results will vary, there is a risk of point fix and over investment )
  48. 48. Thanks! @johnC_Bristol
  49. 49. Further reading… DevOps at Nokia Entertainment http://www.infoq.com/articles/monthly-devops-01-nokia Nokia Music http://www.nokia.com/gb-en/apps/app/nokia-music/
  50. 50. Picture Credits Suspension Bridge & Whisky Barrels http://www.flickr.com/photos/uk_pictures/3483034558/ Barley, Ian Britton http://www.flickr.com/photos/freefoto/729511482/ Agave, Mike Jorgensen http://www.flickr.com/photos/mikejorgensen/137624042/ Snowbird Mountains, http://www.flickr.com/photos/johnandchristina/2438275715/ Frustration http://www.flickr.com/photos/50325419@N08/5661682250/ Snake Sign http://www.flickr.com/photos/matthigh/3312783047/

×