Disciplined Dev Ops 2016 Disciplined Agile Consortium 1
- Slides: 15
+ Disciplined Dev. Ops © 2016 Disciplined Agile Consortium 1
Agenda • • Dev. Ops Gap Why Dev. Ops? Views on Dev. Ops – Continuous Delivery – Development + Operations – Disciplined Dev. Ops Defining Disciplined Dev. Ops The Dev. Ops Mindset Dev. Ops Critical Success Factors Dev. Ops Changes the IT/Business Relationship Parting Thoughts © Disciplined Agile Consortium 2
Exercise: What is Dev. Ops? For five minutes, discuss: • What does Dev. Ops mean to you? • What new behaviours do you need to adopt? © 2016 Disciplined Agile Consortium 3
Do You Have a Dev. Ops Gap? Production Releases Development Operations Change Requests • • Production releases are seen as risky Collaboration between development and operations is strained Development doesn’t appreciate the realities of operations Operations doesn’t understand new development strategies © 2016 Disciplined Agile Consortium 4
Why Dev. Ops? • • • Decreased time to market (reduced cycle time) Decreased cost to deploy Improved mean time between deployments (deploy more often) Improved quality Improved market competitiveness Improved decision making © 2016 Disciplined Agile Consortium 5
One View: Continuous Delivery • Practices: – Automated regression testing – Continuous integration (CI) – Continuous deployment (CD) – Canary tests – Split (A/B) tests • Operations-friendly features: – Feature toggles – Feature-level access control – Built-in monitoring – Self testing – Self recovery © 2016 Disciplined Agile Consortium 6
A Better View: Agile Delivery + Operations • Multi-modal approach to software development • Operations activities are also streamlined and “leaned out” • Some teams will adopt a “you build it, you run it” philosophy, but a common operational infrastructure still required © 2016 Disciplined Agile Consortium 7
Our View: Disciplined Dev. Ops © 2016 Disciplined Agile Consortium 8
Disciplined Dev. Ops: A Definition Disciplined Dev. Ops is the streamlining of IT solution development and IT operations activities, and supporting enterprise-IT activities, to provide more effective outcomes to an organization. © 2016 Disciplined Agile Consortium 9
The Dev. Ops Mindset 1. 2. 3. 4. 5. 6. 7. 8. Streamline the end-to-end flow Reduce the feedback cycle Flexible people Multidisciplinary “generalizing specialists” Standardized infrastructure Automation and tools Standardized development guidelines You build it, you run it © 2016 Disciplined Agile Consortium 10
Dev. Ops Changes Your Relationship with the Business • • Your business and IT processes must be integrated – Plans must be high-level with the details coming just in time (JIT) – Emphasize delivery of value via a consumable solution rather than transitory work products of questionable value – Schedules and estimates must be given in ranges – Traditional business approaches will eliminate most benefits of agile/Dev. Ops The new relationship with the business: – They must be actively involved with development all the way through the lifecycle – The greater visibility and control that they now have implies the need for greater accountability on their part – They often don’t understand the implications of what they ask for, you need to educate them – You need to demonstrate that disciplined agile delivery is not cowboy programming. It is very likely far more disciplined than their current processes © 2016 Disciplined Agile Consortium 11
Dev. Ops Critical Success Factors 1. Build a collaborative and respectful culture across your entire IT organization 2. Focus on people, but don’t forget process and tooling 3. Choice is good © 2016 Disciplined Agile Consortium 12
Parting Thoughts • You don’t just do Dev. Ops – You must also have the Dev. Ops mindset • Dev. Ops improves IT’s ability to support the rest of the organization – The rest of the business needs to evolve too • You have to build Dev. Ops for yourself – You cannot buy it • Dev. Ops permeates IT – You don’t have a “Dev. Ops Group”, nor “Dev. Ops Engineers” © 2016 Disciplined Agile Consortium 13
Important Resource Disciplined. Agile. Delivery. com/disciplineddevops/ © 2016 Disciplined Agile Consortium 14
The Disciplined Agile Consortium (DAC) supports and evolves the Disciplined Agile process decision framework. The DAC site, Disciplined. Agile. Consortium. org, provides information on curriculum and learning resources for Disciplined Agile practitioners. It is also the home of the Disciplined Agile certification program. The Disciplined Agile blog, Disciplined. Agile. Delivery. com, provides a wealth of articles and blog postings about Disciplined Agile topics. The Disciplined Agile discussion forum, Linked. In. com/groups/4685263, is a meeting place for Disciplined Agile practitioners to share their experiences and to get questions answered. © 2016 Disciplined Agile Consortium 15
- Dac certified disciplined agilist (cda)
- Disciplined agile consortium
- Disciplined agile delivery lifecycle
- Dev-sec
- Capato dev ops
- Disciplined agile delivery roles
- Intellectually disciplined
- Disciplined superlative
- The disciplined mind example
- What is discipline
- Riss ops
- Ops operating system
- Fin ops
- Contoh perwabku sabhara
- Gcaa car ops
- Dr. derek bub