DevOps Transformation at Absa Bank: Technical Evolution; Cultural Revolution
summary
Absa builds an isolated engineering network on AWS and automates infrastructure with Chef and Chef Automate plus CI/CD (Chef Workflow, Jenkins/Bamboo); provisioning drops from six weeks to 30 minutes by exposing an internal orchestration product called Reason that calls Chef and AWS. Dev environments are destroyed weekly and rebuilt, teams scale from a seven‑person seed to ~25, pipelines enforce cookbook promotion, and incidents trigger collective on‑call fixes — the system proves faster velocity and fewer manual touches.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:03The DevOps journey
- 6:44Challenges
- 9:20Process
- 11:10Tools Journey
- 16:40New Process
- 19:30Culture
- 26:55What we want to do
- 27:52What should you do
- 29:33Short answer
- 30:02Tools used
- 31:08The journey
- 33:55Isolation
- 36:52Management layers
- 38:47Measuring the change
- 40:19Customer measurement
- 41:42Whats next
- 42:28How do you get people to be
- 47:10Deployments
related talks
26mDevOps success story
17mDevOps Journey at ABN AMRO
38mFrom Science Experiment to Enterprise Rollout
17mBeyond DevOps – Holistic transformations in uncertain times
26mCase Study of Success
34mDevOps Transformations At National Instruments and...
28mDevOps at American Express
26mDevOps in a Data Warehouse: Inside Out