The Essentials of Digital Experience Monitoring_ A Comprehensive Guide.pdf
Continuous Delivery - The Next 10 years
1. Dave Farley Jez Humble
http://www.davefarley.net Google
@davefarley77 @jezhumble
https://www.continuous-delivery.co.uk
Continuous Delivery -
The Next 10 Years
cloud.google.com/devops
3. the unix way?
1. Make each program do one thing well. To do a new job, build afresh rather than complicate
old programs by adding new “features”.
2. Expect the output of every program to become the input to another, as yet unknown,
program. Don't clutter output with extraneous information. Avoid stringently columnar or
binary input formats. Don't insist on interactive input.
3. Design and build software, even operating systems, to be tried early, ideally within weeks.
Don't hesitate to throw away the clumsy parts and rebuild them.
4. Use tools in preference to unskilled help to lighten a programming task, even if you have to
detour to build the tools and expect to throw some of them out after you've finished using
them.
Doug McIlroy, E. N. Pinson, B. A. Tague (8 July 1978). "Unix Time-Sharing System Forward". The Bell System Technical Journal. Bell Laboratories. pp. 1902–1903.
21. Change Approvals
Trust
less
Burnout
less
Deployment Pain
less
Rework
Autonomy Retrospectives
Culture and Work Environment
Westrum
Organizational Culture
Culture of
Psychological Safety
Climate for
Learning
Job
Satisfaction
Identity
SDO Performance
Availability
Lean Product Development
Technical Practices
Database Change
Management
Test
Automation
Deployment
Automation
Trunk-Based
Development
Shift Left
on Security
Loosely Coupled
Architecture
Empowered
Teams
Continuous
Integration
Continuous
Testing
Version
Control
Test Data
Management
Monitoring &
Observability
Proactive
Notifications
Code
Maintainability
Work in
Small Batches
Make Flow of
Work Visible
Gather & Implement
Customer Feedback
Team
Experimentation
Transformational Leadership
Vision
Inspirational
Communication
Intellectual
Stimulation
Supportive
Leadership
Personal
Recognition
Lean Management
Limit Work in
Process (WIP)
Visual
Management
Feedback from
Production
Heavyweight Process
decreases
Clear
Process
Voice
Organizational Performance
Commercial
Performance
Non-commercial
Performance
Software Delivery
Performance
Continuous
Delivery
Cloud
Infrastructure
Predictive Relationship:
Colors are for readability
and do not have meaning
Second - order construct
Constructs grouped by
theme: For readability, this
has no statistical meaning
Functional Outsourcing
decreases
Disaster Recovery
Testing
DORA Research Program
Created January 17, 2020. An interactive version of this diagram with descriptions
of the capabilities is at https://bit.ly/dora-bfd. Our guide to DevOps, along with six
years of State of DevOps Reports, is at https://cloud.google.com/devops
https://bit.ly/dora-bfd
81. @jezhumble
design vs delivery
Product Design and Development Product Delivery (build, testing, deployment)
Create new products and services that solve
customer problems using hypothesis-driven delivery,
modern UX, design thinking.
Enable fast flow from development to production
and reliable releases by standardizing work,
reducing variability and batch sizes.
Feature design and implementation may require
work that has never been performed before.
Integration, test and deployment must be performed
continuously as quickly as possible.
Estimates are highly uncertain. Cycle times should be well-known and predictable.
Outcomes are highly variable. Outcomes should have low variability.
The DevOps Handbook; also
84. Dave Farley Jez Humble
http://www.davefarley.net Google
@davefarley77 @jezhumble
https://www.continuous-delivery.co.uk
Thank you!
cloud.google.com/devops