Slide 1

Slide 1 text

Understanding DevOps 1

Slide 2

Slide 2 text

2 Helen Beal Helen Beal is chair of the Value Stream Management Consortium, co-chair of the OASIS Value Stream Management Interoperability Technical Committee, and chief ambassador at DevOps Institute. She also provides strategic advisory services to DevOps and VSM industry leaders. Helen is the author of the annual State of VSM Reports from the VSMC and the State of Availability Report from Moogsoft. She is a co-author of the book about DevOps and governance, Investments Unlimited, published by IT Revolution. She is a DevOps editor for InfoQ, and hosts the Day-to-Day DevOps webinar series for BrightTalk and speaks on DevOps and value stream-related topics at a wide variety of industry conferences and at corporate events. She regularly appears in TechBeacon’s DevOps Top100 lists and was recognized as the Top DevOps Evangelist 2020 in the DevOps Dozen awards and was a finalist for Computing DevOps Excellence Awards’ DevOps Professional of the Year 2021. She serves on advisory and judging boards for many initiatives including Developer Week, DevOps World, JAX DevOps, and InterOp. Herder of Humans @helenhappybee PURPOSE: Bringing Joy to Work

Slide 3

Slide 3 text

We drive human transformation in the digital age. DevOps Institute is a professional association and certification authority that prepares people and organizations to succeed in building the processes and culture to support the future of IT. We are also a learning destination and community for technology practitioners and leaders looking to continuously learn about the IT technologies and processes that drive enterprise transformation. About DevOps Institute 3

Slide 4

Slide 4 text

We believe the greatest challenges facing businesses isn’t tech, it’s humans. 4

Slide 5

Slide 5 text

POLL 5 Which is your preferred definition of DevOps?

Slide 6

Slide 6 text

Imagine a world where product owners, Development, QA, IT Operations and Infosec work together, not only to help each other, but also to ensure that the overall organization succeeds. By working towards a common goal, they enable the fast flow of planned work into production, while achieving world-class stability, reliability, availability and security. 6

Slide 7

Slide 7 text

But Why? 7 Digital Transformation DevOps Cloud Architecture Automation Better, sooner, faster, safer, happier Scalability, elasticity, flexibility ACCELERATE FLOW DRIVER ENABLERS SOLUTION OUTCOMES

Slide 8

Slide 8 text

What is DevOps? Patrick Debois originally coined the word 'DevOps' 8

Slide 9

Slide 9 text

What DevOps is Not 9 • A title • A separate team • A tool • Only culture • Only automation • Anarchy • A one size fits all strategy DevOps is coming to life through emerging practices that are delivering real value in real organizations.

Slide 10

Slide 10 text

Our Cadence is Off: This is How it Was THE BUSINESS DEVELOPMENT IT OPERATIONS WATERFALL PROJECTS 10 RIGOROUS PROCESSES INNOVATION

Slide 11

Slide 11 text

DevOps Improves IT’s Cadence and Velocity THE BUSINESS AGILE | LEAN | DEVOPS CONTINUOUS DELIVERY* 11 WINNING THROUGH INNOVATION *The first of the 12 principles in the Agile Manifesto

Slide 12

Slide 12 text

The Wall of Confusion 12 DEVELOPMENT “I want change.” IT OPERATIONS “I want stability.”

Slide 13

Slide 13 text

DevOps Goals ●Smaller, more frequent releases ●Reduced effort and risks ●Reduced cost of product iterations and delays ●A culture of communication and collaboration ●Consistency and speed through automation Improvements in: ●Time to market/value ●Integration with the business ●Responsiveness ●Code and deployment quality ●Productivity ●Visibility ●Agility 13 The principles apply whether you are coding or configuring digital products and services.

Slide 14

Slide 14 text

DevOps Values •Culture •Automation •Lean •Measurement •Sharing 14

Slide 15

Slide 15 text

THE FIVE IDEALS 1. Locality and simplicity 2. Focus, flow and joy 3. Improvement of daily work 4. Psychological safety 5. Customer focus THE THREE WAYS 1. Flow 2. Feedback 3. Continuous experimentation and learning DevOps Values 15

Slide 16

Slide 16 text

The Three Ways 16 The First Way The Second Way The Third Way Flow Feedback Continuous Experimentation & Learning Understand and increase the flow of work (left to right) Create short feedback loops that enable continuous improvement (right to left) Create a culture that fosters: • Experimentation, taking risks and learning from failure • Understanding that repetition and practice is the prerequisite to mastery

Slide 17

Slide 17 text

17

Slide 18

Slide 18 text

18 CONTINUOUS INTEGRATION Using version control, all developers commit code to trunk at least once daily. On every commit, automated builds and tests are triggered. This practice leads to… CONTINUOUS DELIVERY Where software is always in a releasable state to be pulled by customers as and when they need the new features.

Slide 19

Slide 19 text

19 DEV BUILD UNIT TEST INTEGRATION TEST USER ACCEPTANCE TEST PRODUCTION DEV BUILD UNIT TEST INTEGRATION TEST USER ACCEPTANCE TEST PRODUCTION AUTOMATIC TRIGGER MANUAL TRIGGER CONTINUOUS DELIVERY CONTINUOUS DEPLOYMENT

Slide 20

Slide 20 text

POLL 20 Where are you at today?

Slide 21

Slide 21 text

21

Slide 22

Slide 22 text

22

Slide 23

Slide 23 text

Pathological (Power-oriented) Bureaucratic (Rule-oriented) Generative (Performance-oriented) Information is hidden Information may be ignored Information is actively sought Messengers are ‘shot’ Messengers are isolated Messengers are trained Responsibilities are shirked Responsibility is compartmentalized Responsibilities are shared Bridging is discouraged Bridging is allowed but discouraged Bridging is rewarded Failure is covered up Organization is just and merciful Failure causes enquiry Novelty is crushed Novelty creates problems Novelty is implemented Culture and the Flow of Information 23 Source: Westrum, A Typology of Organizational Cultures

Slide 24

Slide 24 text

24 And then there’s DevSecOps, SecDevOps, ChatOps, AIOps, GitOps, ProductOps, DataOps…

Slide 25

Slide 25 text

25 Not to mention Site Reliability Engineering, observability, chaos engineering…

Slide 26

Slide 26 text

26 Just think… Ways of Working

Slide 27

Slide 27 text

27