DevOps Days MTL 2019 - Steve Pereira
summary
Value stream mapping and simple flow measurement cut a six‑week customer onboarding down to four days by collapsing handoffs and empowering one person to own steps 1–10, and teams report typical improvements of tenfold on focused processes. Start with a whiteboard, estimate step timings, digitize with draw.io or Google Drawings, iterate every six months, avoid mapping 2,000 steps at once, and ensure people who do the work plus a decision‑capable stakeholder attend so change actually happens.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:25Next 20 years of DevOps
- 3:12High vs low DevOps performers
- 5:44Cost of misaligned handoffs
- 8:59Wasted time in meetings
- 9:41Tools vs process problems
- 11:32Value stream thinking
- 13:20Value stream mapping simplified
- 16:31Real-world mapping results
- 21:48Measuring process changes
- 24:44Sustainability in DevOps
- 25:46Starting with bottlenecks
- 27:17Q&A
- 28:41Q&A: Mapping frequency
- 29:24Q&A: Mapping pitfalls
- 31:08Q&A: Leadership buy-in
- 33:19Q&A: Mapping prerequisites
- 36:29Closing
related talks
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
06mEverything You Always Wanted To Know ...
49mProductivity Panel
27mHow I Wired the Winning Organization!
39mProject Management for Engineers
05mDevOps over time
27mDeveloping Devopsers
28mWhat Enterprise IT Can Learn From a Startup’s Journey