In this video Stefan Kempter presents a pragmatic approach to defining the service management processes for your organization: The YaSM model describes exemplary processes for managing service and provides a complete set of process and document templates.
ITIL® 4, the latest edition of the popular service management framework, has now been released. ITIL® 4 describes principles and practices and includes a huge amount of guidance, yet it also says we should use common sense and keep things "simple and practical". That sounds like a bit of a conundrum, especially as many organizations find it difficult to translate the ideas behind ITIL® into specific processes.
But we have found a good solution, based on several years of feedback on the ITIL® guidelines: The YaSM model describes exemplary processes and provides a complete set of process and document templates, so you don't have to start from nothing as you define the service management processes of your organization.
I'll tell you more about the YaSM processes shortly, but first let's recap, very briefly, what kind of guidance we find in ITIL® 4.
As the authors of ITIL® 4 say, the framework ITIL® 4 consists of two key components: The four dimensions model, and the ITIL® service value system (or 'SVS').
The first component, the four dimensions model, describes four dimensions that should be considered to ensure a holistic approach to service management:
The second component of ITIL®, the service value system, includes several elements:
I'm afraid we cannot go into the details of all of these elements in this short video. The point I'd like to get across is that ITIL® contains various types of guidance and content, such as
Now, how can you bring this guidance to life?
Ultimately, you'll need to translate the ITIL® guidance into processes that work for your organization. This is much easier if you can use pre-defined processes and don't have to start from nothing!
That's why we have created the YaSM process model. YaSM follows the ITIL® guidance and includes a complete set of process and document templates that you can adapt as required.
But what's the best approach to designing ITIL®-aligned processes?
ITIL® 4 says organizations are free to define tailor-made processes, and I think if organizations are to adopt flexible operating models and keep things simple and practical, they need to avoid complexity and adopt a somewhat lean and streamlined set of processes that is not too difficult to understand.
And the processes should preferably be in line with an industry standard. That's why the benchmark for the YaSM processes is ISO 20000, the international standard for service management. YaSM is thus 100% compatible with ISO 20000 (ISO/IEC 20000:2018) and it's a very good choice for organizations that want to get certified against this standard.
And here's what the YaSM process model looks like:
These processes will certainly look familiar to you if you know any edition of ITIL®, or other service management frameworks.
And now, after these somewhat theoretical deliberations, let's look at some practical examples.
The YaSM model describes a set of processes, and for every process, we provide detailed templates. With these templates, it's not too difficult to understand how service management is supposed to work, and to define tailor-made processes for your organization.
The first example is incident management, one of the service management practices. ITIL® 4 describes the time-tested approach to incident management and discusses the key aspects to be considered when dealing with service incidents. In the YaSM model, we have translated this guidance into the incident resolution process, where we find the typical high-level activities such as
For each of these sub-processes, the YaSM model contains an additional level of detail in the form of a swim lane diagram. This one, for example, describes the activities to be performed in 1st level support:
This is classical incident management as we know it from ITIL®, ISO 20000 and virtually all other service management frameworks.
My second example is continual improvement. In ITIL® 4, we find continual improvement
The guidance includes
Again, we have translated the advice provided in ITIL® into a set of specific processes, such as the service improvement process. If we zoom in a bit, you can see that improving a service in YaSM is quite straightforward: It involves
In this process, the service improvement plan is an essential document or database where we keep track of all service improvements. Again, we have an additional level of detail for each sub-process in the form of a swim lane diagram, such as this one, describing the recommended steps for performing service reviews:
I hope you will agree that this is not too difficult to understand and is the perfect base for introducing an improvement process in your organization. With these two examples I wanted to show you how we translated the ITIL® guidance into process templates that you can use as a starting point for defining the processes of your organization.
Now, this session wouldn't be complete without a brief discussion of the "progressive practices" such as Agile, Lean und DevOps, that are hot topics at many organizations. ITIL® does not say you have to do DevOps or Agile. But many organizations will find the DevOps and Agile approach useful, especially if they offer services that heavily depend on software.
Agile and DevOps are not processes, but values, principles and techniques. They usually go hand in hand with the use of modern technologies such as
Agile and DevOps are not suitable for everyone, which is why we keep the YaSM processes generic and don't use specific Agile and DevOps language. But it's not hard to see how these principles can be applied to the YaSM processes.
For example, YaSM includes processes for
In these, we describe generic activities:
Organizations that follow the Agile and DevOps approach would
It's also conceivable that a lot of the action takes place in service improvement. This process can be perfect for enhancing services in small iterations, in response to constantly changing customer needs. These iterations would be managed in "backlogs", a key artefact in Agile methods like Scrum.
And that's it for today. I hope I was able to demonstrate that YaSM, with its streamlined and clear-cut processes, and ITIL® are a good fit. Of course, we cannot cover everything here in this short video, but you can read a detailed comparison between YaSM and ITIL® 4 in the YaSM Service Management Wiki.
If you would like to learn more about YaSM and the YaSM Process Map, please visit yasm.com. There you can also find our complete contact information if you want to get in touch with us.
Thanks for watching, and take care!