... frustrated Ops guy. Chaos, mayhem, and screaming. A few deaths⦠No. DevOps. Jurassic Park, 1993 ... Tip 5 of 7. Do
7 Tips to get started with Enterprise DevOps Chris Phillips Managing Consultant 19th October 2016
Why do DevOps? Dennis Nedry – maverick Dev guy
Ray Arnold – frustrated Ops guy
No DevOps
Chaos, mayhem, and screaming. A few deaths…
Jurassic Park, 1993
Why are we even having this conversation? What is so difficult about it? VISIBILITY Peak of Inflated Expectations
Plateau of Productivity
Slope of Enlightenment
Trough of Disillusionment Technology Trigger
Gartner Hype Cycle
TIME
Geoffrey Moore’s “Crossing the Chasm”
“I have not failed. I've just found 10,000 ways that won't work” Thomas A. Edison (1847-1931)
4
Case Study – Company Profile – International corporation – 30 million customers, $100 billion annual revenue – 50,000 employees
– Situation – Inefficient, manual processes – Inconsistent environments – Lack of integration between tools – Lack of collaboration between project, transition and operational teams, as well as third party providers
– Started a DevOps pilot
Doing all the right things… – Started with The First Way – systems thinking and seeking to increase flow
– Used lean thinking and value stream mapping – Identified low hanging fruit – Defined future blueprint, operating model, and roadmap – Implemented pilot to budget
Outcome – Single-click provisioning of dev and test environments
– Then what?
– Environments provisioned in hours, not weeks
– Project halted due to lack of funding
– Consistent environments throughout dev and test
– Environment switched off
– Operating system, middleware & databases, applicationunder-test
– Why?
– Project viewed as a success and next steps identified
We Need to Talk About the Metrics!
Why no metrics?
How DevOps projects often start (and end)
Business
Language Barrier
Skunkworks DevOps Project
Ops
Dev Departmental Silo Barrier
Tip 1 of 7 Define the value, in business terms Time to Market
Velocity
Revenue & Margin
Productivity
Quality
Regulatory Compliance Customer Satisfaction Reduced Costs
11
Tip 2 of 7 Get Management buy-in – Needed for funding, vision, leadership
– Educate – Link to strategic initiatives
12
Tip 3 of 7 Define and build a metrics system, before you change anything – For example – Frequency of deployment – Speed of deployment – Deployment-to-staging success rate – Deployment-to-production success rate – Incidents and defects
– Feature usage – Mean Time To Restore Service (MTTRS)
13
Tip 4 of 7 Expect fear and resistance to change – plan to address
14
Tip 5 of 7 Don’t get distracted by the toys tools
15
Tip 6 of 7 Allocate full-time resources – Scrum participation
– All work should be backlog driven etc. – Day jobs will kill the project
16
Tip 7 of 7 Pick a low-risk starting point
Early high-profile failure creates a bad image of "this DevOps thing"
17
My top 7
Define the value, in business terms Get Management buy-in Define and build a metrics system, before you change anything Expect fear and resistance to change – plan to address Don’t get distracted by the tools Allocate full-time resources Pick a low-risk starting point 18
19
