Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Fixing Your Org By Continually Breaking It

6,479 views

Published on

DevOps Days Austin 2015 Presentation

Published in: Software

Fixing Your Org By Continually Breaking It

  1. 1. FIXINGYOUR ORG BY CONTINUALLY BREAKING IT J. PAUL REED RELEASE ENGINEERING APPROACHES DEVOPS DAYS AUSTIN 2015
  2. 2. J. PAUL REED AKA “The Sober Build Engineer” @SoberBuldEng on Principal at Release Engineering Approaches Chief Delivery Officer at Praxisflow 15+ years in build/ release engineering
  3. 3. ALSO AVAILABLE ON ITUNES www.theshipshow.com @ShipShowPodcast @eciramella @buildscientist @cheeseplus @sascha_d @petecheslock@SonOfGarr @beerops
  4. 4. ALSO: I AM NOT THIS GUY
  5. 5. ALSO NOT THIS GUY
  6. 6. HEARD OF THIS BOOK?
  7. 7. IMPORTANT DETAILS The Three Ways of DevOps The Four Types of IT Work Interviews with The Business™
  8. 8. 3 WAYS RECAP 1. Systems Thinking 2.Amplify Feedback Loops 3.Culture of Continuous Experimentation & Learning
  9. 9. http://itrevolution.com/the-three-ways-principles-underpinning-devops/ SYSTEMS THINKING
  10. 10. http://itrevolution.com/the-three-ways-principles-underpinning-devops/ AMPLIFY FEEDBACK LOOPS
  11. 11. http://itrevolution.com/the-three-ways-principles-underpinning-devops/ WE FORGET THE 3RD WAY
  12. 12. http://itrevolution.com/the-three-ways-principles-underpinning-devops/ FEEDBACK “BOOMERANGS”
  13. 13. MIND TOO BLOWN?
  14. 14. MIND TOO BLOWN?
  15. 15. MIND TOO BLOWN? #DevOps
  16. 16. “BRB,TOO BUSY TO IMPROVE”
  17. 17. “WELL,THAT USED TO BE OUR WEBSITE...”
  18. 18. RARE IN THE WILD
  19. 19. CONTINUOUS...
  20. 20. CONTINUOUS... Integration
  21. 21. CONTINUOUS... Integration Delivery
  22. 22. CONTINUOUS... Integration Delivery Deployment
  23. 23. CONTINUOUS... Integration Delivery Deployment Improvement?
  24. 24. The evidence of the last 20 years indicates that trying to copy or reproduce another company’s tools, techniques, or principals does little to change an organization’s culture. — Mike Rother
  25. 25. DevOps
  26. 26. Culture Is Not Important...
  27. 27. ON “COMPANY” “CULTURE”
  28. 28. ON “COMPANY” “CULTURE” “Move fast, break things.”*
  29. 29. ON “COMPANY” “CULTURE”
  30. 30. ON “COMPANY” “CULTURE” “Context, not control.”
  31. 31. ON “COMPANY” “CULTURE”
  32. 32. ON “COMPANY” “CULTURE” “A ‘Have Coffee’ culture”
  33. 33. Culture Is Not Important, but Cultural Alignment is critical
  34. 34. EXPERIMENTS, IN JUST FOUR EASY STEPS!
  35. 35. EXPERIMENTS OVER THE LONG TERM
  36. 36. DETAILS, DETAILS Target != Target Condition
  37. 37. “Let’s do The DevOps!” Retrospectives Continuous Integration Kanban Continuous DeliveryConfiguration Management Developers Carry the Pagers! Docker Docker Docker
  38. 38. THE IMPORTANCE OF A TARGET CONDITION (not your idea versus my idea about what we could do) and brings people’s efforts into alignment. — Rother [A] target condition... creates a challenge that depersonalizes a situation
  39. 39. #DevOpsDays @SoberBuildEng
  40. 40. #DevOpsDays @SoberBuildEng
  41. 41. CYNEFIN SIDEBAR
  42. 42. CYNEFIN SIDEBAR
  43. 43. Sample Experiments
  44. 44. MAN ON THE MOON
  45. 45. WEEKLY MEETING OF SUCK
  46. 46. TAKING TIME TO LOOK IN THE MIRROR
  47. 47. GAME ON!
  48. 48. PEBBLE THEORY OF CHANGE
  49. 49. PEBBLE THEORY OF CHANGE Drain until you can see the rocks, i.e. obstacles; then remove those obstacles
  50. 50. PEBBLE THEORY OF CHANGE Drain until you can see the rocks, i.e. obstacles; then remove those obstacles Don’t target the rocks you “know” are there
  51. 51. PEBBLE THEORY OF CHANGE Drain until you can see the rocks, i.e. obstacles; then remove those obstacles Don’t target the rocks you “know” are there Don’t dredge up the whole swamp
  52. 52. [T]he ability of your company to be competitive and survive lies not so much in solutions themselves, but in the capability of the people in your organization to understand a situation and develop solutions. — Rother
  53. 53. Operability?
  54. 54. In Our Software Resilience Microservices Maintainability
  55. 55. In Our Teams Resilience Independently Empowered Teams/Actors Sustainability
  56. 56. Resilience. WHY?
  57. 57. Resilience. WHY? Code Systems Teams Organizations People
  58. 58. J. Paul Reed soberbuildengineer.com @SoberBuildEng www.release-approaches.com Simply Ship. Every Time. Anonymous feedback: sayat.me/jpaulreed
  59. 59. Adoption of Agile & DevOps methodologies is a journey, and every person and organization’s journey is going to be different. -J. Paul Reed DevOps inPractice J. Paul Reed http://www.oreilly.com/webops-perf/free/devops-in-practice.csp

×