Expanding Pockets of DevOps Greatness
Transcript of Expanding Pockets of DevOps Greatness
Expanding Pockets of DevOps Greatness
Gene Kim
Jeff Gallimore
2
Housekeeping
▪ This webinar is being recorded
▪ Links to the slides and the recording will be made available after the presentation
▪ You can post questions via the GoToWebinar Control Panel
3
Gene Kim
Author, Researcher
IT Revolution
Jeff Gallimore
Partner, Co-Founder
Excella Consulting
Meet Your Presenters
4
What Does Greatness Look Like?
▪ More throughput
▪ More stability
▪ More control
▪ More winning
5
High Performers Are More Agile
46x 440xmore frequent
deployments
faster lead times
than their peers
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
6
High Performers Are More Reliable
5x 96xlower change
failure rate
faster mean time
to recover (MTTR)
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
7
High Performers Are More Secure And Controlled
2x 29%less time spent
remediating
security issues
more time spent
on new work
Source: Puppet Labs 2016 State Of DevOps Report: https://puppet.com/resources/white-paper/2016-state-of-devops-report
8
High Performers Win In The Marketplace
2x 2xmore likely to
exceed profitability,
market share and
productivity goals
more likely to achieve
organizational and mission
goals,customer satisfaction,
quantity and quality goals
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
9
High Performers Win In The Marketplace
2.2xhigher employee
Net Promoter Score
Source: Puppet Labs 2016 State Of DevOps Report: https://puppet.com/resources/white-paper/2016-state-of-devops-report
50%higher market
capitalization growth
over 3 years*
10
We Need DevOps Now
▪ We want all those benefits from “more DevOps”…
▪ But how do we get “more DevOps” so we can get those benefits?
▪ Big Realization: You already have DevOps within your organization – it’s just not evenly distributed
11
Vertically
▪ Convincing your team (down) and your boss (up)
▪ Well-known, visible, formal relationships
▪ Based on authority
Horizontally
▪ Connecting to colleagues (across)
▪ Informal power structures and social networks
▪ Based on influence
Scaling DevOps
12
This Webinar Is For You If…
▪ You believe in the benefits of DevOps
▪ You want to build and promote grassroots DevOps efforts within your organization
▪ You’ve had small DevOps successes – like with a single team or project
▪ You’re aware of some like-minded people and groups within your organization, but you don’t know who they all are
▪ You lack a significant span of control (i.e., you’re not an executive)
▪ You want to build a “coalition of the willing”
13
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
Dimensions of Transformational Leadership
14
Your Strategies for Scaling DevOps Horizontally
1. Share: “I provide opportunities to share knowledge and make success visible.”
2. Communicate: “I create common communication channels.”
3. Standardize: “I increase standardization and consistency of processes and tools.”
4. Empower: “I develop leadership capacity.”
15
1. Share
▪ Provide opportunities to share knowledge and make success visible
▪ Help like-minded allies find you
▪ Advertise the real, practical, relevant benefits of DevOps within your organization
▪ Avoid debate of academic, hypothetical, “we’re different”
16
▪ “Show and Tells”
▪ Demo Days
▪ Webinars
▪ Internal Open Source
▪ Dojos
▪ [Picture Here]
1. Share: Tactics
17
▪ Answer “What’s in it for me?” for your audience
▪ Connect the dots so it’s easy to see why their participation is valuable to them
▪ [Picture Here]
1. Share: Pro Tip – “What’s in it for me?”
18
Target
Ross Clanton and Heather Mickman hosted internal DevOps Days events
Verizon
Nanda Kumar gamified DevOps by creating “DevOps Cup” competition
1. Share: Examples – Target and Verizon
19
2. Communicate
▪ Create common “go to” communication channels that focus, facilitate, and encourage collaboration
▪ Make it easy for people to find information they need, share knowledge they’ve discovered, and communicate with like-minded people
▪ Avoid fragmentation and factions
20
▪ Wikis and intranets
▪ Chat rooms
▪ Email lists
▪ Newsletters and mass education
▪ [Picture Here]
2. Communicate: Tactics
21
▪ Use stories with a beginning, middle, and end
▪ Make it visual with graphics, logos, stickers
▪ Include numbers and metrics for evidence
▪ [DOES]
▪ [stickers]
▪ [SODR]
2. Communicate: Pro Tip – Good Marketing
22
3. Standardize
▪ Increase standardization and consistency of language, processes, and tools
▪ Adoption because people want to – not because they have to
▪ “Make the right thing the easy thing”
▪ Respect individual flexibility
23
▪ Standardize common services
▪ Scorecard
▪ Experimentation
▪ Common language
▪ Adopt rogue apps
▪ [Picture Here]
3. Standardize: Tactics
24
Merck
Jason Victor adopted one team’s unsanctioned issue and task management suite and promoted it
Mike Bland used “Rainbow of Death” to change culture around automated testing
3. Standardize: Examples – Merck and Google
25
4. Empower
▪ Develop leadership capacity
▪ Find individuals whose contributions stand out from their peers
▪ Visible and not-so-visible
▪ Be proactive and reach out
26
▪ Identify leaders
▪ Mentor leaders
▪ Promote influence across groups
▪ Create impactful roles
▪ [Picture Here]
4. Empower: Tactics
27
4. Empower: Pro Tip – Keep An Open Mind
▪ Don’t dismiss the counterintuitive
▪ Experiment to find out what really works (and what really doesn’t)
▪ Treat failures as learning opportunities
▪ Incorporate ideas from others to increase their buy-in
28
Tasktop
Mik Kersten helped team members visualize the value stream, which highlighted bottlenecks – and identified big contributors
4. Empower: Example – Tasktop
29
Leadership Matters
▪ Teams with the least amount of transformational leadership behaviors (the bottom third) were one-half as likely to be high IT performers
▪ But leaders cannot do it alone! Teams with the top 10% of transformational leaders performed no better than the median
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
30
Leaders Affect Outcomes Through…
Source: Puppet/DORA: 2017 State Of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
31
▪ Change is risky
▪ Taking risks requires courage
▪ Courage is a characteristic of every great hero
You Can Be A Hero
32
Available for download in the Handouts section of your GoToWebinar control panel
Get The Whitepaper
https://itrevolution.com/book/expanding-pockets-greatness/
33
More Whitepapers
https://itrevolution.com/devops-books/
DevOps Enterprise Summit
https://events.itrevolution.com/
Other Resources
Questions
35
Thank you!
▪ Don’t miss our next webinar!
▪ Featuring Gene Kim, Pauly Comtois, and Tim Buntel
▪ Register today! https://xebialabs.com/community/webinars/