Skip to main content

DevOps and ITSM… Are They Compatible?



Many are surprised to learn that ITSM practices ARE compatible with their DevOps pipelines and even more important that they are a critical element in order to ensure the effectiveness, efficiency and the value that is expected. Those that are struggling with silos us vs. them blame games, or roadblocks and impediments for change and test, are shocked to learn how accelerated, modernized ITSM practices can enable their outcomes! 

Topics and discussion from a recent ITSM for DevOps class were exciting as practitioners, managers, and leaders discovered together how It is possible to streamline and even automate their ITSM processes and practices so that people don’t even realize that they are executing ITSM processes.

We don’t need to change “what” needs to be accomplished. Policy, Governance, and Compliance are a reality. In order to achieve true value and business outcomes service providers must change the way that they think. A change in thinking provokes a change in how we do work. How we implement ITSM practices must change. The reality is that high-performing organizations aren’t achieving success without ITSM processes. Those that are successful understand ITSM4DO.

ITSM for DevOps introduces ways to achieve both speed and control while driving value across the IT value stream.

Learning Objectives: At the end of this course, the learner will understand:
  • How companies are struggling with the technological and human challenges of DevOps transformations
  • The role of service management
  • How IT service management is viewed as a constraint
  • How DevOps introduces new ways of thinking and working
  • How to accelerate and automate ITSM processes in support of DevOps
  • ITSM process integration and automation
  • How to leverage Lean and Agile methods to reduce waste and positively impact both the cost and quality of processes and services

Visit the DevOps Campus at ITSM Academy so you too can…. Educate & Inspire! For all things Agile, Lean, DevOps and ITSM!

Comments

Popular posts from this blog

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

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th