Why Disciplined DevOps?

In this posting we briefly explore why both you and your organization should consider adopting a Disciplined DevOps mindset.  For yourself as an individual there are several interesting benefits.  First, you become more productive as an IT professional, increasing your chance at promotion and making you more attractive in the marketplace.  Second, you are in a position where you can focus on interesting, value-added work, which should lead to greater job satisfaction for you.  Third, much of the dysfunctional politics exhibited in traditional IT  organizations is effectively squeezed out as you move to a Disciplined DevOps mindset, making your work environment a more enjoyable place to be.

There are many reasons why your organization should consider adopting a Disciplined DevOps mindset.  The following table summarizes the potential benefits and how they are achieved:

Benefit Source
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
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

As always, we welcome any feedback that you may have.

2 thoughts on “Why Disciplined DevOps?

  1. Valentin Tudor Mocanu

    DevOps it about “integration” between development and enterprise operations concerns. That mean will need an Agile development process that could map the scaling concerns related to enterprise and could deal with this complexity. That is somehow a part of DAD definition.

  2. Scott Ambler Post author

    Yes, that’s a good way of looking at it. Disciplined DevOps is about the integration of enterprise development and enterprise operations. This is why we need to look beyond software development and include activities such as data management, enterprise architecture, release management and others when we think about streamlining development and operations.


Leave a Reply

Your email address will not be published. Required fields are marked *