From Agile to DevOps to Continuous Delivery – How to Evolve Your Software Delivery”

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

© Electric Cloud | www.electric-cloud.com Are we there yet? “Are you able to deliver new software to production as fast as the business demands?” Based on a 2015 survey of 90+ IT Managers, Directors, Sr. Directors and VPs taken during an EC webinar featuring Forrester Research and Lockheed Martin No Yes ?

Slide 6

Slide 6 text

© Electric Cloud | www.electric-cloud.com The path to software delivery success • First, you think. • Then, you code. • Then a “bunch of stuff” happens. • Then, your code is live, being used by millions of people!

Slide 7

Slide 7 text

© Electric Cloud | www.electric-cloud.com The trouble with software delivery, today • Supporting Agile development velocity downstream • Slow cycle time • Lack of shared visibility between Dev, QA and Ops • Manually operated and non-integrated tool chains • Multiple poorly utilized redundant build and test systems across locations • Brittle, error-prone, and non-scalable home-built systems • No way to audit processes or predict schedules • Wasted time, money dealing with broken build

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

© Electric Cloud | www.electric-cloud.com What is Continuous Delivery? 10 Continuous Delivery (CD) is a pattern language used in software development to automate and improve the process of software delivery Or…read this book

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

© Electric Cloud | www.electric-cloud.com DevOps & Continuous Delivery: Positive Impact Julie Craig, EMA, DevOps and Continuous Delivery: Ten Factors Shaping the Future of Application Delivery, 2014 We do CD We don’t do CD More than 10% Revenue Growth Less than 10% Revenue Growth

Slide 15

Slide 15 text

© Electric Cloud | www.electric-cloud.com Remember the Agile Manifesto? . . . to satisfy the customer through early and continuous delivery of valuable software. #1 of the Twelve Principles behind the Agile Manifesto

Slide 16

Slide 16 text

© Electric Cloud | www.electric-cloud.com The evolution of software development methodologies Kurt Bittner If Agile was the opening act to a great performance… Continuous Delivery is the headliner. Agile Development “An iterative approach to delivering value frequently, and in small batches.” Continuous Integration “Automated build and unit test after each check-in.” Continuous Delivery “Maintaining software in a release-ready state using CI + on-demand automated deploy, QA or prod environments.”

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

© Electric Cloud | www.electric-cloud.com Continuous Delivery: Challenges VP of Engineering Distributed teams Non-standard processes across different teams Duplicated/distributed environments Inefficient artifacts sharing between overseas teams Large collection of non- orchestrated siloed tools Scheduling of tasks in virtualized resources Quality TTM Low productivity Real-time feedback on code quality Low infrastructure utilization Competitiveness Long testing cycles Inadequate access control for critical processes Manual “spreadsheet- driven” processes Need self-service access to environments Lack of shared visibility into pipelines Insufficient testing / code coverage leads to escaped bugs Finger-pointing Flaky automation servers Slow builds Jobs lost in-flight Complex Toolchains Complex Environments Complex Processes Complex Applications Many islands of automation Failed deployments VM Sprawl Long wait times Track issues from request to release What is running where?

Slide 20

Slide 20 text

Slide 21

Slide 21 text

© Electric Cloud | www.electric-cloud.com Continuous Delivery Principles (another sampling) Create a repeatable, reliable process of releasing / deploying software Need for Speed: cycle time matters. A lot. Build quality in: use processes that encourage quality: TDD, BDD Done means done “It works on my machine” everybody is responsible for the delivery process Continuous improvement: lather, rinse, repeat If it’s worth doing… automate it

Slide 22

Slide 22 text

© Electric Cloud | www.electric-cloud.com Ouch, quit it! Thank you sir, may I have another If it hurts, do it more frequently, and bring the pain forward; solve the root-cause instead of working on the symptoms

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

© Electric Cloud | www.electric-cloud.com CD Fitness: Process Level Characteristics Level 0 No process, ad-hoc software delivery schedule Level 1 Many project plans but lack of well-defined processes for change requests (requirements, designs, escalation) No process for continuous testing Level 2 Some well-defined processes exist (e.g. CI, CT, CR) but execution is not consistent nor integrated end-to-end Agile may be used in small batch sizes, in some projects Level 3 Well defined, end-to-end, pipeline, and automation Code is kept in a single branch More evolved processes is utilized (Kanban e.g.) Level 4 Well defined continuous adjustment and improvement process to meet fast moving business requirements by leveraging data generated by the end-to-end CD monitoring tool

Slide 28

Slide 28 text

© Electric Cloud | www.electric-cloud.com CD Fitness: Technology Level Characteristics Level 0 Homegrown scripts or manual processes Basic open source tools Level 1 Many siloed tools, independently used to solve specific issues Commonly operated by different individuals without common understanding, process or oversight Level 2 Shared infrastructure (testing, preflight, delivery) exists Islands of automation with minimal interaction Level 3 Automation throughout build/test/deploy lifecycle Automated provisioning and configuration of necessary assets Centralized, self-service infrastructures that are elastic End-to-end visibility and traceability Level 4 Executive dashboards allow decision makers to make real-time adjustment based on business needs Business determines which content should be released and when

Slide 29

Slide 29 text

© Electric Cloud | www.electric-cloud.com CD Fitness: Culture Level Characteristics Level 0 Small teams working on skunk works projects, academic in nature Level 1 Very private, communication via email, very reactive Level 2 Collaboration occurs but focus on individual modules, “tossed over the wall” for the next group Level 3 Understand business goal, eager to help, seek out help and feedback, focus on coaching and mentoring Level 4 Collaboration and cooperation are paramount, feedback are reviewed and incorporated

Slide 30

Slide 30 text

Slide 31

Slide 31 text

© Electric Cloud | www.electric-cloud.com Transformative Benefits 10 min FASTER DEVELOP TO DEPLOY 90 days 99% improvement TIME 0 errors LESS ERRORS per cycle 10 errors 90+% improvement ERRORS 15 min FASTER DEPLOYMENTS 90+ min 80+% improvement TIME 6 hours FASTER DEVELOP TO DEPLOY 24 hours 75% improvement TIME minutes FASTER AUDITABILITY who, what, when, how 20 days 90% improvement TIME

Slide 32

Slide 32 text

© Electric Cloud | www.electric-cloud.com Success Story: Family Search Largest genealogical organization in the world Employ ~1000 people Multiple web-based applications 24x7 availability requirement Challenges prior to CD: • Cannot deliver features to customer fast enough • Delivering features customers want? • System downtime impacts customer experience • Reduced developer productivity • Loss of continuity

Slide 33

Slide 33 text

© Electric Cloud | www.electric-cloud.com Success Story: Family Search In the past we released products in one to three months; now we can go from commit to production every 10 minutes. Automation is a key part of making that happen.

Slide 34

Slide 34 text

© Electric Cloud | www.electric-cloud.com Thought Leaders “People not practicing Continuous Delivery often doubt it can work. Once they’ve developed in this type of environment they can’t imagine ever going back.” - Gary Gruver, Agile Leader and Co-author: “Large Scale Agile Development” “I am excited to be a part of this industry-wide effort to elevate the state of the practice, and thank Electric Cloud and their partners for helping accelerate the adoption of DevOps practices.” - Gene Kim, DeOps researcher, co-author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win”

Slide 35

Slide 35 text