Ignite: Escaping the Black Hole of Release Management
summary
Teams spend 65% of time on release management across five languages, ten enterprise CMSs, five databases and 40–50 concurrent projects. The claim is that incremental automation and treating configuration as code turn manual toil into a buildable pipeline: automate one weekly task, use freed time to automate the next, attack the current bottleneck, enforce push controls and share ownership. That approach produces momentum, uncovers new bottlenecks like QA, and measurably frees time for improvement.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:43Qualifications
- 0:59The Problem
- 1:15The Black Hole
- 1:31Manual Release Management
- 1:47Admit You Have a Problem
- 2:03Focus Needs to Move
- 2:19Standardize
- 2:51Common Pitfalls
- 3:07Keeping it under control
- 3:23Configuration
- 3:40Bulk Blockers
- 3:56Automation Snowball
- 4:11Build Momentum
- 4:28You Will
- 4:44Lessons Learned
- 5:00Keep an Eye on the Big Picture
- 5:16Dont Give Up
- 5:32Thank You
related talks
05mIgnites- Escaping the Black Hole of Release Management
05mRelease management as a catalyst for CI/CD
41mContinuous delivery in 10 easy mistakes
24mThe 7 Habits of Highly Effective Release Managers
18mManaging Change
21mFrom chaos to control: Future-proofing your Android release process
05mReady, Set, DevOps Roadblock
24mFuture-proofing your Android release process