Compliance by Design | Continuous Compliance
summary
Project teams get concrete outcomes not slogans: practical steps for Compliance by design and continuous compliance that move regulation into CI/CD pipelines, use VSTS/Microsoft to link risks to unit tests, and auto‑generate regulator reports, cutting a medtech release burden from roughly 200 man hours to zero. Case studies include British Council IELTS work, fintech and Greensill failures, and an eye‑drop outbreak (68 infected, 4 deaths), showing what is built, how it’s monitored, and where it succeeds or still needs human oversight.
AI-written summary · about
chapters (6)
- 0:00Compliance introduction
- 7:34Why compliance matters
- 17:43Choosing compliance risks
- 26:50Traditional vs continuous
- 34:10Agile compliance integration
- 38:42Conclusion and key takeaways for compliance by design
related talks
05mHow To Automate Compliance If You Aren't Chuck Norris
10mTest Driven Compliance
33mCompliance as Code - Lessons Learned From Regulated Organizations
29mCompOps (Compliance Operations): Regulatory Cultural Change
41mCompliance & Regulatory Standards are NOT Incompatible with Modern Development
37mDevOps - The Automation of Compliance
33mNavigating Compliance: What Developers Can Learn From Driving
29mAutomating Continuous Compliance for Scalable SaaS Delivery