Banking on Continuous Delivery
summary
Capital One describes moving from waterfall to automated CD, building a software delivery cleanroom where every app, infra and test is in source control, every change is peer-reviewed, pipelines stop on failed checks and no one has access to production. They collect pipeline telemetry with Hygieia and Cloud Custodian to enforce controls and produce evidence in near‑real time. Result: flagged growth from ~20 products deploying multiple times/day in 2016 to ~300 in 2017, 25% of apps in the cleanroom today with a 50% target.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:23Different DNA
- 4:315 Year Journey
- 7:222017 and beyond
- 11:09Former Auditor's Perspective
- 11:48And at Capital One...
- 12:47Compliance vs Governance
- 13:16Three Lines of Defense
- 13:43What is the Developer's Role in Governance?
- 14:27Why Controls?
- 15:55Minimum Set of Controls
- 17:32Biggest hurdle
- 18:35Options
- 19:42Assumptions
- 22:33Software Delivery Clean Room
related talks
33mBanking on Innovation & DevOps
25mDevOps at Capital One: Focusing on Pipeline and Measurement
26mFrom 100 Pipelines to 1
23mHow Shifting Left is Helping CapitalOne in its CICD Pro...
41mEnable your team to do changes in production
32mContinuous Delivery Sounds Great But It Won’t Work Here
45mContinuous Delivery in a World of Constant Change
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases