An Evolutionary Approach to DevOps
summary
A Chicago finance company (Enova) avoids a big‑bang rewrite and instead splits work into small platform teams (≈7–8 engineers), publishes public roadmaps and charters, and chooses tools by context not hype (tried Kubernetes and Terraform ideas but focuses on fit). The program ships iteratively — always be shipping — builds self-service interfaces with naming/tagging standards, automated PR checks, docs and weekly office hours, and measures success by reduced toil and faster, usable deliveries.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:51"CHANGE IS INEVITABLE. CHANGE IS CONSTANT." - BENJAMIN DISRAELI
- 4:31DEVOPS TEAM
- 6:30TWO PIZZA TEAMS
- 8:06INTERNAL VISION
- 8:50TEAM CHARTERS
- 9:33PROJECT MANIFESTOS!
- 10:24ROAD MAPS
- 12:00SHINY NEW TECH
- 13:14CONTEXT RULES EVERYTHING AROUND ME
- 14:29DON'T FEAR THE
- 15:59IF YOU BUILD IT THEY WILL COME!
- 18:54PRACTICAL PERFECT
- 21:41SQUARES INTO ROUND HOLES
- 24:56DOCUMENTATION! DOCUMENTATION!! DOCUMENTATION!!!
related talks
22mEvolving DevOps Teams and Flexible Organizational Culture
01h 02mThe Enterprise DevOps Challenge
34m(Re)building an Engineering Culture: DevOps at Target
22mA Healthier Software Development Life Cycle with DevOps
30mAdopting DevOps? You are aiming at the wrong target!
33mThe End of the Beginning
29mDevOps Anecdotes
29mHunting the DevOps Whale