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.

DevOps beyond the Tools

1,566 views

Published on

DevOps is mainstream - at least the tools, the automation and the metrics. But what happened to DevOps Culture? Does it still matter? If yes - how do we achieve it?

Published in: Technology

DevOps beyond the Tools

  1. 1. DevOps beyond the tools
  2. 2. Johann, Mayflower We do agile stuff, too. (a lot, like no budgets, open books, no job titles, team selected roles, reverse accountability, peer feedback, slacktime, (mostly) open salaries, peer salaries, sociocracy, stuff)
  3. 3. 10 Years of DevOps! Who else was there, back in the days?
  4. 4. DevOps Born as „Agile Operations“ in 2009 (3rd grade today)
  5. 5. Gartner Group, 2011
  6. 6. 2017: DevOps still growing
 early majority
  7. 7. Accenture, 2014 No longer can applications be ‚built‘ as one distinctive activity and ‚maintained‘ as another. Engineering Innovations such as Agile and DevOps enable software to be continuously delivered and evolve as business needs change.
  8. 8. Cap Gemini, 2014 Development to Operations (DevOps) implementations will increase significantly during 2015-2016.
  9. 9. Gartner Group, 2015 Gartner Says By 2016, DevOps Will Evolve From a Niche to a Mainstream Strategy Employed by 25 Percent of Global 2000 Organizations.
  10. 10. Puppet Labs, 2016
  11. 11. Puppet Labs, 2015 It’s their use of DevOps practices that sets these top performers apart from the pack.
  12. 12. Do you even DevOps?
  13. 13. Who is „the Devops“ in a team / company
  14. 14. Is there a 
 „DevOps Team“ in Your Company?
  15. 15. (Ok, that’s two anti patterns 
 for a start.)
  16. 16. Let’s figure out Your actual DevOps Hipster Score
  17. 17. Puppet, CF-Engine or Chef? Please add 1 Hipster Point
  18. 18. Ansible, SaltStack, Fabric? Please add 3 DevOps Hipster Points
  19. 19. Docker Just 1 DevOps Hipster Point - it’s 2017
  20. 20. Kubernetes / DC/OS-Mesos 
 / Swarm Please add 5 DevOps Hipster Points
  21. 21. drone.io GoCD Spinnaker Please add 5 DevOps Hipster Points
  22. 22. ChatOps? NixOS? Please add 5 DevOps Hipster Points
  23. 23. 0 Points? 1-5 Points? 6-10 Points? >10 Points?
  24. 24. How often do you deploy? 1 2 3 4 5 >= 1 time daily multiple times a week at the end of each sprint once a month? every 3/6 months
  25. 25. New features into production 1 2 3 4 5 > 1 per day >2 per week 7-12 each sprint 1-5 per month some each year
  26. 26. Monitoring? Reporting?
  27. 27. State of DevOps: - Automation: check - CI: check - CD: check - Metrics: check
  28. 28. When DevOps started, it was about …
  29. 29. Culture Automation Measurement Sharing
  30. 30. Culture Automation Measurement Sharing
  31. 31. Hey, it works for me. Why bother about 
 culture & sharing? Culture Automation Measurement Sharing
  32. 32. „Even with the best tools, DevOps is just another buzzword if you don’t have the right culture.“
  33. 33. Ok, but what is the right culture?
  34. 34. „DevOps is just short for DevProductSupportNetSecBizOps.
  35. 35. Vice President Product Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant CEO
  36. 36. Vice President Product Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant Specialization Effective Control Efficiency Economy Expansion CEO
  37. 37. Vice President Product Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant Strategy Company Goals Department Goals Individual Goals & KPIs CEO
  38. 38. Vice President Product Vice President Development Vice President Quality Vice President Maintenance
  39. 39. Fingerpointing
  40. 40. Product Development Quality Maintenance Silo effect
  41. 41. Agile 
 …deals with the silo effects between • Requirements and • Development and • Quality Assurance
  42. 42. DevOps … deals with silo effects between • Requirements engineering • Development • Quality • Deployment • Maintenance • Operations
  43. 43. Vice President Product CEO Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant Product Development
  44. 44. Remove Silos
  45. 45. Direct Cooperation vs departmental boundaries Discussions vs handovers & processes
  46. 46. Shared Topics • requirements • business metrics • release pipeline • technical resources • architecture
  47. 47. Shared Responsibility • Responsibility for the product, 
 not department objectives • documentation & ticketing is a tool, 
 not a contract • no handovers
  48. 48. Shared Goals • focus on • product • overall process • shared metrics • user metrics • platform metrics • quality metrics
  49. 49. Vice President Product Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant CEO Team You built it, you run it.
  50. 50. Autonomous Cross-
 Functional Teams • all skills needed are part of the team • no external dependencies • authority for decisions • no handover needed Inverse Conway Maneuver
  51. 51. „Product Design builds the right product“ „Dev builds the product the right way.“ „Ops delivers the right support.“ Respect & Trust (a.k.a. the hard part)
  52. 52. DevOpsCulture Direct cooperation Autonomous Teams Shared Responsability Shared Goals Automation Trust & Respect
  53. 53. Contradictions Organisation DevOps individual 
 accountability shared accountability department goals & objectives shared objectives individual objectives & bonuses shared objectives local efficiency global efficiency
  54. 54. Ignoring these contradictions between DevOps and functional Orgs will result in anti patterns
  55. 55. Vice President Product Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant CEO
  56. 56. Vice President DevOps Database 
 DevOps Enterprise 
 DevOps Junior DevOps „DevOps is a new department focussing on infrastructure & deployment automation“ CEO Devops
  57. 57. Product Development Quality Ass. Maintenance Look, we added another silo! DevOps Dev
 Ops
  58. 58. DevOps is not a function. DevOps is a form of cooperation
  59. 59. Dev Ops QA DevOps
  60. 60. Developer Role Operation Role Quality Assurance Role + DevOps Role?
  61. 61. DevOps-Engineer Devs with QA & Ops knowhow SysEng with QA & Dev Knowhow QA with Dev & Ops Knowhow
  62. 62. DevOps-Engineer - an anti-pattern that is 
 a starting point, too.
  63. 63. Vice President Development Software Developer Frontend Developer DevOps Engineer CEO Development- only DevOps Puppet Vagrant SaltStack Testing & CI … but not in Production
  64. 64. Product Developer Software 
 Development Quality 
 Assurance Operations Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant SLES based SLES based Vagrant Boxes QA uses Ubuntu Product Development WTF WTF
  65. 65. DevOps vs Management
  66. 66. DevOps vs Management Automation is expensive
 Incompatible with functional orgs Incompatible with MbO Incompatible with 
 command & control
  67. 67. Never change a running system. Always improve 
 your running system.
  68. 68. DevOps vs Company Culture No more lonely heroes
  69. 69. Cooperation is harder than it seems No more „stupid sales droids“ No more „stupid frontend devs“ No more „stupid customers“ No more „stupid management“ No more „stupid features“ No more „my department is great, but (other department) is not“
  70. 70. Vice President Product Vice President Development Vice President Quality Vice President Maintenance Product Developer Software Developer Quality 
 Assurance Operator Product Owner Frontend Developer Tester NetSec
 Consultant Product Designer Backend
 Developer Test Infrastructure Performance Consultant CEO MicroService-Team Inverse Conway Maneuver FTW?!
  71. 71. Inverse Conway Maneuver FTW?! Corporate Culture does not change fast.
  72. 72. Inverse Conway Maneuver FTW?! Corporate Culture does not change fast. 
 Functional Org DevOps
  73. 73. Inverse Conway Maneuver FTW?! Corporate Culture does not change fast. 
 Functional Org DevOps True for 20 years True for 6 months
  74. 74. How to create a DevOps Culture
  75. 75. 3Ways of DevOps
  76. 76. 1 Systems Thinking
  77. 77. 1 Systems Thinking Draw how to make Toast http://www.drawtoast.com/
  78. 78. 2 Amplify Feedback Loops
  79. 79. Loops 2 Amplify Feedback Product 
 Development Software Development Deployment Business 
 Analytics Management
  80. 80. 2 Amplify Feedback Product 
 Development Software Development Deployment Business 
 Analytics Management 1 months 3 months 1 week 1 Sprint 1 day 143 days!
  81. 81. 2 Amplify Feedback Product 
 Development Software Development Deployment Business 
 Analytics 1 week 1 day 1 sprint 1 day 23 days Management
  82. 82. 3Culture of Continual Experimentation & Failure
  83. 83. 3Culture of Continual Experimentation & Failure Fail cheap Fail often
  84. 84. 3Culture of Continual Visibility Resilience Experimentation & Failure
  85. 85. 3Ways of DevOps Systems Thinking Amplify Feedback Loops Culture of Continual Experientation DevOps culture is the delayed outcome
  86. 86. 3Ways of DevOps Enable Your teams to 
 understand the business , cooperate and learn together. It’s not about 
 change management
  87. 87. DevOpsCulture Direct cooperation Autonomous Teams Shared Responsability Shared Goals Automation Trust & Respect
  88. 88. Have fun breaking the iron triangle using DevOps!

×