You Can’t Automate Chaos

In a recent DevOps Foundation Certification class one IT executive said “You can not automate Chaos”! Another learner spoke up and said “Yes you can… that is what we are doing”! Although that was meant as a LOL moment, it is true that when it comes to velocity and improving cadence all too often service providers jump the gun and look at automation as the silver bullet. While recognizing that tools, technology and automation are key elements, process and governance must also be considered. Automating before we get management control of these is likely to lead to bigger and faster CHAOS!

Executive buy in and support is rewarded when the business and IT are integrated to the point that IT alignment with the business is a given. Properly designed and well governed process will enable any automation initiative. Remember we are talking about “Just enough process” and “Just enough governance”. If your process is the roadblock then you might have created exactly what you are trying to avoid.

There are many areas that can be automated to support continuous delivery and continuous deployment throughout the service lifecycle so when it comes to vendor and tool selections service providers will benefit by taking a gradient approach. Considerations will include:

An understanding of the integrated value stream including business outcomes and requirements, development, deployment and operational activities.

Metrics and report requirements for all functions are an element of technology and automation that are often missed. Remember that all of these are dynamic so tools and technology must be flexible to meet changing business needs and requirements.

Constraints will need to be identified. These include governance, compliance, financial as well as organization structures and cultural constraints.

Considering integrated suites, application platforms and many other functional tools and technology will be required. We should not be looking at a single vendor or tool but rather the entire tool chain that is required to optimize throughput and automation.

I have found that depending on who you ask there are many interpretations of what DevOps is, what the Agile Values really represent and how ITSM or LEAN initiatives integrate with them. If your organization is considering or is engaged in any ITSM, DevOps or Agile initiative, technology and automation will be required for success. Let’s not automate chaos! It’s time for the industry to get out of the CHAOS business altogether. Ongoing communication, education and training are not just buzz words but will likely be your critical success factors.

For more information: http://www.itsmacademy.com

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