How a Business Exec Led Agile, Lead, CI/CD
summary
A business-led change program remakes an enterprise data warehouse by introducing scaled agile, a dedicated integration/system team, and CI/CD pipelines. The team discovers 4,000 batch jobs causing 24‑hour runs and a 50% source‑code mismatch, inserts a caching workaround to get results, and automates environment provisioning from 6–8 weeks → 1 day. Continuous integration and automated deployment cut weekend deploys from three people all day to one person, and customer sentiment jumps -100 NPS → +50.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:22Ems story
- 3:30Business sponsor
- 4:23Project history
- 6:51Getting started with Agile
- 7:41First Agile team
- 9:08Batch schedule
- 10:55Agile
- 12:00Agile Retrofits
- 13:16Integration in Build
- 15:06Changing of the Guard
- 18:37Automating Deployments that didnt go well
- 20:29Automated Deployment
- 23:54Challenges
- 25:51Culture
related talks
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
44mBreaking a Monolithic Devops
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
17mBeyond DevOps – Holistic transformations in uncertain times
51mSabotaging a Transformation
01h 01mA team's transition to Continuous Delivery
30mHow DevOps is Enabling Lean Application Development
43mThe Road to DevOps