ITSM for DevOps - Development “Divas”

What is your biggest challenge when trying to increase the flow of work through your DevOps or Continuous Delivery Pipeline? In a recent conversation an IT Director laughingly said that his greatest challenge was that they can not get the development “Divas” to recognize that change approval and compliance requirements are necessary and that it takes time.

I chuckled as I thought to myself what those development “Divas” were thinking. Maybe their thoughts were that those paranoid risk adverse Change and Compliance process people do not understand that we need to get this work to the finish line and we need to go fast. Sound familiar?

This is not an uncommon issue. The us-vs-them environment, if not corrected, will continue to disrupt IT service delivery and therefore, business performance.

We must recognize that DevOps and Continuous Delivery (CD) do not stand alone. It is not just the tools and automation and, although it is more about culture, it is not just culture either. There are many good practices that can be leveraged from Agile, Lean, DevOps and yes, even ITSM. What worked five years ago does not work for today’s enterprise.

High performing IT providers must be able to integrate the ITSM processes including event management, problem and incident management and configuration management. It does not stop there. Some of the biggest show stoppers come from the lack of understanding that “Change”, Compliance, Security and other requirements are not going away. The old way of having a Change Advisory Board that meets once a week is gone. We strive for NO WAIT GATES in a CD pipeline. If the old way does not work, then what does? What is the new “modern” way to expedite and accelerate change while ensuring security and compliance? What does work?

DevOps doesn’t eliminate the need for controls and data. Regulatory controls and audits still exist, and risks and impacts must still be managed. “ITSM for DevOps” introduces ways to achieve both speed and control while driving value across the IT value stream.

To ensure time to value, a service provider today must radically rethink and understand how these process activities and requirements are performed. More important is how can they be performed and help to expedite the flow of work?

For more resources and information consider ITSM Academy's Course: ITSM for DevOps

ITSM Academy Resource Center - webinars, templates, etc.

Comments

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