DevOps in Regulated Industries: What to do when Internal Audit says ‘No!’
summary
A study of 100+ cases shows adopters reporting a 20–25% revenue lift year‑on‑year when BizDevXOps is fully in place. The talk lays out three organizational models: strict Dev/Ops separation, squads-with-chapters, and fully integrated teams that enforce segregation of duty at the process level (one client succeeds by tool‑enforced peer approvals). Key fixes are traceability, automation, centralizing regulatory work, reserving capacity, and stopping devs wasting 80% time on paperwork.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:25DevOps myths in regulated industries
- 2:26Key challenges overview
- 3:30Failure culture vs zero audit
- 6:19Why embrace DevOps
- 8:30Segregation of Duty setup
- 11:44Dev and Ops collaboration
- 14:14Process-level segregation
- 16:44Key learnings and strategies
- 19:57Automation and talent retention
- 21:02Closing
related talks
44mDevOps in Regulatory Spaces: It's Only 25% What You Thought It Was…
21mDevOps in a Highly Regulated Financial Infrastructure Company
27mDevOps Next
34mDevOps: Next
16mDevOps and the Bottom Line
43mRegulatory Compliance as a DevOps Enabler
32mDevOps as Driver of Organization-Wide Change
47mOvercoming Obstacles to DevOps