Making the Business Case for DevOps
summary
Calculations and case studies show where DevOps pays off: use annual revenue divided by minutes to value downtime (example $200,000 per minute from Amazon), reduce lead time to change to capture revenue earlier (example Steelcase: 3 days→3 hours yields roughly $2.5M extra), speed builds to save developer time (example Hover: 2.5h→12m), and compare build versus buy (real case saved $250k/year). Tools: CI/CD, Kubernetes, auto scaling, spot/preemptible nodes and the Codefresh calculators to plug your numbers.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:10Building Delivery Loop
- 2:25The Big Issue
- 3:09Michael Lynch
- 4:06Caution
- 4:36Agenda
- 4:53DevOps disciplines
- 5:27Metrics
- 6:16Avoiding downtime
- 7:31How to calculate downtime
- 8:57What uptime means
- 10:14The two teams of DevOps
- 10:39The uptime argument
- 11:28The delivery argument
- 12:11Case study
- 13:57Calculation
- 14:10How much value is delivered
- 15:06Lead time to change
- 15:16Presenting a project
- 15:59Saving engineering time
- 17:46Case study Hover
- 18:00Save an hour
- 18:17Overhead
- 19:07Reduce Infrastructure Overhead
- 21:33Build vs Buy
- 22:28Summary
- 23:29Related Resources
- 23:50Questions
- 28:05GDC
related talks
39mWhat is the ROI of the DevOps implementation?
31mThe Data Behind DevOps: What Does It Take To...
16mDevOps and the Bottom Line
32mContinuous Delivery Delivers Value and So Do You: How to Get Budget, Build Your Case, and Be the Hero
28mThe Future of DevOps in the Enterprise: Trends & Predictions
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
15mPlatform Engineering - a 1 mln $ worth change
32mThe business case for continuous delivery