That DevOps and Agile bring benefit is self-evident; these slides explore how the key benefits can be quantified such that a business case can be built.
15. Assumptions
Splitting into sprints doesn’t lower
productivity
The ideas (scope) could be delivered
independently & has value when
delivered independently
IT has the maturity and engineering
practices to delivery in sprints
Powered by
DevOps
Powered by
DevOps
26. Assumptions
Splitting into sprints doesn’t lower
productivity
The ideas (scope) could be delivered
independently & has value when
delivered independently
Regular change could be absorbed by
the business
39. 39
2008
N = Number of Deploys 1
P = Probability of site degradation 50%
S = Average severity of degradation 0.7
T = Time to detect / resolve (hours) 100
Expected downtime 35
N * P * S * T
2013
250
10%
0.05
5
6.25
Source: http://www.slideshare.net/beamrider9/continuous-
deployment-at-etsy-a-tale-of-two-approaches
40. 40
Before DevOps
Min time to market 20 weeks 4 days
Test coverage 30% 80%
Test cycle duration 4 weeks 6 hours
Outages 30 (2013) None (2014)
DR Test Duration 4 hours 12 minutes
Source: https://www.youtube.com/watch?v=9jqY_bvI5vk
41. 41
N = No. Deploys
P = Probability of site degradation
C = Average cost of degradation
T = Time to detect / resolve
Annual cost of downtime
N * P * C * T
Cost of bad-change
44. 44
“high-performing organizations are still
deploying code 30 times more
frequently, with 50 percent fewer
failures than their lower-performing
counterparts.”
https://puppetlabs.com/2014-devops-report