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.

Transcript

1. Scaling DevOps success before cynicism takes over Michael Stahnke @stahnma 09 Oct 2018
2. @stahnma
3. @stahnma
4. @stahnma
5. @stahnma Why DevOps?
6. @stahnma
7. @stahnma Tell me how
8. @stahnma
9. @stahnma
10. @stahnma
11. @stahnma In a DevOps evolution, there are many paths to success, but even more that lead to failure.
12. @stahnma Team 1 Team 2 Team 3 Team 4 Team 5
13. @stahnma
14. @stahnma cyn·i·cism
 
 noun
 
 an inclination to believe that people are motivated purely by self-interest; skepticism.

15. @stahnma Hating is easier than trying.
16. @stahnma Hating is easier than trying.
17. @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
18. @stahnma Replicate DevOps success across the organization.
19. @stahnma What’s the opposite of scale?
20. @stahnma Heroics
21. @stahnma
22. @stahnma 6 Actions to move forward
23. @stahnma 1
24. @stahnma Begin with Sharing
25. @stahnma Make source code available to all teams
26. @stahnma Allow all teams contribute improvements to tooling
27. @stahnma Hold post incident reviews
28. @stahnma 2
29. @stahnma Complexity is if statements.
 
 Reduce them.
30. @stahnma Complexity is if statements.
 
 Reduce them.
31. @stahnma
32. @stahnma
33. @stahnma
34. @stahnma
35. @stahnma 3
36. @stahnma
37. @stahnma
38. @stahnma
39. @stahnma Take a look at cumbersome process: ask “why” with a friend.
40. @stahnma Nobody wants your job to be more difficult.
41. @stahnma Hating is easier than trying.
42. @stahnma 4
43. @stahnma Start with the practices that are closest to production, then address processes that happen earlier in the software delivery cycle.
44. @stahnma 5
45. @stahnma Activate your security team.
46. @stahnma Infrastructure is automatable
47. @stahnma Team are working across multiple functional boundaries
48. @stahnma 6
49. @stahnma .
50. @stahnma Ensure you have success metrics, they are visible, and they have a narrative.
51. @stahnma Explain why the metric matters.
52. @stahnma Explain cross-department metrics in a common language.
53. @stahnma Buffer Overrun
54. @stahnma Executives have a rosier view 
 of DevOps progress than 
 the teams below them.
55. @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%
56. @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%
57. @stahnma Messages get filtered upward
58. @stahnma Only success makes it to them
59. @stahnma Engage executives for prioritization, not for a mandate
60. @stahnma
61. @stahnma Share first. Remove if statements. Start close to production. Revaluate business processes. Ask why. Metrics need a story. Actions
62. @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
65. @stahnma
66. @stahnma
67. @stahnma
68. @stahnma
69. @stahnma