We don’t need another hero
summary
Argues that removing single-person heroics requires changing flow, not just culture, and gives concrete results and tools: value stream mapping shows 9 days value vs 9 weeks waste, a dedicated transformation team builds a parallel pipeline, and deployments shrink from 3 weeks to 1 hour (target half an hour). Uses SRE principles, infrastructure-as-code, on-demand envs, and a CI/CD pipeline with AWS, Docker, Kubernetes, Jenkins, SonarQube and Artifactory to automate testing, tagging and fast feedback.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:16Nagre’s innovation history
- 3:26Why innovation is critical now
- 6:18The danger of software heroics
- 9:16What DevOps really means
- 11:23Breaking down value stream walls
- 13:53Mapping your value stream
- 16:21Principles of flow in DevOps
- 19:54Nagre’s DevOps transformation goals
- 21:41How Nagre implemented DevOps
- 25:35Nagre’s continuous delivery pipeline
- 27:19Getting started with DevOps
- 29:11Conclusion and Q&A
related talks
26mPrevent Heroism: How to Work Today Reduce Work Tomorrow
52mZero to Hero: Start the DevOps Transformation Today
35mThree Steps to Change: Lessons from Battling Bureaucracy
29mDevOps Transformation at Scale
05mThe Road to DevOps Success: It’s Human
32mTales from the DevOps Transformation Trenches
05mHow 500 People Changed Their Delivery Culture
38mDevOps transformation – the good, the bad and the ugly