Getting started with DevOps
summary
Defines DevOps as a value-stream practice drawn from Toyota lean principles and warns that culture change, not just tools, makes it work. Recommends starting with a small, visible project (example: a pilot across ~500 apps is feasible in stages), building CI/CD pipelines, automated unit-to-integration tests, containerized packages, and blue-green deploys so production becomes “just another environment.” Emphasizes continuous monitoring, logging, iterative learning, a platform team for shared services, and treating the flow as total end-to-end value stream.
AI-written summary · about
chapters (30)
- 0:00Welcome to DevOps
- 1:33What DevOps means
- 2:57Toyota and lean principles
- 4:23Agile and Scrum
- 5:48Breaking work into parts
- 6:32Collaboration challenges
- 8:20Breaking silos
- 9:22Value stream mapping
- 10:28Agile Scrum vs value stream
- 11:30Customer experience
- 12:34Implementing DevOps challenges
- 13:41Firefighting mindset
- 14:45Learning in DevOps culture
- 16:10Start small scale up
- 17:14Legacy systems flexibility
- 18:22PDCA cycle
- 19:02DevOps movement tips
- 19:46Open source tools
- 20:49Designing flexible apps
- 21:31Microservices architecture
- 22:13Automated testing CI/CD
- 23:18Containers pets vs cattle
- 24:44Release management
- 26:28Testing in production
- 27:11Config management
- 27:55Monitoring improvement
- 28:40Logging metrics
- 29:22DevOps team structures
- 30:29Platform teams role
- 31:12Q&A
related talks
09mexplains DevOps Culture
30m3 Practices for Effective DevOps Adoption
16mDevOps - Philosophy vs Practice
54mEffective DevOps for Organizations
08mGetting started with DevOps
41mThe Introduction of DevOps in Large-Scale Organizations
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
55mWe Are All DevOps