Better Software is Better than Worse Software - Michael Coté (Johannesburg 2019)
Download as PPTX, PDF0 likes346 views
This document discusses how adopting better software development practices focused on productivity, efficiency, and product-centricity can help organizations. It advocates for using modern tools and platforms to allow developer autonomy through practices like DevOps. It also emphasizes choosing the right platform to provide consistency across tools, processes, and products while allowing product teams autonomy. Finally, it provides examples of how companies have benefited from these approaches, such as significantly reducing release times, improving availability, and increasing the time developers spend coding.
Better Software is Better than Worse Software - Michael Coté (Johannesburg 2019)
- 1. Better Software is Better than Worse Software SpringOne Tour, 2019 @cote cote.io/bettersoftware 1
- 3. 3
- 4. Robot dogs not required AUTO & TRANSPORTATION INDUSTRIAL & BUSINESS SVCS. HEALTHCARE & INSURANCE FINANCIAL SERVICES TECHNOLOGY & MEDIA CONSUMER & COMMUNICATIONS
- 5. Methodology Tools Platform Cloud native software Your teams Culture vSphere Openstack AWS Google Cloud Azure AppTX PCFS €£$ Becoming product-centric by increasing dev productivity & ops efficiency
- 6. Source: "Leap of Agile Faith,” Mojgan Lefebvre, SVP & Chief Information Officer, Global Specialty, Liberty Mutual Insurance, June, 2017. A new business in 6 months, doubling avg. sales rate 7
- 7. 8
- 8. 9Source: “CEOs and Software,” Rymer & Hammond, Forrester, Jan 2019.
- 9. DevOps creates developer autonomy 10 OPERATIONS Releas e Test Burndown Chart Release backlog Product backlog BUSINESS DEVELOPMENT Build Release One Day Weekly Build Daily standup meeting backlog weeks Retro 🤯🤯👨🤯💼 🤯 😎😡
- 10. 11
- 11. DevOps has pushed developers too far down the stack 12 Burndown Chart Release backlog Product backlog BUSINESS DEVELOPMENT One Day Weekly Build Daily standup meeting backlog weeks 🤯👨🤯💼 Releas e 🤯 😎 apiVersion: extensions/v1beta1 kind: ReplicaSet metadata: name: mysql labels: app: mysql spec: replicas: 1 selector: matchLabels: app: mysql template: metadata: labels: app: mysql spec: containers: apiVersion: v1 kind: Service metadata: name: mysql spec: ports: - port: 3306 protocol: TCP selector: app: mysql 🤯 🤯🤯😡
- 12. Mobile payments Mortgage application Mortgage approval Bill pay Transfers 🤯 🤯 Private or public IaaS 👩🤯💼👔👨🤯💼 Culture, process, methodology, governance, compensation, etc. Leadership, EAs, etc. Platform Engineers Product teams Corporate strategy, revenue goals, mission, etc. 💼🤯 🏭🏢 🤯 🤯 ☁️ “The Business”
- 13. Choose, govern, and garden the right platform 14 Source: CF Summit Europe 2018, Vincent Oostindië, Rabobank.
- 14. Embedded OS (Windows & Linux) NSX-T CPI (15 methods) v1 v2 v3 ... CVEs Product Updates Java | .NET | NodeJS Pivotal Application Service (PAS) Application Code & Frameworks Buildpacks | Spring Boot | Spring Cloud | Steeltoe Elastic | COTS | Spark Pivotal Container Service (PKS) >cf push >kubectl run YOU build the containerWE build the container Pivotal Network “3Rs” Github Concours e Concours e Pivotal Services Marketplace Pivotal and Partner Products Continuous delivery Public Cloud Services Customer Managed Services Repair — CVEs Repave Rotate — Credhub A consistent platform 15 Pivotal Function Service vSphere OpenStack AWS Google Cloud Azure & Azure Stack
- 15. A consistent product process 16 Sources: "Sky is the Limit for Cloud Foundry at AirFrance-KLM," Nathan Wattimena & Fabien Lebrere, AirFrance-KLM, Oct. 2018.; “Why Change? Small batch thinking,” Coté, Sep. 2018; "Transformation Digitale de la Direction Enterprise France," Philippe Benaben, Gan Zifroni, Nicolas Gilot, Orange France, July 2018.
- 16. From 37% availability to $440m in back taxes ● User-centric, small batch ● Only 37% of calls answered, shrinking budgets ● From 2 year to 9 week releases ● 2m+ users paid $440m in taxes Sources: “‘Your IRS Wait Time is 3 Hours’ - Is Lean Possible in Government?”, Emily Price, Pivotal, April 2017; “Agile Transformation is Product Management,” podcast, Oct 2017; “Minimum Viable Taxes: Lessons learned building an MVP inside the IRS,” slides, Andrea Schneider & Lauren Gilchrist, 2015. See another write-up. Before After
- 17. From coding 20% of the time coding to coding 90% of the time An agile methodology, proven over 25+ years: ● Balanced teams w/all roles needed, dedicated to the product ● Paired programming, & beyond ● Test-driven Development ● Short iterations ● Continuous Integration & Continuous Delivery 18 Source: “Don’t Forget People and Process in Your Digital Transformation,” Allstate case study, March, 2017. Sources: VW.
- 18. Don’t build infrastructure, build applications 250+ apps supported by 3 ops staff, autonomous DevOps/product teams Idea to production In 2 days; 3 months to market vs yrs; 80% of dev time coding Small teams deploying to production in minutes, not days. Sources: CF Summit Europe 2018, Vincent Oostindië, Rabobank; Crafting your cloud-native strategy, Coté, 2017; Mojgan Lefebvre, Liberty Mutual, June, 2017; Interview with Orange’s Xavier Perret, 2017; "A Unifying Foundation for the Customer Journey at Mercedes-Benz," BuiltToAdapt, Apr 2018; Allianz interview, Sep 2016. Modernized app, rolled out 20 countries in 5 months. 40% policy strike rate, vs. 20% industry average. 19 40%+ productivity/cost, rebooted member facing app.
- 20. 21