Leading a DevOps Transformation

Slide 1

Slide 1 text

Slide 2

Slide 2 text

@jezhumble what devops isn’t… the problem (why cd matters) how does devops help? how to get there …and what it is agenda

Slide 3

Slide 3 text

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

Slide 4

Slide 4 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 5

Slide 5 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 6

Slide 6 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 7

Slide 7 text

how devops helps

Slide 8

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

Slide 9 text

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

Slide 10

Slide 10 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 eﬀiciency • 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 11

Slide 11 text

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

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

it’s about culture and architecture not process, tools, organizational structure

Slide 15

Slide 15 text

@jezhumble …rewriting all our systems and sticking them in the cloud …ﬁring 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 16

Slide 16 text

@jezhumble devops is… …learning to work in small batches (product dev & org change)

Slide 17

Slide 17 text

@jezhumble projects are evil “Black Swan Farming using Cost of Delay” | Joshua J. Arnold and Özlem Yüce | bit.ly/black-swan-farming

Slide 18

Slide 18 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 ﬁne-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 19

Slide 19 text

http://www.ﬂickr.com/photos/trustedsource/6132507962/

Slide 20

Slide 20 text

@jezhumble strangler application

Slide 21

Slide 21 text

@jezhumble rules of strangler • start by delivering new functionality—at least at ﬁrst • don’t rewrite existing functionality except to simplify • deliver something fast • design for testability and deployability • architect the new software to run on a paas

Slide 22

Slide 22 text

@jezhumble org change Geoﬀrey Moore, Crossing the Chasm

Slide 23

Slide 23 text

@jezhumble devops is… …learning to work in small batches (product dev & org change) …creating fast feedback loops

Slide 24

Slide 24 text

@jezhumble deployment pipeline

Slide 25

Slide 25 text

@jezhumble devops is… …learning to work in small batches (product dev & org change) …creating fast feedback loops …enabling cross-functional collaboration though value streams

Slide 26

Slide 26 text

@jezhumble devops is… …learning to work in small batches (product dev & org change) …creating fast feedback loops …enabling cross-functional collaboration across value streams …developing a culture of experimentation

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

eﬀective teams https://rework.withgoogle.com/blog/ﬁve-keys-to-a-successful-google-team/

Slide 29

Slide 29 text

@jezhumble disaster recovery testing “For DiRT-style events to be successful, an organization ﬁrst 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 30

Slide 30 text

Ryn Daniels | @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 31

Slide 31 text

No content

Slide 32

Slide 32 text

Slide 33

Slide 33 text

@jezhumble value stream mapping

Slide 34

Slide 34 text

@jezhumble improving performance

Slide 35

Slide 35 text

Mike Rother | http://www-personal.umich.edu/~mrother/

Slide 36

Slide 36 text

@jezhumble encourage collaboration agree and communicate measurable business goals give teams resources to experiment and reward learning keep going achieve quick wins and share lessons learned the journey “6 Steps To Survive A DevOps Transformation” | http://ubm.io/1dKJajR

Slide 37

Slide 37 text

thank you! © 2016-18 Jez Humble & Associates LLC https://continuous-delivery.com/ To receive the following: • A copy of this presentation • A 100 page excerpt from Lean Enterprise • Excerpts from the DevOps Handbook and Accelerate • 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: jezhumble@sendyourslides.com Subject: devops