Recommandé
Contenu connexe
Similaire à My Dad Won’t Buy Me a DevOps
Similaire à My Dad Won’t Buy Me a DevOps (20)
Plus de TechWell
Plus de TechWell (20)
Dernier
Dernier (20)
My Dad Won’t Buy Me a DevOps
- 4. 10/24/17 2 DevOps is About TransformaCon Three DevOps truths: • It’s about People, Process and Tools • You can’t solve your problems with just tools • To sell DevOps to your company, you need to express value DevOps is About Transforming Your Applica?on Delivery Pipeline 4 • Agile / CI / CD changes are occurring across organizaCons • Unfortunately, these changes occur: • Within individual silos • When each team focuses on what they need • Everyone is solving their problems in their own silo • OperaCons struggling to unify into a consistent paWern Silos, Silos Everywhere Web OFFSHORE NEW MOBILE APP Windows
- 5. 10/24/17 3 5 In order to implement a soluCon, you have to understand how much your applicaCon delivery is really cosCng you Cost of ApplicaCon Delivery 6 None of these individual cost centers can accurately calculate the cost to get a code change from developer into ProducCon Most people point to specific cost metrics: • Cost of DEV staff • Cost of OperaCons • Cost of Project • Cost of Outsourcing ApplicaCon Delivery Cost
- 6. 10/24/17 4 7 How can you expect to draw out the cost of implemenCng ConCnuous Delivery (CD) in a IT Spending chart?? • Hardware • So`ware • Staff • But those are just parts of the picture…. Where is DevOps In Here? TechCrunch 2011 IT Spend 8 CalculaCng Cost of ApplicaCon Delivery Think about ALL releases over enCre DEV to PROD pipeline
- 7. 10/24/17 5 9 Consider: • What defines a release? • Is it a Saturday night outage, with all apps included? Or is it a per-app event? • Think about everyone who has a role in geeng your applicaCon running in PROD. • DEV, QA, InfoSec, OPS, DBAs, etc. “How many applica-ons do you have and how many ac-ve releases are associated with an app at any given -me?” Prep Work Note: For this cost exercise, we’ll use XebiaLabs tools to express the “how” 10 What is the cost of your staff involved in the release process? For simplicity, we'll cost: • IT people (ex/ Developers, Opera-ons, QA) • non-IT people (ex/ BAs, PMs, Business Testers) Staff in Your Release Process Cost of IT deployment staff $125.00 Cost of Business/Test staff $75.00
- 9. 10/24/17 7 13 We’ll simplify and use two types of releases: • "Major" (ex/ 24hr releases) • "Minor" (ex/ 5hr release) Your company may differen-ate in different ways, so we'll generalize into these two buckets Let’s Talk About PROD Number of MAJOR releases in PROD 2 Number of MINOR releases in PROD 10 HOURS - MAJOR PROD (total man hours) 18 HOURS - MINOR PROD (total man hours) 10 Error rate to deploy (PROD) 30% Hours to fix deployment errors in PROD (noCfy, analyze, fix code, redeploy) 10 Number of PROD outages 2 Cost of unexpected PROD outage $10,000 14 What are some metrics for your applica?on delivery from Development to your pre-PROD environment? Metrics Around Your Delivery Number of deployments to DEV per year 100 Number of deployments to /your/path/to/ prod environments per year 132 EsCmated HOURS to deploy to one of these environments: /your/path/to/prod 3 Error rate to deploy (/your/path/to/prod) 35% Hours to fix deployment errors in any PRE- PROD environment (noCfy, analyze, fix code, redeploy) 3
- 10. 10/24/17 8 15 Current Cost of ApplicaCon Delivery Current Cost for Deployments (DEV) $3,125.00 Current Cost for Deployments (/your/path/to/prod) (includes Error rate to deploy value for considering failed/re-deployments) $721,710.00 Current Cost for Deployments (PROD) (includes "Error rate to deploy (PROD)" value for considering failed/re- deployments) $81,636.00 Current Cost for Deployments (DEV->PROD) + 2 unexpected outages $826,471.00 16 What are your planned improvements in your release and deployment processes once you've introduced automa?on? • Consistent applicaCon deployment through all environments • No need for manual deployment instrucCons • Environment configuraCons included in the deployment • All tasks completed consistently during the release process Add in Some AutomaCon AnCcipated reducCon deployment effort (Cme) 50% AnCcipated reducCon in manual configuraCon (resource efforts) 85% AnCcipated reducCon in errors 75%
- 11. 10/24/17 9 17 Your Numbers Next Year Number of deployments to DEV per year 200 Number of deployments to /your/path/to/prod environments per year 50 EsCmated HOURS to deploy to one of these environments: /your/path/to/prod 1 Error rate to deploy (/your/path/to/prod) 8.8% Hours to fix deployment errors in /your/path/to/prod (noCfy, analyze, fix code, redeploy) 1 Number of MAJOR releases in ProducCon 10 Number of MINOR releases in ProducCon 25 HOURS - MAJOR PROD 9 HOURS - MINOR PROD 5 Error rate to deploy (PROD) 8% Hours to fix deployment errors in PROD (noCfy, analyze, fix code, redeploy) 5 Number of PROD outages 0 18 Looking BeWer Cost of Deployments with Automa?on Cost for Deployments (DEV) $750.00 Cost for Deployments (/your/path/to/prod) (Fewer people, less -me and fewer errors) $43,500.00 Cost for Deployments (PROD) (Fewer people, less -me and fewer errors) $59,138.13 Cost for Deployments (DEV->PROD) + 0 unexpected outages $103,388.13
- 12. 10/24/17 10 19 Now That’s Cost ReducCon! Per Applica?on Cost Savings YEARLY SAVINGS in Deployments to DEV $2,375.00 YEARLY SAVINGS in Deployments (/your/path/to/prod) $678,210.00 YEARLY SAVINGS in Deployments (PROD) $22,497.88 TOTAL YEARLY SAVINGS in Deployments (DEV->PROD) + 0 unexpected outages $703,082.88 20 Great – you’ve idenCfied it. What next? Take a look at your app stacks, as well as the path that your applicaCons take from DEV through PROD • What are you going to measure? • How are you going to calculate? More important: how can you use these cost computaCons to help you with your DevOps transformaCon iniCaCve? What Next?
- 13. 10/24/17 11 21 Notes from the War Desk 22 Most customers look to invest in DevOps to: • Release faster & do more with the same staff • Keep employees happy • Build more stuff & reserve your people for highest priority work • Have fewer meeCngs • Make your tools work together • Audit reports • Reduce failures Typical Customer Goals
- 15. 10/24/17 13 ExecuCves Echo a Similar SenCment “We’re making changes, but they don’t seem to be working as we hoped. What is the problem?” So….how do you know if there are problems with your transforma?on ini?a?ve? 25 26 “Too Much DEV” Warning signs: • DEV using tools for delivery of applicaCon that aren’t used in PROD • Automated in DEV, manual in PRE-PROD • DEV isn’t providing what other teams need • “Check the Jenkins log to see what’s in the release” • DEV provides packaged code, with instrucCons • “Pick up the Zip file in this folder…” How to resolve: • Defined paths to PROD for DEV teams to choose from DEV | ops
- 16. 10/24/17 14 27 “Too Much Ops” warning signs: • OPS implemenCng tools that DEV won’t use. • OPS has their own scripCng to deploy • “For this team we do ‘x’, for this team we do ‘y’” • Manual-intensive process for meeCng all OperaConal requirements. How to resolve: • MeeCng: Dev Manager, Ops Manager, CIO dev| OPS Fear of Change Warning Signs CreaCng “soluCons” that will not help fully solve your enCre release issues: • Adding more manual processes • Adding more people
- 17. 10/24/17 15 Warning Signs • Forcing developers to ”remember” the process • Lots of failed deployments, re-deployments, rollbacks Developers understand this Allowing MulCple Delivery PaWerns This is a mystery for your Developers Developers want to deliver faster here Warning Signs • Making decisions to solve delivery problems per app (per project, per environment, etc.) • Using soluCons that aren’t applicable for more than 80% of your app stack Ignoring “the Other” ApplicaCons
- 18. 10/24/17 16 AcCon Plan Create a DevOps TransformaCon with a soluCon that: • Addresses the needs of the people, process and tools • Is consistent for all teams • Is repeatable across all environments DevOps Credo “Be^er to have them inside the tent pissing out than outside pissing in” -- Lyndon B. Johnson 32
- 19. 10/24/17 17 Bring Everyone to the Table 33 How does XebiaLabs help customers solve this problem? • Schedule a 2-3 hour mandatory meeCng • Everyone involved with delivery of applicaCon from DEV to PROD • For each team, review: • What they need • What is blocking You now have your backlog, to solve your applica?on delivery problem DevOps Advisory Board 34 Do you have a DAB team? I see a lot of customers with “Architecture Boards” for reviewing so`ware only You need to formalize a DEV-to-PROD team, focusing on: • People • Process • Tools Example: Developer wants to implement new provisioning tool