Bringing product thinking into DevOps
summary
Product teams pair with DevOps to reorder work by risk and context, not by tooling hype: teams build a prototype automated 80‑page regulatory PDF that pulls risks, stories and test results from Jira and wins regulator sign‑off, prioritize shipping production first so regulators can certify an environment that otherwise takes 2–3 months, and embed compliance and operations into squads to avoid retraining thousands of people weekly. They use story map sequencing, experience maps and value‑prop canvases to choose the next smallest valuable slice.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:44Continuous Delivery
- 15:48Tools
- 20:01Four tools
- 21:52User map
- 24:19Experience map
- 27:00Proposition canvas
- 28:23Sequencing
- 31:55Summary
- 32:35Mindset shift
- 33:06Challenges
- 35:58Inception
- 36:48Questions
related talks
25mBringing Product thinking to DevOps
24mBringing Product Thinking into DevOps
28mBringing DevOps to Product
44mDevOps in Regulatory Spaces: It's Only 25% What You Thought It Was…
43mRegulatory Compliance as a DevOps Enabler
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
37mDevOps - The Automation of Compliance
18mDesign Patterns For Efficient DevOps Processes