DevOps Project Failures - Lessons Learned and Strategies for Recovery
summary
A panel reports concrete failures and fixes: a customer restores from a returned test device after ransomware because a test image kept real data; a risky rollout becomes stable when a multi‑continent Kubernetes platform with millions of devices is reimagined as a platform engineering product; CI pain points show 72% time spent maintaining tests and push adoption of observability tools like Playwright/Cypress trace replays and Replay IO; a pilot proves gamified testing increased adoption and taught which processes actually need documentation and drills.
AI-written summary · about
chapters (9)
- 0:00DevOps project failures
- 3:40Backup necessity myths
- 7:34Cultural misalignment
- 15:48Adoption challenges
- 24:49Vendor selection
- 27:20Business continuity
- 34:30Testing as defense
- 40:53Gamification for testing
- 45:31Q&A
related talks
17mDevOps Leadership in practice. True stories
42mLessons Learned as a DevOps Consultant
47mWhere the Security Rubber Meets the DevOps Road
02mOpening Remarks
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
45mDevSecOps Worst Practices
55mDevOps @Scale (Greek Tragedy in 3 Acts)
28mYou Can’t buy DevOps, but you may Need to Sell it