DevOps Culture & Practices to Create Flow
summary
Shows concrete outcomes and engineering work: a Google-scale CI system runs >60 trunk check-ins per minute at peak, >100 million test cases and 4,000 CI builds per day to give immediate feedback; Toyota’s andon analog gets pulled ~3,000 times a day. A 400-person HP LaserJet firmware team rewrites the codebase, uses feature toggles and a staged deployment pipeline (per-change two-hour tests, batched merges, hardware-board tests, 30k overnight test hours) and cuts support and branch porting while raising innovation eightfold.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:29the production line?
- 2:44lean product dev vs manufacturing
- 8:31toyoda automatic loom, typeg
- 9:10toyoda automatic loom, wpeg
- 21:40deployment pipeline
- 30:24hp laserjet firmware team
- 32:07the economics
- 34:26improvement kata
- 43:28high trust culture
- 45:01leadership
- 46:35takeaways
- 46:59jesse's rule
- 47:22questions
related talks
30mPushing to master - adopting trunk based development
22mA Healthier Software Development Life Cycle with DevOps
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
25mDevOps Handbook Experiments in Accelerating Delivery
34mDevOps: Next
45mDevOps: The Key to IT Performance
01h 01mA team's transition to Continuous Delivery
43mThe Road to DevOps