DevOps Culture It’s not just the tools Bob Payne VP Consulting LitheSpeed...
-
Upload
morgan-oconnor -
Category
Documents
-
view
217 -
download
0
Transcript of DevOps Culture It’s not just the tools Bob Payne VP Consulting LitheSpeed...
Bob Payne
• 15+ years of Agile • VP LitheSpeed Enterprise
Consulting • Agile Enablement that’s
pragmatic, not prescriptive
• Host of “Agile Toolkit Podcast”
• Chair AgileDC conference• Speaker all over
2
[email protected]@AgileToolkit
A Bit of History
And you may ask yourself-Well...How did I get here?
Same as it ever was...Same as it ever was...
Traditional Development Model (V-Model)
http://www.ambysoft.com
• BRUF/BDUF approaches often result in wastage (build to specification instead of something the stakeholders actually need)
• Hand-offs inject defects• The longer the feedback cycle the the greater the average
cost of fixing a found defect• Total Cycles get Longer and Longer
Dealing with Uncertainty
What to build: End uncertainty
How to build it: Means uncertainty
Who to build for: User uncertainty Better Plan
Agile is at its best when you need to learn.
Initial Plan
Empirical methods monitor progress & direct
adjustments.
Feedback: Agile Manifesto Recipe
Individuals and
interactions
Working software
Customer collaboration
Responding to change
1st Agile Principle
Our highest priority is to satisfy the customer through
early and continuous delivery of valuable software
7
Even if Development is Agile, we can still hit the “Wall” of Confusion
Icons: http://dev2ops.org
Historical Divide
8
Where is business in this picture?
What is DevOps?
It is...Not• Tools that can be purchased• A role or even a team• Prescriptive
It is…• Integration of Development and
Operations• Feedback across Business, Delivery, Run• Automation and Behaviors over
Documentation and Gates
• Most of all …. A Competitive Advantage
Showtime! What is DevOps
DevOps: From Idea to Outcome
DevOps
Idea Delivery
Business
Outcome
Measure and Learn
Delivery: To bring about true business agility, the entire development-to-operations lifecycle should be treated as a single end-to-end unified process
12
Yes Tools Matter
13
Business Agility: How Fast can you Learn?
• Only as fast as you can get feedback
• Real feedback comes from customers
• Only Outcomes Matter
• Outcomes come from Deployed Software
• Why does this matter?
Avoid the Fate of Nokia!Failure to Innovate or Even Respond Rapidly Killed their Market Dominance
Customers loved this…
…Until they tried this…
“While Nokia phones used to be prized in Asia and other developing economies for their durability and value, the company was late to introduce innovations like touch screens. That left the high end of the market to brands like Apple and Samsung.”
– New York Times, Sept. 2013
Showtime! Spotify
DevOps – CALMS Model
17
DevOps – CALMS Model
CultureHearts and minds, embrace the whole team
AutomationOf all (most) things; testing, deployment, infrastructure
LeanSmall batch sizes, value for end-users
MeasurementOf all things; show the improvement (adaption)
SharingTransparent, open
18
Culture Shock
• All In Now … No Silos
• Integrate Continuously
• Quality is Continuous
• Deployment is Automated
• Delivery is Continuous
• Build Measure Learn Operate
• Break Things…In Production
All In Now…No Silos … No Walls
Continuous Integration
Write a new test
Test Fails
Write Code
Test Passes
Clean up code, make sure tests
pass
IntegrateRed, Green, Refactor
Developer heartbeat
Quality is Continuous, NOT a Phase
http://testobsessed.com/
Continuous testing is the only way to ensure continuous progress.
Continuous Deployment
Commit stage
CompileUnit TestsAnalysis
Acceptance test stage
User acceptanc
etesting
Performance testing
Deploy to Productio
n
Faster Feedback
Higher Confidence / More Production-Like Environments
Pipeline stages = feedback opportunities
Continuous Delivery: Overview
24
http://ptgmedia.pearsoncmg.com/images/art_humble_continuousdelivery/elementLinks/humble_fig01.jpg
Ideas
Development/Test + Continuous Integration
Build, Measure, Learn, Operate
25
Continuous Deployment
Automate InfrastructureOperate and Measure
Version Code + Infrastructure
Break Things…In Production
• Chaos Monkey: Randomly disables our production instances
• Latency Monkey: Induces artificial delays to RESTful calls
• Conformity Monkey: Finds instances that don’t adhere to best-practices and shuts them down
• Doctor Monkey: Shuts down unhealthy instances• Janitor Monkey: Ensures that our cloud environment
is running free of clutter • Security Monkey: Finds security violations or
vulnerabilities and terminates the offending instances. • 10-18 Monkey: Detects problems in languages and
character sets• Chaos Gorilla: Simulates an outage of an entire
Amazon availability zone
DevOps Goals & Benefits
Quality
Reduce Risk Culture Change (no silos)
Continuous Improvement
(Adapt)CustomerValue
(short lead times) Embedded
Governance without gates
Single Piece Flow
Limit WIP
27
Wrap up
• What’s your delivery lifecycle today and what do you want it to be?
• How can you detect failures earlier?
• How can you increase collaboration to diagnose and remediate faster?
• How can you best pursue continuous experimentation and learning?
28