Slide 1

Slide 1 text

@jezhumble oop 6 february 2018 growing a culture of experimentation

Slide 2

Slide 2 text

@jezhumble start small (teams and scope) and deliver often culture is measurable and it can be changed… slowly change culture by changing behavior and doing things differently leaders must make it cheap, quick and safe to run experiments practice making mistakes so it becomes normal too long: didn’t listen;

Slide 3

Slide 3 text

what is culture? “A pattern of shared tacit assumptions that was learned by a group as it solved its problems of external adaptation and internal integration, that has worked well enough to be considered valid and, therefore, to be taught to new members as the correct way to perceive, think, and feel in relation to those problems.” — Edgar Schein, The Corporate Culture Survival Guide

Slide 4

Slide 4 text

software delivery as a competitive advantage “Firms with high-performing IT organizations were twice as likely to exceed their profitability, market share and productivity goals.” http://bit.ly/2014-devops-report

Slide 5

Slide 5 text

software delivery as a competitive advantage high performers were more than twice as likely to achieve or exceed the following objectives: • Quantity of products or services • Operating efficiency • Customer satisfaction • Quality of products or services provided • Achieving organizational and mission goals • Measures that demonstrate to external parties whether or not the organization is achieving intended results http://bit.ly/2017-devops-report

Slide 6

Slide 6 text

@jezhumble time to restore service lead time for changes release frequency change fail rate it performance http://bit.ly/2014-devops-report

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

high trust culture Westrum, “A Typology of Organizational Cultures” | http://bmj.co/1BRGh5q how organizations process information

Slide 9

Slide 9 text

effective teams https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/

Slide 10

Slide 10 text

capabilities that drive high performance Accelerate: The Science of Lean Software and DevOps, Forsgren, Humble and Kim 2018

Slide 11

Slide 11 text

lean product development • working in small batches & use of MVPs • visibility into the flow of work across the value stream • seeking—and acting on—feedback from customers • giving teams the authority to create & change specs

Slide 12

Slide 12 text

@jezhumble culture of experimentation 1. in the small

Slide 13

Slide 13 text

impact mapping Gojko Adzic, Impact Mapping

Slide 14

Slide 14 text

hypothesis-driven delivery We believe that [building this feature] [for these people] will achieve [this outcome]. We will know we are successful when we see [this signal from the market]. Jeff Gothelf “Better product definition with Lean UX and Design” http://bit.ly/TylT6A

Slide 15

Slide 15 text

experiments Different types of user research, courtesy of Janice Fraser

Slide 16

Slide 16 text

Jon Jenkins, “Velocity Culture, The Unmet Challenge in Ops” | http://bit.ly/1vJo1Ya

Slide 17

Slide 17 text

continuous delivery

Slide 18

Slide 18 text

“Evaluating well-designed and executed experiments that were designed to improve a key metric, only about 1/3 were successful at improving the key metric!” do less “Online Experimentation at Microsoft”, Kohavi et al http://stanford.io/130uW6X

Slide 19

Slide 19 text

@jezhumble culture of experimentation 2. in the large

Slide 20

Slide 20 text

the production line http://www.flickr.com/photos/toyotauk/4711057997/

Slide 21

Slide 21 text

methodologies Certainly the thieves may be able to follow the design plans and produce a loom. But we are modifying and improving our looms every day. So by the time the thieves have produced a loom from the plans they stole, we will have already advanced well beyond that point. And because they do not have the expertise gained from the failures it took to produce the original, they will waste a great deal more time than us as they move to improve their loom. We need not be concerned about what happened. We need only continue as always, making our improvements. Kiichiro Toyoda, quoted in Toyota Kata, p40 (Rother)

Slide 22

Slide 22 text

how to change culture? http://www.thisamericanlife.org/radio-archives/episode/403/nummi http://sloanreview.mit.edu/article/how-to-change-a-culture-lessons-from-nummi/ “What changed the culture was giving employees the means by which they could successfully do their jobs. It was communicating clearly to employees what their jobs were and providing the training and tools to enable them to perform those jobs successfully.” —John Shook

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

@jezhumble What obstacles are preventing you from reaching it? which one are you addressing now? What is the target condition? (The challenge) What is the actual condition now? When can we go and see what we learned from taking that step? What is your next step? (Start of PDCA cycle) improvement kata

Slide 25

Slide 25 text

@jezhumble hp futuresmart

Slide 26

Slide 26 text

hp laserjet firmware 2008 ~5% - innovation capacity 15% - manual testing 25% - product support 25% - porting code 20% - detailed planning 10% - code integration Costs Full manual regression: 6 wks Builds / day: 1-2 Commit to trunk: 1 week Cycle times

Slide 27

Slide 27 text

@jezhumble implement continuous integration reduce hardware variation create a single package create a simulator implement comprehensive test automation futuresmart rearchitecture

Slide 28

Slide 28 text

@jezhumble target conditions

Slide 29

Slide 29 text

@jezhumble 1 month program level plan for 400-person org fits on 1 piece of paper teams can use any process / methodology they like turning objectives into features / stories happens within teams leaders don’t tell people what to do or how to do it same heuristic for process improvement and product development observations

Slide 30

Slide 30 text

https://www.slideshare.net/reed2001/culture-1798664/94-Highly_Aligned_Loosely_Coupled_Highly

Slide 31

Slide 31 text

@jezhumble deliver and create fast feedback loops Mike Bracken | @MTBracken | http://mikebracken.com/blog/the-strategy-is-delivery-again/

Slide 32

Slide 32 text

capabilities that drive high performance Accelerate: The Science of Lean Software and DevOps, Forsgren, Humble and Kim 2018

Slide 33

Slide 33 text

“I think building this culture is the key to innovation. Creativity must flow from everywhere. Whether you are a summer intern or the CTO, any good idea must be able to seek an objective test, preferably a test that exposes the idea to real customers. Everyone must be able to experiment, learn, and iterate.” innovation culture http://glinden.blogspot.com/2006/04/early-amazon-shopping-cart.html

Slide 34

Slide 34 text

thank you! © 2018 Jez Humble & Associates LLC https://continuousdelivery.com/ | https://devops-research.com/ To receive the following: • 30% off my new video course: creating high performance organizations • 50% off my CD video training, interviews with Eric Ries, and more • A copy of this presentation • A 100 page excerpt from Lean Enterprise • An excerpt from The DevOps Handbook • A 20m preview of my Continuous Delivery video workshop Just pick up your phone and send an email To: jezhumble@sendyourslides.com Subject: devops