Adop%ng DevOps Prac%ces

Transcription

1

2 Adop%ng DevOps Prac%ces Adop%ng Devops prac%ces can be bo#om up or top down or some combina%on of both. However unless there is some buy in from management and alignment with the strategic goals of the business, the development and opera%ons team will con%nue to work in a disjointed fashion. This session describes a number of strategies and approaches to implemen7ng DevOps prac%ces aligned to your business goals.

3 Introduc%on Why the need? What is DevOps? Adop%on Strategies Principles & Prac%ces Where to begin Summary

4 Why is DevOps Important Now? Enterprises have young, nimble start- up compe%tors Agile soiware development is increasing More organiza%ons are migra%ng to the cloud Consumers have app mentali%es and expecta%ons There is more data available to the business Time to market must increase Is DevOps realistic for Enterprise IT? Yes. While enterprise IT faces legacy challenges, DevOps practices are universal and adaptable to different environments.

5

6 Walls of Confusion

7 Blamestorming

8 Dev- Ops Impedance Mismatch SoIware Development and Release processes have too much built- in wastage Handovers Silos Sign- offs Dev and Ops have conflic%ng priori%es Dev wants Change Ops want Stability

9 Agile Delivery

10 What is DevOps? DevOps is a cultural and professional movement that stresses communication, collaboration and integration between software developers and IT operations professionals. Responds to accelerated demand for quality soiware products and services Acknowledges the interdependence of IT func%ons Recognizes the need for cultural improvements Supports and leverages agile, lean and IT service management (ITSM) prac%ces Encourages the use of automa%on

11 DevOps Goals BeZer IT alignment and business responsiveness Faster, smaller, more frequent releases Improved Time to market Quality of code, products and services Produc%vity Customer sa%sfac%on Employee sa%sfac%on Less waste and fewer defects Lower long- term costs

12 Adop%on strategies Top Down Senior management direc%on Organisa%onal set up and change Align all aspects and a planned path Experiment - Learn - retry BoZom up Pilot project Cross func%onal team coopera%on Create the new way Bank the improvements capture learnings Repeat and communicate success as well as failures

13 DevOps cannot stand alone Agile Dev Ops ITSM Lean

14 Values CAMS Culture Automa%on Measurement Sharing

15 DevOps Principles The 3 ways The first way - Flow of work (lei to right) Understanding and improving flow The second way Amplifying feedback loops (Right to lei) The third way - Con%nuous experimenta%on and learning (Kata) Ref The Phoenix project (Gene Kim et al)

16 Con%nuous Integra%on Delivery Deployment Prac%ces First way Value stream mapping Kanban

17 Prac%ces Second way Examples of feedback loops Peer review of produc%on changes Dashboards Produc%on logs Post mortems Incident / problem /change mgt data sharing

18 Prac%ces third way Allocate %me for improvement Create culture that fosters Con%nual experimenta%on Taking risks and learning from failure

19 Right Priori%es 1. People 2. Process 3. Technology Culture Improve communica%ons DevOps Promote collabora%on

20 Where to begin Figure out the why Management buy in has to be around the Why DevOps is not the Why in itself Simplifica%on of complex processes Automa%on of repeatable tasks / processes Eight Steps to transforming your organisa%on John P CoZer Tackle the cultural shii Pilot approach Selec%on Criteria aligned to business goals Follow on consolidate Anchor results If you cant change the culture - create a new one J

21 Summary Lock in the Why Agree an incremental approach Address the Culture and Values Experiment and learn from experience - always looking to improve all areas

22 Thank You

23 What is the DevOps Founda%on course? A sixteen (16) hour cer%fica%on course that provides founda%onal knowledge of DevOps including DevOps vocabulary DevOps values and prac%ces The rela%onship between DevOps, Lean, Agile and ITSM The principles of DevOps automa%on Guidance for nurturing a DevOps culture The course and cer-fica-on examina-on are accredited by the DevOps Ins-tute. *

24 DevOps Dimensions The best tools to address each of the 4 dimensions of DevOps Practices. Plan & Track Collaborative planning and tracking tools are a must if you want disparate groups to work together across the organization. 1 2 Dev & QA Dev and QA teams need to work together so a standard set of tools that encourage a single source of truth is a must. Monitor & Optimize You need to be able to react quickly and fix production issues so that the business can have trust in the DevOps process and you constantly learn and improve. 4 3 Release & Deploy Frequent Release and Deploy requires automation of both infrastructure provisioning and software configuration and deployment.

25 Plan & Track Transparency, Visibility, Collaboration JIRA and JIRA Agile Confluence & HipChat Plan & Track All types of work planned and tracked using a suite of enterprise collaboration tools Wallboards JIRA Portfolio

26 Dev & QA Tools to allow Dev and QA teams to work together JIRA IDE Integration Bamboo JIRA & JIRA Agile Zephyr for JIRA Productivity Improve the speed and transparency of all development and QA actiivty Stash & Bitbucket

27 Release & Deploy Frequent Releases Requires Automation Release Release & Configuration Management Deploy Software Defined Infrastructure Automated Deployment. Automated Provisioning

28 Monitor & Alert Monitor application performance from the point of view of the end-user 2pm 3pm 4pm 5pm 6pm 7pm 8pm