webinar: a roadmap for devops success
TRANSCRIPT
A Roadmap for DevOps SuccessMichael OlsonPuppet
Agenda
Building the case
Aligning incentives & teams
Key technical practices
Where to start
Measuring results
Building the case
Ensure reliability
Move faster
Opposing Forces?
High-performing IT orgs are more agile
200xMore frequent deployments
2,555xFaster lead times than their peers
High-performing IT orgs are more reliable
3xChange success rate
24xFaster mean time to recover (MTTR)
High-performing IT orgs are winning
1.5xMore likely to exceed profitability & productivity goals
50%Higher market capitalization growth over 3 years
Employees in high-performing organizations more likely to recommend their organization as a great place to work
Because they address security at every stage, high-performing teams spend less time fixing security issues
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
Aligning incentives & teams
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:
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
Aligned Incentives
Delivering value to
customers
Business
Ops teams
Quality teams
Devteams
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
Pattern 1: Blended Dev & Ops teams
Dev Ops
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
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 OpsDevOps
Key technical practices
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
DevOps toolchain… across all technologies.
Version control Configurationmanagement Continuous Integration Deployment
tools Monitoring
andothers
…
andothers
…
Where do you start?
DevOps Adoption Lifecyclemake 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
Where to start
Collaboration IterationFast Feedback Visibility
Version Control
Configuration Management Peer Review Continuous
Delivery
Automated Testing &
Deployments
Infrastructure as Code
Measuring results
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
Resources
Puppet 2016 State of DevOps Report: https://puppet.com/2016-devops-report
The Phoenix Project by Gene Kim
Continuous Delivery by Jez Humble