DevOps at Kaiser Permanente: Overcoming 75 Years of Inertia in Healthcare
summary
Kaiser Permanente runs a measured DevOps push that finds 66% waste in legacy release pipelines and quantifies it as $864k/month lost, then shifts kp.org from two-month batch releases to a two-week cadence with five integrated pipelines, automated tests, and 450 commits per day. The team builds a “factory of the future,” onboards squads (aiming for 20 squads), posts retros openly, hits 20+ production releases since April, and moves kp.org to cloud by 2019.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:35Who am I
- 3:06Digital Engagement
- 4:16The Oh Shit Moment
- 7:18Compelling Why
- 12:48Blockers
- 14:53Getting past it
- 19:49Where are we
- 22:26What about our workforce
- 23:37QA
related talks
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
26mDevOps and Lean in Legacy Environments
22mA Healthier Software Development Life Cycle with DevOps
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems
54mFrom Code to Customer
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
27mDevOps Champions: Leading the Transformation