Change management (Keep it Simple, Stupid!)
summary
Creates a lightweight change process centered on a JIRA Kanban board with a new CMB issue type that requires a detailed change plan, test plan and detailed rollback plan while leaving other fields optional. Automated deployments (CI/CD, Chef and versioned cookbooks) are exempt. Rolls out to ops first, then engineering. Measures a roughly 40% drop in self‑inflicted outages over a year, accepts cross‑team dependencies and repetitive tasks as remaining challenges, and emphasizes keeping the process simple and adaptable.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:13Why is change management important?
- 3:31Regulatory compliance
- 4:10Documentation of changes
- 5:49Fewer mistakes
- 6:37Speed and agility
- 7:55Pitfalls to avoid
- 9:20How did we do it at SendGrid?
- 11:07CMB tickets
- 15:33How is it working?
- 16:17Challenges for us
- 18:30Every organization is different
- 23:12General advice
related talks
35m"Change Management: A Scientific Classification"
05mRelease management as a catalyst for CI/CD
41mContinuous delivery in 10 easy mistakes
54mBridging the Gap CICD Mind the Gap
07mAutomated Change Management
34mYou only have to change one thing to do the DevOps
51mBetter software, faster: principles of Continuous Delivery and DevOps
35mThree Steps to Change: Lessons from Battling Bureaucracy