Ten Ways to Doom Your DevSecOps
summary
Lists ten concrete failure modes and gives actionable counters: slow onboarding that takes days or months and kills engagement; a pretend cloud that hides behind tickets instead of self-service cloud APIs; mandated “agile” rituals and status rollups that block team autonomy; change control boards that DORA links to higher risk; emphasize Infrastructure as Code and immutable infrastructure to prove releases; too many decision makers and too many metrics; warns realistic expectations and disciplined incremental wins.
AI-written summary · about
chapters (13)
- 0:00intro
- 1:43preamble
- 2:14slow onboarding
- 3:09"cloud"
- 3:55"agile"
- 5:02change control board
- 6:15afraid to fail
- 7:25unchanging culture
- 8:37unchanging policies
- 9:48too many decision makers
- 10:43too many metrics
- 11:29unrealistic expectations
- 12:09summary, reach out!
related talks
07mTen Ways to Doom Your DevOps
05m5 Pitfalls of Using DevOps to Govern
29m5 ways to screw up your DevOps Transformation
43mTen DevSecOps Culture Failures
45mDevSecOps Worst Practices
17mDevOps Leadership in practice. True stories
33mThe DevOps disaster: 15 ways to fail at DevOps
32mTales from the DevOps Transformation Trenches
