This document discusses eliminating barriers between development and operations teams through adopting a DevOps culture and shared practices. It addresses basic conflicts between wanting change versus stability and flexibility versus control. It presents models for DevOps delivery and dimensions to consider in people, processes, tools and governance. Challenges in culture change are discussed, with games used as an analogy for maturity. Metrics for measuring DevOps progress are proposed.
5. 5
DIMENSIONS TO CONSIDER
Enterprise Governance & Metrics
People and Organisation & Culture
Programme & Change Management
Technology &
Engineering
Tools
DevOps
Practices
@mircohering #notafactoryanymore
6. 6
WHY IS THIS HARD?
“ignorance more frequently begets
confidence than does knowledge”
Charles Darwin
@mircohering #notafactoryanymore
7. In a survey of faculty at the University of Nebraska, 68% rated themselves in the top 25% for teaching ability. -
Wikipedia
In a similar survey, 87% of MBA students at Stanford University rated their academic performance as above the
median. - Wikipedia
For driving skill, 93% of the US sample and 69% of the Swedish sample put themselves in the top 50% - Wikipedia
How do you think people would rate you as a leader?” It turns out that 74% of the respondents think they’re either
above average or the best leader their people have ever had. – SmartBrief on Leadership
Let‘s look at some examples
DUNNING KRUGER EFFECT - ILLUSORY SUPERIORITY
@mircohering #notafactoryanymore
8. 8
ORGANISATIONAL BLINDNESS IN ACTION
Impression of standard process across organisational levels (Quality Software
Management: First-Order Measurement (Quality Software Management) by
Gerald M. Weinberg 1991 )
67%
22%
CLOUD NIST
58%
46%
37%
C-SUITE MANAGER ENGINEER
Adoption across 15 criteria
@mircohering #notafactoryanymore
9. 9
WHAT COMPUTER GAMES CAN TEACH US ABOUT
MATURITY MODELS
@mircohering #notafactoryanymore
10. 10
THERE ARE COMMON PATTERNS
Throughput
Code &
Functional
Quality
SCM, Build, Deploy,
Environments
@mircohering #notafactoryanymore
11. Model A
DEVOPS DELIVERY MODELS
Model C
Continuous Delivery
Automated Application Deployment
into Persistent Environments
Automated environment provisioning:
Cloud provisioning of Environments is part of
the Deployment process
Model B
Container-based Deployment:
Container-based deployment of
Microservice based application
services
24/7
11@mircohering #notafactoryanymore
16. A DEVOPS BLUEPRINT
DEV
PPTE
NFT
PROD
SITx
Workflow
Management
IDE
Defects
Retrofits
Requirements
Technology
based
Source Control
Source code
Documentation
Build Server Build Store
Build Scheduler
Build & Deployment Orchestration, Automation &
Governance
Extract
Store
Deploy
Automated
Regression
Cycle
Automated
Regression
Cycle
Automated
Regression
Cycle
Test Management
Service
Virtualisation
EnvironmentsSoftware Delivery Testing
Analytics
Dashboards Build Health
Continuous
Improvements
Reporting & Metrics
Deployment duration
Deployment
Defects
Orchestration, Automation
& Governance
Environment provisioning & tests
Compute Network Storage
Configuration
Management
Environment
Design & templates
Initiate
Monitoring
(Functional & Non-
Functional)
Platform Delivery
Test data
management
Test
Architecture
Test Automation
Data
Warehouse
16@mircohering #notafactoryanymore
17. DEVOPS TOOLS SHOULD FOLLOW DEVOPS PRACTICES
17
Fit-for purpose
Compatibility with tech &
app stack
Licensing (Open Source,
Commercial)
Config as Code /
Dev -> Prod promotion
Integration with other tools
Ease of configuration
5
Skills (Organisation & Market)
6
7
1
2
3
4
@mircohering #notafactoryanymore
18. USING A VALUE STREAM MAP TO GOVERN YOUR DEVOPS
ADOPTION
Collaborative Discussion on Process and Gaps
Documented Process
Reporting on progress and status
Do we do this
here or there?
Not sure – let
me call someone
who knows
18@mircohering #notafactoryanymore
19. DB INC
DAY 0
DEVOPS DEPLOYMENT DIAGRAM
EMAIL PRE CHECK DEPLOY
TECH VAL
POST CHECK
FUNC VAL
EMAIL SHAKE-DOWN
Cycle Time
Prep Time Deploy Time VAL Time
LIVE
MT
SA
MT
MAN
MANUAL
CIX - 0 Hours
iDEV - 7 Hours
TST - <> Hours
Failure Rate Failure Rate Failure Rate Failure Rate
CIX 15% N/A 10% N/A
iDEV N/A N/A
TST N/A N/A
CIX - 24 Hours
iDEV - <> Hours
TST – <> Hours
DAY 0
MT
SA13
27% 73%
Number of process
activity
Level of Automation
(%)
Level of Manual
Intervention (%)
<>
AUTOMATED
LEGEND
CIX - 3 Hours
iDEV - <> Hours
TST - <> Hours
CIX – 0.5 Hours
iDEV - <> Hours
TST - <> Hours
TECH CONF
19@mircohering #notafactoryanymore
20. WHAT METRICS ARE GOOD METRICS
20
Traditional Teams Agile Teams
Measure Outputs Measure Outcomes
Measure Activity Measure Results
Measure Time Spent per Task Measure Work Items Completed
Assess Snapshots Assess Trends
Provide Feedback Infrequently Provide Feedback Frequently
Use Metrics for assessment Use Metrics to Inform Program Decisions
Performance
Results
Throughput,
Efficiency
Trends, Flow
Feedback
Value of
Measurement
Performance
Results
Throughput,
Efficiency
Trends, Flow
Feedback
Value of
Measurement
@mircohering #notafactoryanymore
21. 21
HOW DO WE KNOW WE ARE
GETTING BETTER?
Deployment Success
rate
Change failure rate
Production Incidents
& Defects
Change Leader &
Cycle Time
Transaction Cost
Mean Time to Detect
Mean Time to
Restore
eNPS
% Engineering
bNPS
@mircohering #notafactoryanymore
23. THE EVALUATION CHALLENGE -PART 2
@mircohering #notafactoryanymore
First Time Resolution
Rate/Resolution TimeSLAs
23
24. WANT MORE LEARN MORE?
To receive the following:
A copy of this presentation
An excerpt of DevOps for the Modern Enterprise
Videos and slides from my DevOps Enterprise talks
Most popular blog posts from notafactoryanymore.com
Get early access to any material coming out with
“DevOps For the Modern Enterprise”
Just pick up your phone and send an email:
To: mirco@SendYourSlides.com
Subject: devops
@mircohering 24