1. © Disciplined Agile Consortium+
Disciplined DevOps
© Disciplined Agile Consortium

2. © Disciplined Agile Consortium
Agenda
DevOps Gap
Why DevOps?
Views on DevOps
Defining Disciplined DevOps
The DevOps Mindset
Parting Thoughts
© Disciplined Agile Consortium

3. © Disciplined Agile Consortium
Do You Have a DevOps Gap?
Production
Releases
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
© Disciplined Agile Consortium

4. Disciplined Agile Delivery: Introduction to DAD
A Closed DevOps Gap
Taken from the book An Executive’s Guide to Disciplined Agile: Winning the Race to Business Agility
© Disciplined Agile Consortium
© Disciplined Agile Consortium

5. © Disciplined Agile Consortium
Why DevOps?
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
Decreased time to market
Shorter Transition efforts from automation
Smaller “chunks” of work can be implemented faster
Decreased cost to deploy
Automated regression testing
Automated deployment
Streamlined release management
Improved mean time between deployments
Practices such as Continuous Integration and Continuous Delivery enable teams to deploy more often
Decreased cost to deploy enables teams to deploy more often
Improved quality
Adoption of agile testing and quality techniques such as automated regression testing, refactoring, independent testing, and many others
Agile and lean strategies are applied to enterprise architecture, enabling a more holistic view of the organization which in turn promotes greater reuse and reduction/avoidance of technical debt
Agile and lean strategies are applied to data management, improving overall data quality across your organization
Improved market competitiveness
Agile/lean teams enjoy greater stakeholder satisfaction, on average, compared to traditional teams
Streamlined operations and support provide better overall service to end users
Improved quality
Improved decision-making
Real-time insight from Development Intelligence strategies
Real-time insight from Operational Intelligence strategies
Shorter feedback cycles provided by decreased time to market enable teams to easily run experiments to discover what their stakeholders actually want
See:
© Disciplined Agile Consortium

6. 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
This is a very common view amongst agile developers and some tool vendors. Continuous Delivery is clearly an important part of DevOps but it’s really only a streamlined version of the development part of the equation.
Continuous Delivery is one of several delivery lifecycles supported by Disciplined Agile.
© Disciplined Agile Consortium

7. 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
Continuous
Delivery: Agile
Lean
IT Operations
Continuous
Delivery: Lean
Exploratory
Disciplined Agile supports several delivery lifecycles, all of which could be part of your overall DevOps strategy – It’s not just about continuous delivery, although CD is highly desirable.
Minimally, DevOps should be about streamlining development (regardless of lifecycle) and operations.
© Disciplined Agile Consortium

8. © Disciplined Agile Consortium
The BizDevOps Vision
© Disciplined Agile Consortium

9. © Disciplined Agile Consortium
The DevSecOps Vision
© Disciplined Agile Consortium

10. The DataDevOps/DevDataOps Vision
© Disciplined Agile Consortium

11. Explicit Release Management and Supports
© Disciplined Agile Consortium

12. Our View: Disciplined DevOps
Several important points:
1. In larger organizations, release management cannot be handled by just the development teams. If you have dozens, or even hundreds, of solution delivery teams working in parallel their release efforts will need to be coordinated somehow. See
2. It’s not just about operations, but operations and support (help desk).
3. Data is the lifeblood of your organization. Operational data management should be streamlined too. Releasing database changes should also be streamlined (i.e. if it takes six weeks for your data professionals to add a column into a database, you’re not really able to release changes into production very smoothly are you?).
4. Security (DevSecOps) is built right in too.
We need to streamline the overall flow between all of these activities.
© Disciplined Agile Consortium

13. Disciplined DevOps: A Definition
Disciplined DevOps is the streamlining of IT solution development and IT operations activities, along with supporting enterprise-IT activities such as Security and Data Management, to provide more effective outcomes to an organization
© Disciplined Agile Consortium

14. © Disciplined Agile Consortium
The DevOps Mindset
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
© Disciplined Agile Consortium

15. © Disciplined Agile Consortium
Parting Thoughts
You don’t just do DevOps
You must also have the DevOps mindset
DevOps improves IT’s ability to support the rest of the organization
The rest of the business needs to evolve too
You have to build DevOps for yourself
You cannot buy it
DevOps permeates IT
You don’t have a “DevOps Group”, nor “DevOps Engineers”
After describing these critical strategies that support Disciplined DevOps, we’d like to conclude with what we feel to be critical success factors:
Build a collaborative and respectful culture across your entire IT organization. Our experience is that people, and the way that they work together, are the primary determinants of success when it comes to adopting a Disciplined DevOps strategy. Unfortunately, it is considerably more difficult to bring about cultural change in an organization than it is to adopt a handful of new practices.
Focus on people, but don’t forget process and tooling.  DevOps is primarily a mindset, but as you’ve seen in this article there is a large number of potential practices/strategies (yes, that process stuff) that you need to consider adopting.  In turn these practices/strategies are supported by tooling, either existing tooling that you have in place (albeit now used in a different manner) or new tooling that you will need to adopt.
Choice is good.  This article has made it clear that there are many options available to you, each of which has its advantages and disadvantages.  No single approach is perfect, and no single approach works in all situations.  You not only need to have choices, it’s incredibly good to have choices.
© Disciplined Agile Consortium

16. Important Resource DisciplinedAgileDelivery.com/disciplineddevops/
© Disciplined Agile Consortium

17. © Disciplined Agile Consortium
The Disciplined Agile Consortium (DAC) supports and evolves the Disciplined Agile process decision framework. The DAC site, DisciplinedAgileConsortium.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, DisciplinedAgileDelivery.com, provides a wealth of articles and blog postings about Disciplined Agile topics. The Disciplined Agile discussion forum, LinkedIn.com/groups/ , is a meeting place for Disciplined Agile practitioners to share their experiences and to get questions answered.
© Disciplined Agile Consortium