Ignites- Escaping the Black Hole of Release Management
summary
Manual release work consumes 65% of the team's time, spanning .NET, Java, front-end, PHP and Ruby across 10 different web CMS and 8 different databases. The team standardizes the delivery process, treats configuration as code in source control, and uses an automation snowball—automate one task per week, reclaim time to automate the next. Automation uncovers new bottlenecks (QA became the choke point until automated) and requires cultural change and cross‑team ownership.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:30Qualifications
- 0:45Release Management
- 1:00Release Management is a Black Hole
- 1:15Manual Release Management is Fun
- 1:30Admit You Have a Problem
- 1:45Deliver Not What You Deliver
- 2:00Standardize
- 2:15Team Sport
- 2:30Control Configuration Culture
- 2:45QA Demos
- 3:00Configuration
- 3:15Cultural blockers
- 3:30Automation snowball
- 4:00Automation finds new bottlenecks
- 4:15Culture vs tools
- 4:30Take a step back
- 4:45Release Manual
related talks
06mIgnite: Escaping the Black Hole of Release Management
24mThe 7 Habits of Highly Effective Release Managers
05mRelease management as a catalyst for CI/CD
21mFrom chaos to control: Future-proofing your Android release process
53mTransforming testing methodologies: From manual to robust strategies
41mContinuous delivery in 10 easy mistakes
24mFuture-proofing your Android release process
41mShift Left, Shift Right and Improve the Centre