Day 1 Ask the Speaker
summary
Concrete outcomes and practices: pipeline work is handed to dedicated DevOps teams using a model-driven approach instead of sprawling diagrams, legacy tools like BladeLogic and HP PPM get replaced by simpler automation, and incidents fall from about 630 to 512 incidents per month. Early metric focus is year one: version control, teams adopt Chef and Kubernetes, databases consolidate from MongoDB/MySQL toward standards, compliance uses code checks like Inspec and managers experiment with the Atlantean monthly topics to change culture.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:10DevOps team structure
- 2:12Cultural challenges
- 4:00Retraining engineers
- 5:27Leadership focus
- 7:21Performance reviews
- 9:11Changing habits
- 12:09Starting DevOps
- 13:45Retraining management
- 16:53Over-communication
- 19:21Key metrics
- 21:30Choosing metrics
- 24:25Autonomy vs standardization
- 27:51Shared services
- 29:23Merging teams
- 31:49Leadership courage
- 33:15Cross-functional teams
- 36:18Outcome-based standards
- 37:36Standardization vs innovation
- 41:22DevOps costs
- 43:50Merging practices
- 45:37Working with auditors
- 48:14Inviting auditors
