DevOps Transformation — Breaking Down Walls
summary
Describes transforming DevOps practices in a large, 15-year-old product with millions of lines of code and many external partners where feature delivery to partner installations currently takes about two years. Covers problems of modernizing delivery velocity in legacy environments and outlines practical approaches and tools for shortening the cycle (continuous delivery, automation and organizational changes) without rebuilding the product from scratch.
AI-written summary · about
chapters (26)
- 0:00DevOps transformation intro
- 1:25Two-year release cycle
- 5:34Long release cycle problems
- 7:42Three key problems
- 8:23Dev vs auto-test history
- 12:49Wall: devs vs auto-testers
- 14:16Integrating auto-testing
- 17:34Auto-testing takeaways
- 18:17Dev vs QA history
- 20:05Wall: devs vs QA
- 21:09Tools for QA issues
- 22:15Design-first testing
- 23:18No separate QA teams
- 24:01Wall: dev teams
- 26:17Introducing DevOps team
- 27:45Fixing DevOps missteps
- 29:27Building DevOps team
- 31:21Final results and improvements
- 31:43Q&A: Manual checklists
- 34:13Q&A: Team size limits
- 35:38Q&A: Architecture impact
- 36:46Q&A: Dev role acceptance
- 38:32Q&A: Agile and Jira
- 40:11Q&A: Dev motivation for testing
- 42:00Q&A: Test design and coverage
- 43:05Q&A: Coverage and regression
related talks
17mBeyond DevOps – Holistic transformations in uncertain times
29mDevOps Transformation at Scale
30mWhat's It Like When DevOps Is Just Another Day at the Office?
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
27mDevOps Next
49m5 Steps to a DevOps Transformation
38mDevOps transformation – the good, the bad and the ugly
34mYou only have to change one thing to do the DevOps