Slide 1

Slide 1 text

@jezhumble | devopsdays dallas 2018 devops leadership workshop

Slide 2

Slide 2 text

@jezhumble “the enterprise” Project A Project B Project C DBAs Infrastructure team Service desk Value stream Operations Engineering Business Ping!

Slide 3

Slide 3 text

@jezhumble Project A Project B Project C DBAs Infrastructure team Service desk Value stream Operations Engineering Business Ping! Project D Let’s create a new product enterprise projects

Slide 4

Slide 4 text

@jezhumble Project A Project B DBAs Infrastructure team Service desk Project D We’re going agile! Oh no! Oh no! Value stream Operations Engineering Business

Slide 5

Slide 5 text

@jezhumble Project A Project B DBAs Infrastructure team Service desk Value stream Operations Engineering Business Project D Our test-driven code follows SOLID principles Shame it doesn’t work Change management

Slide 6

Slide 6 text

@jezhumble …rewriting all our systems and sticking them in the cloud …firing our sysadmins / testers / … and hiring “devops experts” …doing a re-org …giving developers (or anyone else for that matter) access to prod …buying a bunch of devops tools myths: devops isn’t…

Slide 7

Slide 7 text

@jezhumble devops movement a cross-functional community of practice dedicated to the study of building, evolving and operating rapidly changing, secure, resilient systems at scale

Slide 8

Slide 8 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 9

Slide 9 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 10

Slide 10 text

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

Slide 11

Slide 11 text

@jezhumble 2018 performance benchmarks http://bit.ly/2018-devops-report

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

@jezhumble lean management

Slide 14

Slide 14 text

@jezhumble lean product management

Slide 15

Slide 15 text

technical practices http://bit.ly/2018-devops-report

Slide 16

Slide 16 text

transformational leadership Transformational leaders share five common characteristics that significantly shape an organization's culture and practices, leading to high performance.

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

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

Slide 19

Slide 19 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 20

Slide 20 text

culture impacts performance

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

likert-type scale How strongly do you agree or disagree with the following? On my team...

Slide 23

Slide 23 text

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

Slide 24

Slide 24 text

@jezhumble identity and Google items • I am glad I chose to work for this organization rather than another company. • I talk of this organization to my friends as a great company to work for. • I am willing to put in a great deal of effort beyond what is normally expected to help my organization to be successful. • I find that my values and my organization's values are very similar. • In general, the people employed by my organization are working toward the same goal. • I feel that my organization cares about me. Adapted from adapted from Atreyi Kankanhalli, Bernard C.Y. Tan, and Kwok-Kee Wei (2005), “Contributing Knowledge to Electronic Knowledge Repositories: An Empirical Investigation,“ MIS Quarterly, 29, 113-143. Westrum items

Slide 25

Slide 25 text

@jezhumble ask: how can we get people better information? in a complex, adaptive system failure is inevitable when accidents happen, human error is the starting point of a blameless post-mortem ask: how can we detect and limit failure modes? dealing with failure

Slide 26

Slide 26 text

@rynchantress | https://ryn.works/2017/06/17/on-failure-and-resilience/ The immediate response from everyone around was to ask, “What help do you need?”

Slide 27

Slide 27 text

@jezhumble disaster recovery testing “For DiRT-style events to be successful, an organization first needs to accept system and process failures as a means of learning… We design tests that require engineers from several groups who might not normally work together to interact with each other. That way, should a real large-scale disaster ever strike, these people will already have strong working relationships” Kripa Krishnan | http://queue.acm.org/detail.cfm?id=2371297 —Kripa Krishnan, Director, Cloud Operations, Google

Slide 28

Slide 28 text

@jezhumble climate for learning http://bit.ly/2018-devops-report

Slide 29

Slide 29 text

exercise • How can we measure the productivity of an individual?

Slide 30

Slide 30 text

the talent myth “The talent myth assumes that people make organizations smart. More often than not, it’s the other way around...Our lives are so obviously enriched by individual brilliance. Groups don’t write great novels, and a committee didn’t come up with the theory of relativity. But companies work by different rules. They don’t just create; they execute and compete and coordinate the efforts of many different people, and the organizations that are most successful at that task are the ones where the system is the star.” — Malcolm Gladwell http://gladwell.com/the-talent-myth/

Slide 31

Slide 31 text

