Leading a DevOps Transformation

Implementing DevOps is more than just implementing tools. It requires thinking – and acting – differently about everything from budgeting and program management to architecture and compliance. In this talk, Jez presents what DevOps is and, just as importantly, what it isn’t from the leadership perspective, and takes you through the journey you’ll need to embark on in order to achieve the outcomes DevOps promises.

Transcript

1. @jezhumble | dev on summit | march 14, 2018 leading a devops transformation © 2017 Jez Humble
2. @jezhumble what devops isn’t… the problem (why cd matters) how does devops help? how to get there …and what it is agenda
3. @jezhumble “the enterprise” Project A Project B Project C DBAs Infrastructure team Service desk Value stream Operations Engineering Business Ping!
4. @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
5. @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
6. @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
7. how devops helps
8. @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
9. 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
10. 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
11. @jezhumble time to restore service lead time for changes release frequency change fail rate it performance http://bit.ly/2014-devops-report
12. Jon Jenkins, “Velocity Culture, The Unmet Challenge in Ops” | http://bit.ly/1vJo1Ya http://bit.ly/2016-devops-report
13. Jon Jenkins, “Velocity Culture, The Unmet Challenge in Ops” | http://bit.ly/1vJo1Ya
14. it’s about culture and architecture not process, tools, organizational structure
15. @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…
16. @jezhumble devops is… …learning to work in small batches (product dev & org change)
17. @jezhumble projects are evil “Black Swan Farming using Cost of Delay” | Joshua J. Arnold and Özlem Yüce | bit.ly/black-swan-farming
18. @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…
19. http://www.flickr.com/photos/trustedsource/6132507962/
20. @jezhumble strangler application
21. @jezhumble rules of strangler • start by delivering new functionality—at least at first • 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
22. @jezhumble org change Geoffrey Moore, Crossing the Chasm
23. @jezhumble devops is… …learning to work in small batches (product dev & org change) …creating fast feedback loops
24. @jezhumble deployment pipeline
25. @jezhumble devops is… …learning to work in small batches (product dev & org change) …creating fast feedback loops …enabling cross-functional collaboration though value streams
26. @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
27. @jezhumble high trust culture Westrum, “A Typology of Organizational Cultures” | http://bmj.co/1BRGh5q how organizations process information
28. effective teams https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/
29. @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
30. 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?”
32. @jezhumble devops is… …learning to work in small batches (product dev & org change) …creating fast feedback loops …enabling cross-functional collaboration across value streams …making it safe to fail …continually working to remove waste and make things better
33. @jezhumble value stream mapping
34. @jezhumble improving performance
35. Mike Rother | http://www-personal.umich.edu/~mrother/
36. @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
37. 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