Intel’s Journey to Large Scale DevOps Transformation
summary
Intel shrinks an eight‑week path to production by building a Common Continuous Delivery Service and running communities, hackathons and an internal open‑source catalog; a self‑built DevOps maturity model plus value‑stream Kaizen guides team targets. CI users grow 70 to 700 (a 10x CI users increase) but half remain inactive because dozens of stitched tools live under different owners. Low adoption shows in weak infrastructure‑as‑code and config management, and a persistent PII detection gap in security scanning.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:43About Intel
- 2:09Challenges
- 3:25Approaches
- 5:57Dont let tool be
- 8:36DevOps maturity model
- 10:53Value Stream Analysis
- 11:28Influencer Model
- 13:15Metrics
- 14:13Maturity
- 14:45Continuous Integration Tool
- 15:38Maturity Model
- 17:25Continuous Integration
- 17:52Configuration Management
- 18:21Future Target
- 18:46Key Takeaway
- 19:54Wish List
related talks
28mIntel’s Middle Out Journey to DevOps
22mA Healthier Software Development Life Cycle with DevOps
43mThe Road to DevOps
31mThe Continuous Culture
29mHunting the DevOps Whale
38mDevops in an Industrial Company: From Milestones to a Continuous Quality Assurance Approach
41mThe Introduction of DevOps in Large-Scale Organizations
37mWant to do the DevOps? Change Everything