Bringing DevOps to Product
summary
Applies DevOps practices to the product-to-dev handoff and shows concrete changes: runs 15 value stream mapping workshops across three verticals and 12 business units, embeds product owners on teams, adopts a visible product task board and WSJF prioritization, builds an API bridge to automate handoffs, and makes tech debt a tracked “red card” with 20% time allocated. Results: lead time drops and teams ship 30% faster to market with fewer wasted features and shared business/technical metrics.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:13Howards Story
- 2:29Snark
- 3:55Yolo
- 4:14The Rant
- 5:41Growing Pains
- 7:39Standups
- 15:26Setting the deadline
- 17:03Essential properties
- 18:24North Georgia
- 19:06Why the pipeline
- 20:38Working together
- 21:23Three things to avoid
- 22:39Stop personal attacks
- 23:04Reacting is automatic
- 23:20Kobayashi Maru
- 26:25Conclusion
related talks
25mBringing Product thinking to DevOps
24mBringing Product Thinking into DevOps
43mBringing product thinking into DevOps
34mDevOps culture
45mDevOps Transformation — Breaking Down Walls
27mDevOps Champions: Leading the Transformation
25mDevOps Bringing a New Concept to Software Quality
17mBeyond DevOps – Holistic transformations in uncertain times