Frederick Winslow Taylor (1856-1915) “Scientific Management” •Time and motion studies to analyze and standardize processes •Managers apply scientific principles to plan work, workers perform it as efficiently as possible •Believed in rewarding workers for output •OK for fundamentally algorithmic work

Slide 32

Slide 32 text

@jezhumble learning ability emergent leadership mindset how should we recruit? http://nyti.ms/1v72xuz | http://nyti.ms/1v72sHl

Slide 33

Slide 33 text

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

Slide 34

Slide 34 text

changing 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 35

Slide 35 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 36

Slide 36 text

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

Slide 37

Slide 37 text

@jezhumble climate for learning http://bit.ly/2018-devops-report

Slide 38

Slide 38 text

@jezhumble deploy and release its product or service on demand, independently of other services the product or service depends upon? make large-scale changes to the design of its system without the permission of somebody outside the team or depending on other teams? complete its work without needing fine-grained communication and coordination with people outside the team? perform deployments during normal business hours with negligible downtime? do most of its testing on demand, without requiring an integrated test environment? architectural outcomes: can my team…

Slide 39

Slide 39 text

Steve Yegge’s Platform Rant | http://bit.ly/1zxknpR

Slide 40

Slide 40 text

http://www.flickr.com/photos/trustedsource/6132507962/

Slide 41

Slide 41 text

@jezhumble strangler application

Slide 42

Slide 42 text

break

Slide 43

Slide 43 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 44

Slide 44 text

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

Slide 45

Slide 45 text

deployment pipeline

Slide 46

Slide 46 text

hp laserjet firmware ~5% - innovation 15% - manual testing 25% - current product support 25% - porting code 20% - detailed planning 10% - code integration 2008 ~40% - innovation 5% - most testing automated 10% - current product support 15% - one main branch 5% - agile planning 2% - continuous integration 2011 The remaining 23% on RHS is spent on managing automated tests.

Slide 47

Slide 47 text

the economics 2008 to 2011 • overall development costs reduced by ~40% • programs under development increased by ~140% • development costs per program down 78% • resources now driving innovation increased by 8X A Practical Approach to Large-Scale Agile Development (Addison-Wesley) Gruver, Young, Fulghum

Slide 48

Slide 48 text

Toyota Kata: Managing People for Improvement, Adaptiveness, and Superior Results, Mike Rother

Slide 49

Slide 49 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 50

Slide 50 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 51

Slide 51 text

@jezhumble target conditions

Slide 52

Slide 52 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 53

Slide 53 text

No content

Slide 54

Slide 54 text

@jezhumble capacity planning A Practical Approach to Large-Scale Agile Development - Gruver, Young, Fulghum

Slide 55

Slide 55 text

@jezhumble capacity planning

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

@jezhumble start with a few measurable outcomes everyone must be involved in setting objectives / outcomes set a regular cadence both for planning and for review make sure metrics are visible throughout the organization ensure teams have the necessary capacity, resources and support tips and tricks

Slide 59

Slide 59 text

@jezhumble expect to get it wrong the right first time top-level outcomes should be system outcomes don’t measure below the team level goals should be stretch but achievable metrics should drive outcomes, not make you feel good about yourself things to watch out for

Slide 60

Slide 60 text

@jezhumble specify a qualitative objective specify quantitative “key results” that are acceptance criteria a tool for creating alignment and transparency around goals OKRs

Slide 61

Slide 61 text

@jezhumble create alignment and transparency expose organizational dysfunction: • leadership that is unable to prioritize • leadership that thrashes and is unable to focus • micromanagement & trying to dictate “how” rather than “what” • people hiding information • people working on things that don’t matter OKRs / catchball

Slide 62

Slide 62 text

exercise • Ask two other people the following questions: • What’s your goal for the end of this year? • How will you know if you’ve achieved it? choose up to 3 things

Slide 63

Slide 63 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 64

Slide 64 text

thank you! © 2016-18 Jez Humble and Associates LLC https://continuousdelivery.com/ To receive the following: • A copy of this presentation • The link to the 2018 Accelerate State of DevOps Report (and previous years) • A 100 page excerpt from Lean Enterprise • Excerpts from the DevOps Handbook and Accelerate • 30% off my video workshop: creating high performance organizations • A 20m preview of my Continuous Delivery video workshop • Discount code for CD video + interviews with Eric Ries & more Just pick up your phone and send an email To: [email protected] Subject: devops