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:

Best Practices and Methodologies: These are the answers for how to. It is not just one best practice, methodology, or standard that will get you there. “There” is where you are trying to go. Consider methods such as DevOps, ITSM, Agile, Lean, and standards as tools in a toolbox. ITIL 4 for 2019 will reinforce that they all have a role to play in the integrated Continuous Delivery Pipeline. Without the inclusion of multiple methodologies, it could be like leaving a key ingredient out of the recipe and expecting a delicious result.

People, Process, and Technology: We have all heard this one before. There is not a DevOps Continuous Delivery pipeline without the inclusion of all three. It is People, Process, and Technology but what we do not hear is that it is in that order of importance. It’s the People, the People, the People, and if you think you’ve got it all right reconsider the inclusion of the People. A certified “Agile Process Owner” knows when it comes to process, it is just enough process, just enough governance but to say you don’t require process and governance is an extreme risk. And lastly, the tools are not the silver bullet. Automation is a key element to success but without the inclusion and the importance placed on people and process, the tools and technology may not render the results you have hoped and strived for. Inclusion and balance with a little common sense are always best.

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 upfront 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 be integrated 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”, “We are too small”, or “You just don’t understand, we have a certain culture here”. There is one “Value Stream” and the inclusion of all parties from idea to the realization of value is required.

…educate & inspire

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search