DevOps Transformation at Scale
summary
Starts with Scrum then removes sprint commitments for single-piece flow and strict WIP limits, uses a value‑stream workshop and the DORA assessment to prioritize work. A model‑line team is built to eliminate handoffs, compressing the value stream from 187 steps (8 handoffs) to 111 steps across the area and under 50 for the model line with handoffs 8→4 and model line 0. Cycle time drops from 84 days to 22 days (74%); next focus is CI/CD and automation and an internal DevOps learning track (Kubernetes, cohorts).
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:25The Starbucks Mission
- 0:56How large is Starbucks
- 1:22Point of Sale
- 2:09Bio
- 3:42How do you start
- 5:07Scrum Transition
- 5:39Stay the Course
- 6:10Colocated Teams
- 7:00Aha Moment
- 8:30Scrum retrospectives
- 10:14The next phase
- 11:18The value stream
- 13:44The team
- 15:18The workshop
- 15:50Improvement requires change
- 16:33Make space
- 17:20Whip is painful
- 18:27Journey map
- 18:53DevOps Assessment
- 20:28Failure Bow
- 22:47Experimentation
- 24:01Team
- 24:55Learnings
- 25:49Results
- 26:55Next Phase
- 27:13Continuous Learning
- 28:03DevOps Community
- 28:31Conclusion
related talks
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
45mDevOps Transformation — Breaking Down Walls
27mDevOps Champions: Leading the Transformation
34mDevOps culture
43mAbout to Start Your Nth DevOps Transformation?
39mGetting started with DevOps
24mHow DevOps changed the way we operate software
01h 00mDevOps – Value at Speed