Want to do the DevOps? Change Everything
summary
Claim: successful DevOps adoption requires changing organization, architecture, pipeline and culture together — you can’t just install tools. Example wins: a printer team rewrites firmware to move from maintenance to features; a travel company peels one service (hotel pricing) off a monolith and uses A/B tests on button color to lift conversions; a compliance example shows Cloud.gov handles 269 of 325 security controls, lowering team burden. Pitfalls: 90% mistook downloading Jenkins for CI; real CI runs every commit and fixes failures within minutes. Continuous delivery is the safety net that proves releases bad, not magically fast.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:45THE CHANGES IN TODAY'S TALK
- 4:29WHAT ISN'T DEVOPS
- 8:51TRADITIONAL MODEL
- 11:24MONOLITHS CAN BE HARD
- 12:51DEVELOP SMALLER PIECES MICROSERVICE ARCHITECTURE
- 16:01CAR AS A SERVICE
- 17:40AN EXAMPLE OF PLATFORM AS A SERVICE
- 19:38PRODUCT TEAMS
- 23:41CI THEATRE
- 27:31EXAMPLES OF THINGS WHICH ARE BAD
- 28:41OUR CONTINUOUS DELIVERY PIPELINE
- 32:36SUMMARY
related talks
34mYou only have to change one thing to do the DevOps
49m5 Steps to a DevOps Transformation
30m3 Practices for Effective DevOps Adoption
01h 02mWe have DevOps. No one was fired. But what to do?!
31mThe Continuous Culture
50mAdopting DevOps? You are Aiming at the Wrong Target!
54mEffective DevOps for Organizations
28mYou Can’t buy DevOps, but you may Need to Sell it