What is the ROI of the DevOps implementation?
summary
Argues that ROI is concrete: replacing per-customer on‑prem installs that take 8 hours support per customer per year with cloud infrastructure‑as‑code, CI/CD and automated provisioning drops new instance setup to 5 minutes provisioning and scales sales from ~15 to 100 customers/year, cutting support load and improving code quality. Emphasizes need for management buy‑in, an evangelist to drive change, willingness to rehire/refire, and pragmatic choices between refactor, rewrite or buy.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:59DevOps philosophy
- 4:50DevOps as communication
- 8:50Customer focus in DevOps
- 11:37Company readiness for DevOps
- 14:29Leadership in DevOps
- 17:41Management support
- 19:48Technical debt in DevOps
- 22:16Traditional vs DevOps costs
- 25:29DevOps value added
- 27:40Measuring DevOps ROI
- 30:48DevOps impact on business
- 31:52Summary
related talks
29mMaking the Business Case for DevOps
16mDevOps and the Bottom Line
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
24mHow DevOps changed the way we operate software
33mUnleashing the Gorillacorn - DevOps in Very Large Enterprises
43mAbout to Start Your Nth DevOps Transformation?
47mWhere the Security Rubber Meets the DevOps Road
01h 01mEnterprise Adoption of DevOps