The 7 Habits of Highly Effective Release Managers
summary
AGS builds slots and poker titles with ~600 staff and 130 ongoing games, and treats release work as coordinating complex deployments across hardware, cloud, networks and code. Concrete practices: separate change vs release; a release policy with naming and frequency rules (monthly/quarterly or agile cadence); early visible change records for scheduling; heavy use of automation and templates because automation reduces human error and saves overtime/service-credit costs; quality gates as enablers; rollout options (big‑bang, pilots, phased); and post‑release retrospectives to capture lessons and update the CMDB.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:31About the speaker
- 5:41What is release management
- 7:30Change vs release management
- 9:45Clear release policy
- 12:36Planning releases
- 14:02Standardize and automate
- 15:11Quality gates for acceptance
- 16:58Deploy to business needs
- 18:26Reviews for improvement
- 20:55Summary
- 21:17Q&A
related talks
27mHow implement release management efficiently in development cycle with modern solutions?
05mIgnites- Escaping the Black Hole of Release Management
06mIgnite: Escaping the Black Hole of Release Management
47mRelease Management, As It Is
05mRelease management as a catalyst for CI/CD
28mHow to ship apps better, faster, stronger
18mManaging Change
17mA Brief History of Release Engineering