Download as PDF, PPTX
Uploaded byILM Professional Services
More Than A Buzzword: How DevOps Can Impact Your Business
The document outlines the impact of DevOps on business, highlighting its core values such as culture, automation, measurement, and sharing. It emphasizes the importance of collaboration between development and operations teams, leading to faster deployment, reliability, and improved business agility. Various statistics and case studies are presented to illustrate the performance differences and ROI achieved through DevOps practices.
More Related Content
Similar to More Than A Buzzword: How DevOps Can Impact Your Business
More Than A Buzzword: How DevOps Can Impact Your Business
- 1.
- 2.
- 3.
- 4. What the word DevOps is • “software DEVelopment” + “information technology OPerationS” • Devs: software •Ops: infrastructure • But wait… there’s more! (Figure 4)
- 5.
- 6.
- 7. With DevOps… …teams are able to quickly and independently develop, test, and deploy code and (business) value quickly, safely, securely, and reliably to customers. This allows organizations to maximize developer productivity, enable organization learning, create high employee satisfaction, and winin the marketplace. (The DevOps Handbook)
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. DevOps Myths Myths • DevOps engineer • “Jack of all trades, master of none” •More interruptions Truths • DevOps evangelist & team • Still specialists • Reclaim time (Figure 6)
- 15.
- 16.
- 17.
- 18.
- 19.
- 20. DevOps Culture: Increased Collaboration • “Report It” “Fix It” (collaboration & shared responsibility) • Ops help Devs design environment from beginning •Devs help Ops support Prod • Eliminate “Us vs. Them” mentality (Figure 12)
- 21.
- 22. Automation: Pets vs Cattle (Owning vs Renting) • Indispensable • Manually uniquely crafted •Personal attachment • Named (Traditional) (DevOps) • Expendable • Automated & consistently built • No nurturing • Numbered (Figure 13)
- 23.
- 24.
- 25.
- 26. The Bottom Line Business Agility – (according to HRZone.com) refers to distinct qualities that allow organisations to respond rapidly to changes in the internal and external environment without losing momentum or vision. Adaptability, flexibility and balance are three qualities essential to long‐termbusiness agility. (Most businesses rely heavily if not solely on IT to accomplish this)
- 27.
- 28. Key Performance Indicators (KPIs) • Deployment Frequency • Speed of Deployment •Deployment Success Rate • Time to Recovery • Culture – Not Measured
- 29.
- 30.
- 31. Failure Rate • Changes that cause an outage: 23% vs 7.5% • Get more done –and with less errors
- 32.
- 33. The DevOps Difference • Ops: less pager calls at 3am • Devs: write more code •More fun – and deliver more value (Figure 2)
- 34.
- 35.
- 36.
- 37. “Show Me the Money!” • Silverpop/IBM: Automating Deployments yields Savings • Etsy: DevOps Increased Revenue YearInitiative Sales Increase Visitors Increase 2009 Automated deployments $90M(by 103% to $177M) 96% (to 320M) 2010 Standardized infrastructure & configurations $130M(by 73% to $307M) 66% (to 534M) 2011 Eliminating non‐standard technologies $219M(by 71% to $526M) 67% (to 895M) Before DevOps • 12‐18 people for 8+ hours • 400 manual steps • Inconsistent error‐prone process With DevOps • 5 minute deployments • Zero downtime • $1M annual savings (IBM, 2015) (IT Revolution, 2012)
- 38.
- 39.
- 40. Getting Started With DevOps • Organizational definition of DevOps • ROI Analysis •Value: more specific than time & $ • Cost: training, staff augmentation, tools • Time (“it depends”): • Automate deployments: e.g. 3 weeks (Pearson VUE, 2014) • DevOps/Containers: ~1 year • Each iteration gets easier: 1, 2, 10, 100, 1K • Get top‐down buy‐in (Figure 17)
- 41. Walking the path 1. Start small – DevOps is not all‐or‐nothing 2.Have a plan – create feedback loops 3. Try many tools – don’t (necessarily) buy the hammer 4. Explore different combinations of tools – look for patterns and learn from others’ successes and failures 5. Examine your organizational workflows ‐ find bottlenecks and constraints and identify types of work and value streams 6. Evaluate expertise that exists within the organization, and tools and processes already in place Remember – work in cycles and use your data to drive your choices.
- 42. Automation: The 3 C's (CI/CD) • Need automated testing • Which CD is best? •“It depends” ‐ do what’s best for your organization • Both minimize time spent not delivering value (Figure 14)
- 43.
- 44. Better Together • Fantastic Four • DevOps •The Cloud • Microservices (modularity) • Containers (virtualization) • 1 OS to rule them all – unlike VMs • Infrastructure as code – e.g. Dockerfile • Eliminate WOMM (Works on My Machine) • No wrong recipe • Any number of them • No pre‐requisites • Implement each incrementally (Figure 16)
- 45.
- 46. Summary 1. DevOps CAN definitely bring business value 2. DevOps IS • A Collaborative culture •Cross‐disciplinary engineering practices • Efficient & integrated tools • Continuous learning from feedback loops 3. Get started with DevOps! (Figure 18)
- 47. www.ilmservice.com Sean Epping Principal Consultant • Thank you! • Q&A(Figure 19) sean.epping@ilmservice.com seanepping @seanepping
- 48. Resources • Feedback Loop: (Amazon, 2015): DevOps: A Look at Our Tools and Processes • (Puppet Labs, 2016): 2016 State of DevOps Report •And other great DevOps resources from Puppet Labs: • Six DevOps myths, busted • Get Started with DevOps: A Guide for IT Managers • How to Build a High‐Performing IT Team: Five essential steps to mapping your DevOps journey • DevOps Business Value: Case Studies • (IBM, 2015) Silverpop/IBM: Automating Deployments yields Savings • (IT Revolution, 2012) Etsy: DevOps Increased Revenue • CAMS acronym description: (John Willis, Chef 2010), What Devops Means to Me • CAMS image: DEVOPS: HOW A CULTURE OF EMPATHY CREATES MASSIVE PRODUCTIVITY, Telehouse • Wall of Confusion: (John Willis, IT Revolution 2012): DevOps Culture, IT Revolution
- 49. Figures/Images • Figure 1: goal bridge.jpg • Figure 2: I‐Love‐My‐Job.jpg •Figure 3 (Princess Bride ‐ what DevOps means): Microsoft Virtual Academy: DevOps • Figure 4 (Venn diagram DevOps): DevOps Journey Part II ‐ Version Control • Figure 5 (sold them tools… ‐ Dr. Evil's allies): Agile Memes, Part 1 • Figure 6: myth‐busted.jpg • Figure 7: logos: Agile (loops.png) & DevOps (cog wheels gears.png) • Figure 8 (roles included in Agile & DevOps): What Is Continuous Delivery: The Last Mile • Figure 9 (worked in Dev…): DevOps: Tear Down that Wall! • Figure 10: Avengers ‐ Together.jpg • Figure 11 (wall between Devs & Ops): VMware DevOps Blogs: What Is DevOps, and Why Should I Care? — The IT Leadership Perspective • Figure 12: removing walls & silos • Figure 13: Pets (puss‐in‐boots.png) vs Cattle (Pets vs. Cattle: The Elastic Cloud Story ‐ slide 8) • Figure 14 (CI/CD): Continuous Integration, Delivery and Deployment Explained • Figure 15 (versioning code & infrastructure): DevSecOps (slide 11) • Figure 16 (better together ‐ fantastic four): cookies & milk and donut & coffee • Figure 17: Logic – Spok.gif • Figure 18: questions ‐ raised_hands.jpeg
- 50.
- 51.