DevOps in Regulatory Spaces: It's Only 25% What You Thought It Was…
summary
DevOps teams scale into regulated health‑science by turning tools into auditable platforms: a Greenfield DevOps stack evolves into a qualified Robot Framework and Jenkins pipelines that chunk deployments, cut documentation time dramatically, and produce evidentiary artifacts on commit. Quality sits at the table as a second customer, intent is questioned to right‑size controls, and release docs are assembled at commit not retroactively. Measured adoption climbs as automation replaces paper stacks and inspection time drops, enabling faster, controlled delivery of validated systems.
AI-written summary · about
chapters (37)
- 0:00Introduction
- 2:16The Journey
- 4:22Disclaimer
- 4:36Health Science
- 6:25Technology Data
- 7:56Where We Are Now
- 8:54Inspiration
- 9:32What they start learning
- 9:47When they get in their groove
- 10:24Software
- 10:54Quality
- 11:57Technology
- 12:13Diversity
- 13:01Becoming an Orchestrator
- 13:42Quality Organisation
- 15:22Conceptual Tools
- 16:32Terms
- 18:55Qualifications
- 20:06Scaffolding
- 21:28DevOps and Programming
- 22:29Principles
- 24:48Florida
- 25:20The intent
- 26:36Common interests
- 28:34Common ground
- 28:59Boil the ocean
- 32:09Examples
- 32:35Robot Framework
- 33:33Paper Audits
- 34:54Automation Audits
- 36:26Automation Audit
- 37:07Release Documentation
- 38:45End Result
- 39:13Reduce Risk
- 40:01Adoption
- 40:33Summary
- 40:43Conclusion
related talks
22mDevOps in Regulated Industries: What to do when Internal Audit says ‘No!’
43mRegulatory Compliance as a DevOps Enabler
37mDevOps - The Automation of Compliance
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
43mBringing product thinking into DevOps
30mProve it! The Last Mile for DevOps in Regulated Organizations
21mDevOps in a Highly Regulated Financial Infrastructure Company
38mDevops in an Industrial Company: From Milestones to a Continuous Quality Assurance Approach