This document provides an overview of DevOps success including: 1) High-performing IT organizations that practice DevOps are able to deploy code more frequently, have faster lead times, and higher change success rates, leading to increased reliability, productivity, and market growth. 2) Organizations should align incentives, form cross-functional teams, and automate workflows to reduce manual work and cycle times for better visibility and job satisfaction. 3) Key DevOps practices include continuous integration, version control, and continuous delivery across all technologies to reduce deployment pain and increase deployment frequency. 4) When starting a DevOps transformation, companies should establish a single source of truth, standardize processes, iterate on those processes, and

1. A Roadmap for
DevOps Success
Michael Olson
Puppet

2. Agenda
Building the case
Aligning incentives & teams
Key technical practices
Where to start
Measuring results

3. Building the case

4. Ensure
reliability
Move
faster
Opposing Forces?

6. High-performing IT orgs are more agile
200x
More frequent
deployments
2,555x
Faster lead times
than their peers

7. High-performing IT orgs are more reliable
3x
Change success
rate
24x
Faster mean time to
recover (MTTR)

8. High-performing IT orgs are winning
1.5x
More likely to exceed
profitability &
productivity goals
50%
Higher market
capitalization growth
over 3 years

9. Employees in high-performing
organizations more likely to
recommend their organization
as a great place to work

10. Because they address security
at every stage, high-performing
teams spend less time fixing
security issues

11. High performers spend
29% more time on new work
than low performers,
and 22% less time on
unplanned work and rework
New work vs. unplanned work

12. Aligning incentives & teams

13. Organizational goals
Lack of alignment
Low trust culture
Siloed teams
Lots of manual work
Long cycle times
Poor visibility
High burnout
Aligned around goals
High trust culture
Cross-functional teams
Mostly automated work
Short cycle times
Fast feedback & insight
High job satisfaction
FROM:
FROM:
FROM:
FROM:
FROM:
FROM:
FROM:
TO:
TO:
TO:
TO:
TO:
TO:
TO:

14. Conflicting incentives
Business delivering value to customers
Dev teams delivering new features
Ops teams ensuring stability of systems
Quality teams ensuring quality of software releases

15. Aligned Incentives
Delivering
value to
customers
Business
Ops
teams
Quality
teams
Dev
teams

16. Typical Enterprise Org Structure
IT Operations
NOC
Commercial
Banking
Business Units
Credit Cards
Mortgages
Investment Banking
Systems Engineers
Network Engineers
Storage Admins
DBAs
InfosecDev teams reside in
business units

17. Pattern 1: Blended Dev & Ops teams
Dev Ops

18. Pattern 2: Cross-functional team
Characteristics
• Consists of devs, testers, ops, product
owner, etc.
• Focused on delivering a single
application
• Self-sufficient
• Optimized for throughput

19. Pattern 3: Temporary DevOps Team
Characteristics
• Consists ideally of devs with systems
experience, or sysadmins with
programming experience
• Focused on automating pain points
• Responsible for building a platform that
allows self-service
• Provides a toolchain to enable devs to
build, test and deploy their systems
• Coaches other teams
Dev Ops
Dev
Ops

20. Key technical practices

21. Continuous delivery drives results
Automation
Continuous
integration
Version control
These practices
lead to…
Less
deployment
pain
More frequent
deployments
Lower change
fail rates
Higher levels of
org performance
(productivity,
market share,
profitability)
Key technical practices

22. DevOps toolchain
… across all technologies.
Version control
Configuration
management
Continuous Integration
Deployment
tools
Monitoring
and
others
…
and
others
…

23. Where do you start?

24. DevOps Adoption Lifecycle
make it visible • share • measure at each stage
Stage 1: Establish a single source of truth
Stage 2: Standardize processes
Stage 3: Iterate on processes
Stage 4: Enable the business

25. Where to start
Collaboration IterationFast Feedback Visibility
Version
Control
Configuration
Management
Peer Review
Continuous
Delivery
Automated
Testing &
Deployments
Infrastructure as Code

26. Measuring results

27. What to measure?
Speed
• Deployment frequency
• Change lead time (from dev’s laptop to production)
• Cycle time
Reliability
• Change fail rate
• Mean time to recover
• Availability / downtime

28. Resources
Puppet 2016 State of DevOps Report: https://puppet.com/2016-devops-report
The Phoenix Project by Gene Kim
Continuous Delivery by Jez Humble