Bringing Product Thinking into DevOps
summary
Argues that delivery pipelines must be managed as products, showing concrete wins: a medical services client moves from releases every three months to days by automating release evidence and certification, a fintech uses LaunchDarkly feature flags for safe continuous deploys, and a bad tool choice (using bash vs python) nearly derails work. Recommends using Wardley maps, service blueprints and story maps, adding a product lead or short product sessions to prioritize and sequence pipeline work.
AI-written summary · about
chapters (6)
- 0:00Pipeline as a product
- 3:56Treat pipelines as product
- 8:53Product mindset for pipelines
- 13:03Steps to add product thinking
- 21:55Benefits and tips
- 24:00Q&A
related talks
25mBringing Product thinking to DevOps
28mBringing DevOps to Product
30mEverything Is A Product...
43mBringing product thinking into DevOps
28mThe DevOps Pipeline
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
41mThe Pipeline-Driven Organization
05mHow I Started Worrying and Stopped Loving DevOps
