Minimum Viable IT Service Management (MVITSM)

The aim of Minimum Viable IT Service Management (MVITSM) is to put in place “just enough” process to meet your organizations, needs, goals and circumstances.

Minimum Viable Product
To understand this concept let’s take a look at some of the origins. The term Minimum Viable Product (MVP) originated in software development. If we research the definition we find that in product development, the MVP is a product which has just enough features to gather validated learning about the product and its continued development. Gathering insights from an MVP is often less expensive than using a product with more features which increase costs and risk in the case where the product fails, for example, due to incorrect assumptions.

Minimum Viable Process
In a recent workshop Donna Knapp from ITSM Academy indicated that the Minimum Viable Process is really a matter of looking at what are the minimum critical activities that need to be performed in a process. Complex bureaucratic processes tend to become rigid and rarely get scaled back. To ensure outcomes we really need to start with the most basic form of a process and if the process is already in place then look to scale back to only those minimum critical activities.

Minimum Critical Activities
The following are some characteristics that could help identify what your critical activities should be.

Critical Activities will:

Represent activities that must be performed to provide evidence of compliance

(Legal and regulatory controls / standards)

Define “what to do” not “how to do it”
Are not based on a single framework
Provide a starting place to assess current practices

Red – not performing
Yellow – Performing / Needs improvement
Green – Performing Successfully

It helps to bring transparency to work in progress, cycle time and completed work. Exposure of waste is the first step to eliminate it and to produce quality service at the speed and cost that is relevant to today’s standards. New ways of speaking and acting will lead to new behaviors. As we start moving into a more nibble system for service management we understand that we need to bring ”Agile” and “Lean” values to our process design or redesign activities. As the process and the behavior shifts your culture will change. Why? Bigger, Better, More …. Faster than ever before at the least amount of cost!

Learn More about DevOps and Agile Service Management.

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