Inclusion – Required for DevOps Continuous Delivery Pipeline

As a noun the official definition of the word inclusion is defined as the state of being included or being made a part of something. When a book covers many different ideas and subjects, it is an example of the inclusion of many ideas. When multiple people are all invited to be part of a group, this is an example of the inclusion of many different people. There are many certification classes available for DevOps, Agile and ITSM. All of them will speak of Inclusion.

When considering inclusion in a DevOps Continuous Delivery Pipeline, service providers frequently miss the inclusion of some very necessary elements. In order to ensure real value, and cost-effective solutions fast, it is back to basics. Consider the inclusion of the following:

  • Requirements: In the past, there has been more of a focus on the Utility (Functional Requirements) for a product or service than there was on the Warranty (Non-Functional) Requirements. Full blow requirements up front before the development ensures a stable antifragile environment and customer outcomes that deliver true value. Consider inclusion for requirements including Security, Compliance, Availability, Capacity and Continuity first. Most find the code, the integrated testing, and the results to be better than anticipated. Want to really be proactive and not always firefighting? Let’s do it right the first time with the inclusion of all requirements.
  • Value Stream Stakeholders: This is a big one. It is not just Dev and Ops that need to integrate but rather all stakeholders in the Value Stream. And yes, this includes the Customer, the Business Partner, CISO and practitioners. Shatter the silos. There is no such thing as “We are too big” or “We are too small” or “You just don’t understand, we have a certain culture here”. There is one “Value Stream” and inclusion of all parties from idea to the realization of value is required. 

…educate & inspire

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

The Difference between Change and Release Management

How Does ITIL Help in the Management of the SDLC?

Search This Blog