DevOps Bringing a New Concept to Software Quality
summary
A DevOps case about a messaging-style product used by 30 teams across three regions introduces core CI tests to prevent cross-team breakages. The rollout started with a few checks that produced noisy failures traced to developer-environment and process problems; a “quality babysitter” reproduced commits locally, trained teams, and coordinated fixes. The test suite expanded from about 100 to ~240 automated tests, pipeline time increased by roughly 15 minutes, stabilized within three sprints, and full-day outages disappeared.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:11Quality passion
- 5:20DevOps culture
- 6:52WhatsApp-like challenge
- 10:48Training and logs
- 13:15Team resistance
- 14:42Babysitter approach
- 17:51Maturity and dynamics
- 20:41Results and success
- 22:49Testing pipeline
- 23:53Frustration lesson
- 24:59Conclusion and Q&A
related talks
20mEnsuring Quality in DevOps Culture
38mDevops in an Industrial Company: From Milestones to a Continuous Quality Assurance Approach
25mDevOps Handbook Experiments in Accelerating Delivery
24mHow DevOps changed the way we operate software
43mThe Road to DevOps
34mDevOps: Next
36mDevOpsSup - Extended DevOps approach
47mHow Testing is Evolving in DevOps
