Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Scaling DevOps success before cynicism takes over

Scaling DevOps success before cynicism takes over

You’re winning with DevOps, now what? For the last decade we’ve seen case studies on high-performing teams who’ve implemented DevOps practices. How does this scale beyond the team? How do we influence skeptics? Let’s look at scaling out success when the point of reference is larger than the team. Success using DevOps practices has been unevenly distributed. Some teams claim success while their colleagues and peers struggle with basic technology delivery. For the organization as a whole, continuing to improve optimized areas results only in local gains. The true promise of DevOps was to globally optimize technology delivery. How do you scale? How do you influence others teams, or a whole department? How do you overcome blockers that were originally seen as beyond your scope of control? This discussion will walk through scaling DevOps practices beyond the team or small number of teams by upleveling the discussion to focus on department or org-level patterns. This scaling will cover grass-roots expansion of success, the trade-offs of a top-down mandate, and forcing functions to steer multiple groups of people on their aligned goals. There are still metrics to use when looking at DevOps from a larger perspective, and those are covered as well.

Michael Stahnke

October 09, 2018
Tweet

More Decks by Michael Stahnke

Other Decks in Technology

Transcript

  1. @stahnma In a DevOps evolution, there are many paths to

    success, but even more that lead to failure.
  2. @stahnma cyn·i·cism
 
 noun
 
 an inclination to believe that

    people are motivated purely by self-interest; skepticism.

  3. @stahnma scale verb (def 2c) to pattern, make, regulate, set,

    or estimate according to some rate or standard e.g. a production schedule scaled to actual need
  4. @stahnma Start with the practices that are closest to production,

    then address processes that happen earlier in the software delivery cycle.
  5. @stahnma C-Suite Management Team Teams contribute improvements to tooling provided

    by other teams 64% 46% 35% We balance lowering technical debt with new feature work 61% 44% 33% Security teams involved in technology design and deployment 64% 48% 39%
  6. @stahnma C-Suite Management Team Delta Teams contribute improvements to tooling

    provided by other teams 64% 46% 35% 29% We balance lowering technical debt with new feature work 61% 44% 33% 28% Security teams involved in technology design and deployment 64% 48% 39% 25%
  7. @stahnma Share first. Remove if statements. Start close to production.

    Revaluate business processes. Ask why. Metrics need a story. Actions
  8. @stahnma 2018 State of DevOps Report 2018 author discussion 2017

    Report 2016 Report 2015 Report 2014 Report 2013 Report boringtechnology.club Post Incident Reviews Resources