YaSM and ITIL: Difference between revisions
No edit summary |
No edit summary |
||
Line 25: | Line 25: | ||
<p> </p> | <p> </p> | ||
<p><b>Comparison:</b> YaSM and ITIL<sup><small>®</small></sup> (ITIL 4)</p> | <p><b>Comparison:</b> YaSM and ITIL<sup><small>®</small></sup> (ITIL 4)</p> | ||
<p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></ | <p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html> | ||
<p> </p> | <p> </p> | ||
[[What is YaSM|YaSM]]<sup><small>®</small></sup> [[#YaSM|[1]]] and [[ITIL]]<sup><small>®</small></sup> [[#ITIL|[2]]] have common roots and share the same principles, so users familiar with ITIL will find the YaSM model and the [[Service Management Processes|YaSM processes]] easy to read. | |||
This page provides a detailed account of <span id="md-webpage-educationalUse" itemprop="educationalUse">how the YaSM service management model relates to the latest edition of ITIL 4</span>. If your organization uses ITIL V3, there is another page with a [[YaSM and ITIL V3|comparison between YaSM and ITIL V3 (ITIL 2011)]]. | This page provides a detailed account of <span id="md-webpage-educationalUse" itemprop="educationalUse">how the YaSM service management model relates to the [[ITIL#ITIL_4|latest edition of ITIL 4]]</span>. If your organization uses [[ITIL#ITIL_V3|ITIL V3]], there is another page with a [[YaSM and ITIL V3|comparison between YaSM and ITIL V3 (ITIL 2011)]]. | ||
<p> </p> | <p> </p> | ||
Line 55: | Line 55: | ||
<p><a class="external text" href="https://wiki.en.it-processmaps.com/index.php/Main_Page" title="ITIL® Wiki | Main page">ITIL®</a> has a history of some 30 years. It has gone through several revisions and has grown into a large and sophisticated framework that many find difficult to understand.</html> | <p><a class="external text" href="https://wiki.en.it-processmaps.com/index.php/Main_Page" title="ITIL® Wiki | Main page">ITIL®</a> has a history of some 30 years. It has gone through several revisions and has grown into a large and sophisticated framework that many find difficult to understand.</html> | ||
* Where ITIL V2 defined only 10 processes for service support and service delivery, | * Where [https://wiki.en.it-processmaps.com/index.php/ITIL_Processes#ITIL_Processes_according_to_ITIL_Version_2_.28ITIL_V2.29 ITIL V2 defined only 10 processes] for service support and service delivery, | ||
* [[YaSM and ITIL V3|ITIL V3 specified 26 processes]] organized around the service lifecycle, | * [[YaSM and ITIL V3|ITIL V3 specified 26 processes]] organized around the service lifecycle, | ||
* and ITIL 4 describes a [[ITIL_4_vs_ITIL_V3#ITIL_4_service_value_system_.28SVS.29|service value system]] including [[#ITIL_4_practices_and_YaSM_processes|34 service management practices]]. | * and ITIL 4 describes a [[ITIL_4_vs_ITIL_V3#ITIL_4_service_value_system_.28SVS.29|service value system]] including [[#ITIL_4_practices_and_YaSM_processes|34 service management practices]]. | ||
Line 64: | Line 64: | ||
==The YaSM model and ITIL== | ==The YaSM model and ITIL== | ||
The YaSM model describes a set of streamlined [[Service Management Processes|service management processes]], with a clear-cut structure. 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 | The YaSM model describes a set of streamlined [[Service Management Processes|service management processes]], with a clear-cut structure. | ||
<html>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 <a class="external text"href="https://yasm.com/en/blog/yasm-itil-lite" title="Related article: Is YaSM 'ITIL lite' or 'lean ITIL'?">approaches for 'light' or 'lean' ITIL</a> would advocate. Rather, YaSM is less complex and easier to read because it introduces a simple and intuitive process structure.</html> | |||
The YaSM model follows the principles behind ITIL - and also the guidance provided in other service management frameworks and approaches, such as [[YaSM and COBIT|COBIT]]<sup><small>®</small></sup>, [[SIAM and YaSM|SIAM]]<sup><small>®</small></sup> and [[VeriSM and YaSM|VeriSM]]™. What is more, the YaSM processes are 100% compatible with the requirements of [[YaSM and ISO 20000|ISO 20000]], dem internationalen Standard für Service-Management. | The YaSM model follows the principles behind ITIL - and also the guidance provided in other service management frameworks and approaches, such as [[YaSM and COBIT|COBIT]]<sup><small>®</small></sup>, [[SIAM and YaSM|SIAM]]<sup><small>®</small></sup> and [[VeriSM and YaSM|VeriSM]]™. What is more, the YaSM processes are 100% compatible with the requirements of [[YaSM and ISO 20000|ISO 20000]], dem internationalen Standard für Service-Management. | ||
Line 100: | Line 102: | ||
Not every ITIL 4 practice can be translated into a process (some describe management techniques and principles rather than activities). | 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. | But a [[ITIL 4 vs ITIL V3|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. | ||
It is therefore not wrong to argue that ITIL 4 includes guidance for processes, and providing templates for ITIL 4 processes is quite feasible. | It is therefore not wrong to argue that [[#ITIL_4_practices_and_YaSM_processes|ITIL 4 includes guidance for processes]], and providing templates for ITIL 4 processes is quite feasible. | ||
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. | 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. | ||
Line 120: | Line 122: | ||
Typical examples for service management processes are service portfolio management, incident management, change management, etc. | Typical examples for service management processes are service portfolio management, incident management, change management, etc. | ||
<html>Processes are often documented in a process model, for which the <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map | <html>Processes are often documented in a process model, for which the <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map">YaSM Process Map</a> provides an example and a complete set of<a href="https://yasm.com/en/products/yasm-process-map" title="YaSM service management templates"> service management process templates</a>.</html> | ||
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. | 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. | ||
Line 146: | Line 148: | ||
|- | |- | ||
|-style="background:#eeeeee; vertical-align:top; text-align:left; " | |-style="background:#eeeeee; vertical-align:top; text-align:left; " | ||
|colspan="2"|ITIL 4 | |colspan="2"|ITIL 4 four dimensions model | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|The four dimensions of service management | |The four dimensions of service management | ||
Line 182: | Line 184: | ||
* The YaSM model applies this approach in a number of processes, such as the service improvement process. | * The YaSM model applies this approach in a number of processes, such as the service improvement process. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|ITIL 4 practices | |ITIL 4 practices | ||
| | | | ||
* ITIL 4 presents 34 practices as "sets of organizational resources designed for performing work or accomplishing an objective". | * ITIL 4 presents 34 practices as "sets of organizational resources designed for performing work or accomplishing an objective". | ||
Line 199: | Line 201: | ||
* [[#ITIL_4_technical_management_practices_and_related_YaSM_processes|ITIL 4 technical management practices and related YaSM processes]] | * [[#ITIL_4_technical_management_practices_and_related_YaSM_processes|ITIL 4 technical management practices and related YaSM processes]] | ||
The YaSM model is thus a good starting point for defining ITIL 4 processes. | The YaSM model is thus a good [[Service Management Processes|starting point for defining ITIL 4 processes]]. | ||
<p> </p> | <p> </p> |
Revision as of 17:37, 14 April 2019
Comparison: YaSM and ITIL® (ITIL 4)
Part of: YaSM vs. other service management frameworks and standards
YaSM® [1] and ITIL® [2] have common roots and share the same principles, so users familiar with ITIL will find the YaSM model and the YaSM processes easy to read.
This page provides a detailed account of how the YaSM service management model relates to the latest edition of ITIL 4. If your organization uses ITIL V3, there is another page with a comparison between YaSM and ITIL V3 (ITIL 2011).
ITIL® has a history of some 30 years. It has gone through several revisions and has grown into a large and sophisticated framework that many find difficult to understand.
- Where ITIL V2 defined only 10 processes for service support and service delivery,
- ITIL V3 specified 26 processes organized around the service lifecycle,
- and ITIL 4 describes a service value system including 34 service management practices.
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:
The YaSM model and ITIL
The YaSM model describes a set of streamlined service management processes, with a clear-cut structure.
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 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, dem internationalen Standard für 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.
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. 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.
It is therefore not wrong to argue that ITIL 4 includes guidance for processes, and providing templates for ITIL 4 processes is quite feasible.
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.
Processes and value streams in ITIL 4
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.
Processes are often documented in a process model, for which the YaSM Process Map provides an example and a complete set of service management process templates.
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.
ITIL 4 Components[3] | Related YaSM processes and content |
---|---|
ITIL 4 key concepts | |
Key concepts of service management |
|
ITIL 4 four dimensions model | |
The four dimensions of service management |
|
The ITIL 4 service value system (SVS) | |
Service value system overview |
|
ITIL guiding principles |
|
Governance |
|
ITIL service value chain |
|
Continual improvement |
|
ITIL 4 practices |
|
ITIL 4 practices and YaSM processes
ITIL 4 describes 34 management practices as "organizational resources designed for performing work or accomplishing an objective". Some of these practices are general management practices or methods adopted from technology management, but most of them correspond to the processes known from the previous edition of ITIL V3 and other service management frameworks.
As YaSM was designed to be aligned with ITIL, there is generally good alignment between the ITIL 4 practices and the YaSM service management processes, as described in the following tables:
- ITIL 4 general management practices and related YaSM processes
- ITIL 4 service management practices and related YaSM processes
- ITIL 4 technical management practices and related YaSM processes
The YaSM model is thus a good starting point for defining ITIL 4 processes.
Remarks:
- The management practices in this table are based on ITIL 4 Foundation, published in February 2019.
- If your organization uses ITIL V3, there is another page with a comparison between YaSM and ITIL V3 (ITIL 2011).
ITIL 4 management practices[4] | Related YaSM processes | Comparison: YaSM service management and ITIL 4 |
---|---|---|
Architecture management |
|
|
Continual improvement |
| |
Information security management |
| |
Knowledge management |
|
|
Measurement and reporting |
| |
Organizational change management |
|
|
Portfolio management |
| |
Project management |
| |
Relationship management |
| |
Risk management |
| |
Service financial management |
| |
Strategy management |
| |
Supplier management |
| |
Workforce and talent management |
|
ITIL 4 management practices[4] | Related YaSM processes | Comparison: YaSM service management and ITIL 4 |
---|---|---|
Availability management |
|
|
Business analysis |
|
|
Capacity and performance management |
|
|
Change control |
| |
Incident management |
| |
IT asset management |
| |
Monitoring and event management |
| |
Problem management |
| |
Release management |
| |
Service catalogue management |
| |
Service configuration management |
| |
Service continuity management |
| |
Service design |
| |
Service desk |
| |
Service level management |
|
|
Service request management |
| |
Service validation and testing |
|
ITIL 4 management practices[4] | Related YaSM processes | Comparison: YaSM service management and ITIL 4 |
---|---|---|
Deployment management |
|
|
Infrastructure and platform management |
|
|
Software development and management |
|
|
References
- [AXELOS, 2019]. -- AXELOS: ITIL® Foundation, ITIL 4 Edition. - The Stationery Office; Norwich, UK, February 2019.
External links
- [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.
Notes
[1] YaSM stands for "Yet another Service Management Model". YaSM® is a registered trademark of IT Process Maps GbR.
[2] 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
[3] The ITIL guidance referenced in this table is based on ITIL 4 Foundation, published in February 2019.
[4] The management practices in this table are based on ITIL 4 Foundation, published in February 2019.
Is based on: The YaSM Process Map - Document: "YaSM and ITIL®"
By: Stefan Kempter and Andrea Kempter , IT Process Maps.
The YaSM model and ITIL › ITIL 4 processes and ITIL 4 process templates? › ITIL 4 components and YaSM › ITIL 4 practices and YaSM processes