Against this backdrop, many organizations that wish to adopt ITIL best practices are wondering where to begin. Ultimately, service providers will need to define tailor-made processes that work for the organization, and YaSM provides an alternative to ITIL that makes this task easier:
This does not mean that YaSM is simplistic: Every ITIL process or practice serves a purpose, and YaSM does not merely omit some processes, as various approaches for 'light' or 'lean' ITIL would advocate. Rather, YaSM is less complex and easier to read because it introduces a simple and intuitive process structure.
The YaSM process model follows the principles behind ITIL - and also the guidance provided in other service management frameworks and approaches, such as COBIT®, SIAM® and VeriSM™. What is more, the YaSM processes are 100% compatible with the requirements of ISO 20000, the international standard for service management.
Note: YaSM® is an independent service management model and is not officially endorsed by the owners of ITIL®.
ITIL 4 processes and ITIL 4 process templates?
Earlier versions of ITIL were organized around service management processes, but ITIL 4 describes a service value system and service management practices that do not specifically relate to processes.
Fig. 2: ITIL 4 and YaSM ITIL 4 processes and process templates based on YaSM service management.
Technically speaking, there are thus no "ITIL 4 processes" - but to apply the ITIL 4 guidance in practice organizations surely need to define suitable processes. (The authors of ITIL 4 state that defined processes "ensure the organization is enabling value creation for all stakeholders efficiently and effectively".)
So the question arises: Can a service management process model like YaSM define ITIL® 4 processes, and is it possible to provide ITIL 4 process templates?
The answer is yes, although translating ITIL 4 into process templates is not as straightforward as it is with ITIL V3 (see fig. 2).
There is no defined set of ITIL 4 processes and to work out ITIL 4-aligned processes, based on the ITIL 4 practices, users must apply their own judgement.
Not every ITIL 4 practice can be translated into a process (some describe management techniques and principles rather than activities). But a comparison between ITIL 4 and ITIL V3 shows that most of the ITIL 4 practices can be traced back to ITIL V3 processes. For example, the ITIL 4 practice of incident management clearly corresponds to the familiar incident management process.
What is more, ITIL 4 is not prescriptive and in favor of "keeping things simple and practical".
This presents an opportunity for a fresh start with a less complex, streamlined and well-defined set of ITIL 4 process templates, as provided in the YaSM model. These templates can be easily adapted to create tailor-made processes, in line with the needs of specific organizations.
In this video Stefan Kempter presents a pragmatic approach to defining the service management processes for your organization:
In the four dimensions model, ITIL 4 relates to "value streams and processes", and organizations are advised to identify their processes and value streams. But there is often confusion around the two concepts because they are somewhat similar: Both describe sequences of activities and both create value. So should organizations focus on processes or value streams?
In practice, most organizations will use processes as well as value streams:
Processes represent the organization's operating model, and properly defined processes are important because they ensure, among others, that
Employees and other stakeholders are aware of their responsibilities and accountabilities
Repeated tasks are carried out consistently and efficiently
Rules and compliance requirements are observed.
Typical examples for service management processes are service portfolio management, incident management, change management, etc.
Value streams are somewhat similar to processes, but their purpose is different: Value streams are mostly representations of the steps required to deliver a service to a customer. They show "end-to-end" views and typically start with a customer need and end with that need being fulfilled. Value streams are often included in service definitions to describe how value is created and how users interact with the service.
An example of a value stream could be the sequence of steps required for the onboarding of new customers to a specific service.
ITIL 4 components and YaSM
The following table provides an overview of the ITIL 4 components versus processes and content from the YaSM service management model.
Comparison: ITIL 4 Components vs. YaSM Service Management
The first part of ITIL describes the key concepts of service management.
The YaSM model is based on these concepts and explains how organizations can bring them to life in their service management processes.
ITIL 4 four dimensions model
The four dimensions of service management
ITIL defines four dimensions that should be considered to ensure a holistic approach to service management: Organizations and people, information and technology, partners and suppliers, as well as value streams and processes. These dimensions are applicable to the service value system in general and to specific services.
The YaSM processes are designed to consider these key aspects of service management as services are designed, operated and continually improved.
The ITIL 4 service value system (SVS)
Service value system overview
The ITIL service value system (SVS) describes "how all the components and activities in the organization work together to enable value creation". It includes five components: Guiding principles, governance, service value chain, practices and continual improvement.
The ITIL SVS is in some ways similar to the holistic systems approach known from other service management frameworks and standards, such as ISO 20000 and VeriSM.
The YaSM model supports organizations that wish to adopt a systems approach for managing their services, providing detailed processes, document templates, policies, etc.
ITIL guiding principles
The ITIL 4 guiding principles are universal recommendations that can guide organizations in many situations, such as "work holistically" and "keep it simple and practical".
The YaSM model helps organizations to apply many of these principles in practice.
The governance component of the ITIL service value system is about directing and controlling the organization.
The YaSM processes include a number of activities that are concerned with governance, such as establishing policies, performing reviews at different organizational levels, defining the service strategy and monitoring performance.
ITIL service value chain
The ITIL service value chain is the central element in the ITIL service value system. It presents the key activities required to create value for customers. The six value chain activities are: Plan, improve, engage, design and transition, obtain / build, deliver and support.
The YaSM model describes 19 service management processes. This configuration is not identical with the ITIL 4 service value chain, but on a more detailed level the activities in the YaSM processes broadly correspond to the value chain activities.
The ITIL model for continual improvement describes a structured approach to identifying and implementing improvements that can be used at all levels of the organization.
The YaSM model applies this approach in a number of processes, such as the service improvement process.
ITIL 4 practices
ITIL 4 presents 34 practices as "sets of organizational resources designed for performing work or accomplishing an objective".
These practices are integrated into the YaSM processes.
ITIL 4 advises that organizations use a continual improvement register (CRI) to manage their improvement ideas. In the YaSM model, improvement ideas are managed through the service and process improvement plans.
The YaSM model does not contain a specific availability management process. Rather, service availability is treated as an aspect of services to be managed through the service lifecycle processes.
Availability requirements are defined during the service design stage, and services are then built with those requirements in mind. The operating process will be responsible for measuring the achieved availability levels, which allows the service improvement process to take action if availability must be enhanced.
This ITIL 4 practice describes techniques for analyzing systems, processes, architectures, etc.
Some of these techniques are applied in the YaSM processes, for instance as service requirements are defined in the service design process.
Capacity and performance management
(Various YaSM processes)
YaSM does not contain a specific capacity management process but treats service capacity and performance as aspects to be managed through the service lifecycle processes.
Capacity and performance requirements are defined during the service design stage, and services are then built with those requirements in mind. The operating process will be responsible for measuring capacity and performance levels, which allows the service improvement process to take action if capacity must be adjusted or performance improved.
The key activities of IT asset management as described in ITIL 4, such as maintaining a list of IT assets, recording changes and providing current information about IT assets, are included in the YaSM process for managing configuration information (SP4).
YaSM does not describe financial asset management in detail.
The service desk practice highlights the key aspects to be considered when offering a single point of contact with customers and users. It does not describe service desk activities.
In the YaSM model, the typical service desk activities are described in the incident and service request resolution process.
Service level management
(Various YaSM processes)
In the YaSM model, several processes are concerned with managing service levels throughout the service lifecycle.
The required service levels - as well as the required service outcomes - are defined in the service design stage, based on the needs of the customers. Monitoring and reporting of service levels is the responsibility of service operation. The service improvement process will review the achieved service levels against the committed levels and initiate corrective action if required.
Once in a while I get asked during our webinars if YaSM is an alternative to ITIL. It almost seems quite a few people would like to avoid having to deal with ITIL - but is it a good idea to ignore it? [...]
YaSM is definitely lighter than ITIL (actually we decided to create YaSM because many of our customers looked for something lighter). But we don't want YaSM to be confused with what is often called "ITIL lite" or "lean ITIL" because we think the existing approaches are often flawed: [...]
AXELOS announced an initiative to promote the usage of ITIL® in non-IT environments: Their aim is provide additional guidance, so that non-IT service providers are better able to benefit from ITIL. [...]
[AXELOS, 2019]. -- AXELOS: ITIL® Foundation, ITIL 4 Edition. - The Stationery Office; Norwich, UK, February 2019.
[IT Process Wiki]. -- S. Kempter & Kempter, A.: "IT Process Wiki". -- The Wiki about the IT Infrastructure Library ITIL® (ITIL 4, ITIL 2011, ITIL V3 & V2), ISO 20000 and IT Service Management (ITSM). - IT Process Maps; Lindau (Bodensee), Germany.
[IT Process Wiki - ITIL Processes]. -- S. Kempter: IT Process Wiki, "ITIL Processes". - IT Process Maps; Lindau (Bodensee), Germany.
 YaSM stands for "Yet another Service Management Model". YaSM® is a registered trademark of IT Process Maps GbR.
 ITIL® is a registered trademark of AXELOS Limited. - IT Infrastructure Library® is a registered trademark of AXELOS Limited. ITIL official site: axelos.com/best-practice-solutions/itil
 The ITIL guidance referenced in this table is based on ITIL 4 Foundation, published in February 2019.
 The management practices in this table are based on ITIL 4 Foundation, published in February 2019.
YaSM® | Service Management (ESM, BSM, ITSM) & ISO 20000
YaSM® is a registered trademark of IT Process Maps GbR. ITIL® and IT Infrastructure Library® are registered trademarks of AXELOS Limited. COBIT® is a registered trademark of ISACA. ISO/IEC 20000® is a registered trademark of ISO. CMMI® and Capability Maturity Model® are registered trademarks of Carnegie Mellon University. USMBOK™ is a registered trademark of Virtual Knowledge Solutions International Incorporated (VKSII). SIAM® is a registered trademark of EXIN. VeriSM™ is a registered trademark of IFDC. -- Microsoft®, Word™, Excel®, SharePoint® and Visio® are registered trademarks of Microsoft Corp. ARIS™ and IDS Scheer are registered trademarks of Software AG.
This page was last edited on 17 February 2020, at 16:55.