Turning Around the Containership
summary
Four-year transformation inside a bank documents concrete wins and failures: initial focus on the wrong teams and the wrong toolset slows progress, then teams adopt Git, build CI/CD pipelines, and use Graphite/Grafana for metrics; an ops focus team is relocated to build a reproducible, automated platform with Puppet-style infrastructure as code practices and delivers a green pipeline deployed to production. Internal DevOpsDays and hackathons accelerate adoption, one formerly resistant Unix engineer becomes an evangelist, but the painful “middle” of reorg and skill gaps persists.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 1:51The problem: old ING
- 3:54Beginning the transformation
- 6:42Initial technical hurdles
- 8:22Navigating the middle pain
- 9:52Large-scale reorganization
- 12:24Building engagement
- 15:13Internal devops days
- 18:16Managing varying team speeds
- 21:24Integrating infrastructure
- 23:52Success stories
- 25:13Key takeaways and Q&A
related talks
20mJourney Of Devops Teams in a Corporate Environment
29mDevOps Mindset Transformation
30mHow We Led Three Banks Through DevOps Transformations
32mTales from the DevOps Transformation Trenches
17mBeyond DevOps – Holistic transformations in uncertain times
30mA Story of DevOps Transformations
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
27mThe Five Phases of DevOps