Making the business case for DevOps
•
146 j'aime•37,502 vues
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.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Making the business case for DevOps
Similaire à Making the business case for DevOps (20)
Dernier
Dernier (20)
Making the business case for DevOps
- 1. DevOps Making the Business Case Copyright © 2015 Accenture All Rights Reserved.
- 2. Martin Croker Managing Director, Accenture Technology Architecture Responsible for DevOps capability at Accenture. @martincroker martin.croker@accenture.com
- 3. 3
- 4. DevOps has value How do we articulate it?
- 6. 6 Time to Market Business Agility Productivity Running Costs Total Benefit
- 7. Time Money Money now is worth more than the same amount of money later… Benefit
- 8. 8 Idea Value
- 10. Time Release
- 12. 12 Sprints
- 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
- 16. 16 Laggards Market Share % 100 75 50 25 Innovators Majority Time
- 17. 17 Laggards Market Share % 100 75 50 25 Innovators Majority Delay Time
- 18. 18 Laggards Market Share % 100 75 50 25 Innovators Majority Loss of market Share? Time
- 19. 19 Time to Market Business Agility Productivity Running Costs Total Benefit
- 21. 21 Design & Build QA & Test Operate Best Guess
- 22. 22 Design & Build QA & Test Operate Best Guess Feedback Experiments
- 23. 23 Design & Build QA & Test Operate Best Guess 1 YEAR6 MONTHS1 MONTH2 WEEKS1 WEEKS1 DAY1 HOURMINUTES
- 24. 24 “Anyone who has never made a mistake has never tried anything new.” Albert Einstein
- 25. 25 Time to Market Business Agility Productivity Running Costs Total Benefit
- 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
- 28. 28 Copyright © 2015 Accenture All Rights Reserved. Deployment Automation Effort Productivity Risk
- 32. 32 “Quality comes not from inspection, but from improvement of the production process..“ - Dr W. Edward Deming
- 35. Productivity (SLOC / Day) ProjectSize
- 37. 37 Time to Market Business Agility Productivity Running Costs Total Benefit
- 38. 38 “80% of unplanned outages are due to ill- planned changes …” -- Visible Ops Handbook
- 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
- 42. Other potential run-time benefits Anti-fragility Infrastructure costs Operations automation
- 43. 43 Time to Market Business Agility Productivity Running Costs Total Benefit
- 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
- 46. 46 @martincroker