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

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 than 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

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 th