YaSM and ITIL: Difference between revisions
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
<meta property="og:image:width" content="400" /> | <meta property="og:image:width" content="400" /> | ||
<meta property="og:image:height" content="348" /> | <meta property="og:image:height" content="348" /> | ||
<meta name="twitter:card" content="summary_large_image"> | |||
<meta name="twitter:site" content="@yasmcom"> | |||
<meta name="twitter:creator" content="@yasmcom"> | |||
<meta name="twitter:title" content="YaSM and ITIL®"> | |||
<meta name="twitter:description" content="ITIL® vs. YaSM®. - a detailed cross-reference between the ITIL and YaSM service management processes."> | |||
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm.jpg"> | |||
<meta name="twitter:image:alt" content="The IT Infrastructure Library ITIL and the YaSM framework: Comparison of the service management frameworks."> | |||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
Line 39: | Line 46: | ||
<p>YaSM, however, is somewhat leaner and less complex. This was important to us because we think both large and small organizations should be able to benefit from service management best practice.</p> | <p>YaSM, however, is somewhat leaner and less complex. This was important to us because we think both large and small organizations should be able to benefit from service management best practice.</p> | ||
< | <ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-arrow-right.png');padding-left: 18px;"> | ||
<li>For a brief summary, watch our animated video about the <a href="https://yasm.com/en/videos/yasm-itil">differences between YaSM and ITIL®</a> (9:28 min.).</li></ul><p></html> | |||
<p> </p> | <p> </p> | ||
Line 45: | Line 53: | ||
==<span id="yasm-itil-differences">YaSM and ITIL®: The main differences</span>== | ==<span id="yasm-itil-differences">YaSM and ITIL®: The main differences</span>== | ||
This does not mean that YaSM is simplistic: Every ITIL process serves a purpose, so YaSM does not merely omit a number of ITIL processes, as a number of approaches for "light" or "lean" ITIL would advocate | This does not mean that YaSM is simplistic: Every ITIL process serves a purpose, so YaSM does not merely omit a number of ITIL processes, as a number of approaches for "light" or "lean" ITIL would advocate. | ||
To understand why this leads to more simplicity, consider the following example: ITIL treats configuration management as part of service transition. But configuration management activities also occur elsewhere in the service lifecycle, and configuration information is needed as an input for virtually every ITIL process. This is why YaSM takes the view that it is more straightforward and intuitive to treat configuration management as a "supporting" process outside the service lifecycle. | Rather, YaSM is less complex because it departs in some areas from ITIL's rigorous service lifecycle structure, and introduces a simpler and more intuitive process structure which distinguishes between [[YaSM_Processes#service-lifecycle-processes|service lifecycle processes]] and [[YaSM_Processes#supporting-service-management-processes|supporting service management processes]]. | ||
To understand why this leads to more simplicity, consider the following example: | |||
ITIL treats configuration management as part of service transition. But configuration management activities also occur elsewhere in the service lifecycle, and configuration information is needed as an input for virtually every ITIL process. This is why YaSM takes the view that it is more straightforward and intuitive to treat [[SP4: Manage configuration information|configuration management]] as a "supporting" process outside the service lifecycle. | |||
What is more, the ITIL processes focus on managing services throughout their lifecycle, but there are no explicit processes for setting up and maintaining the service management processes themselves [[#ISO20000|[2]]]. For example, ITIL describes an incident management process, but is less explicit about how the process comes into existence. YaSM addresses this issue by adding a number of additional supporting processes. | What is more, the ITIL processes focus on managing services throughout their lifecycle, but there are no explicit processes for setting up and maintaining the service management processes themselves [[#ISO20000|[2]]]. For example, ITIL describes an incident management process, but is less explicit about how the process comes into existence. YaSM addresses this issue by adding a number of additional supporting processes. | ||
Line 56: | Line 68: | ||
<p> </p> | <p> </p> | ||
==<span id="video-itil-yasm">Video: ITIL® vs. YaSM</span>== | |||
<html><a href="https://yasm.com/en/videos/yasm-itil" ><img src="https://yasm.com/en/content/videos/yasm-itil/yasm-itil-video.jpg" width="320" height="180" class="thumbimage" alt="Video: YaSM and the IT Infrastructure Library ITIL" title="Watch the video: YaSM and ITIL" style="display: block; float: right; margin-top: 10px; margin-left: 30px; margin-bottom: 10px; margin-right: 10px" /></a> | |||
<p style="margin-top: 10px;">In this video Stefan Kempter gives you a better understanding of the similarities and differences between YaSM and ITIL® by taking you through a couple of examples. | |||
<p>He shows you how we managed to create a streamlined framework that is in line with ITIL® and covers all key aspects of service management best practice.</p> | |||
<ul style="list-style-image: URL('/wiki/en/img/yasm-wiki/icon-arrow-right.png');padding-left: 18px;"> | |||
<li>Watch the video: <a href="https://yasm.com/de/videos/yasm-itil" title="Video: YaSM and ITIL">YaSM and ITIL®</a> (9:28 min.)</li></ul> | |||
<br style="clear:both;"/><br /><p></html> | |||
==<span id="comparison-yasm-itil">ITIL processes and corresponding YaSM processes</span>== | ==<span id="comparison-yasm-itil">ITIL processes and corresponding YaSM processes</span>== | ||
Line 74: | Line 95: | ||
<p> </p> | <p> </p> | ||
<html><i><b>Notes:</b></i><br /> | |||
</p> | |||
<ul><li><i>YaSM is an independent framework and is not officially endorsed by the owners of ITIL.</i> <br /></li> | |||
<li><i>All ITIL processes in the following tables are linked to IT Process Map's ITIL® Wiki - the "<a href="https://wiki.en.it-processmaps.com/index.php/Main_Page">IT Process Wiki</a>" - where you can find the relevant descriptions of the ITIL processes.</i></li> | |||
<li><i>The process structure in this table is based on ITIL 2011 Edition.</i></li></ul> | |||
<p> </ | <p> </html> | ||
==<span id="service-strategy">YaSM vs. ITIL Service Strategy</span>== | ==<span id="service-strategy">YaSM vs. ITIL Service Strategy</span>== | ||
Line 426: | Line 447: | ||
==<span id="itil-functions-yasm">ITIL functions and YaSM</span>== | ==<span id="itil-functions-yasm">ITIL functions and YaSM</span>== | ||
Apart from a set of processes ITIL also describes a number of "functions". For instance, incident management is introduced as a process and facilities management as a function. | <html>Apart from a set of processes ITIL also describes a number of "<a href="https://wiki.en.it-processmaps.com/index.php/ITIL_Functions" title="ITIL functions">functions</a>". For instance, incident management is introduced as a process and facilities management as a function.</html> | ||
By definition, a function is an organizational entity, often characterized by a special area of knowledge or experience. Examples would be the human resources department or a team of experts operating a certain part of the technical infrastructure. | By definition, a function is an organizational entity, often characterized by a special area of knowledge or experience. Examples would be the human resources department or a team of experts operating a certain part of the technical infrastructure. | ||
Line 439: | Line 460: | ||
<p> </p> | <p> </p> | ||
==Related | ==Related articles== | ||
<html><a href="https://yasm.com/en/blog/itil-alternative-yasm"><img src="https://yasm.com/en/content/blog/141029-itil-alternative-yasm/img-180x110.jpg" alt="ITIL framework alternative: The YaSM Framework" style="display: block; float: left; border:1px solid #d9d9d9; margin-right: 10px"/></a> | <html><a href="https://yasm.com/en/blog/itil-alternative-yasm"><img src="https://yasm.com/en/content/blog/141029-itil-alternative-yasm/img-180x110.jpg" alt="ITIL framework alternative: The YaSM Framework" style="display: block; float: left; border:1px solid #d9d9d9; margin-right: 10px"/></a> | ||
Line 476: | Line 497: | ||
==External links== | ==External links== | ||
*<span id="ref-itil-wiki">[IT Process Wiki]. -- S. Kempter & Kempter, A.: "[https://wiki.en.it-processmaps.com/index.php/Main_Page IT Process Wiki]. -- The Wiki about the IT Infrastructure Library ITIL<sup><small>®</small></sup> (ITIL 2011, ITIL V3 & V2), ISO 20000 and IT Service Management (ITSM). - IT Process Maps; | *<span id="ref-itil-wiki">[IT Process Wiki]. -- S. Kempter & Kempter, A.: "[https://wiki.en.it-processmaps.com/index.php/Main_Page IT Process Wiki]. -- The Wiki about the IT Infrastructure Library ITIL<sup><small>®</small></sup> (ITIL 2011, ITIL V3 & V2), ISO 20000 and IT Service Management (ITSM). - IT Process Maps; Lindau (Bodensee), Germany.</span> | ||
*<span id="ref-service-strategy">[IT Process Wiki - ITIL Service Strategy]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Strategy ITIL Service Strategy]. - IT Process Maps; | *<span id="ref-service-strategy">[IT Process Wiki - ITIL Service Strategy]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Strategy ITIL Service Strategy]. - IT Process Maps; Lindau (Bodensee), Germany.</span> | ||
*<span id="ref-service-design">[IT Process Wiki - ITIL Service Design]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design ITIL Service Design]. - IT Process Maps; | *<span id="ref-service-design">[IT Process Wiki - ITIL Service Design]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design ITIL Service Design]. - IT Process Maps; Lindau (Bodensee), Germany.</span> | ||
*<span id="ref-service-transition">[IT Process Wiki - ITIL Service Transition]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition ITIL Service Transition]. - IT Process Maps; | *<span id="ref-service-transition">[IT Process Wiki - ITIL Service Transition]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Transition ITIL Service Transition]. - IT Process Maps; Lindau (Bodensee), Germany.</span> | ||
*<span id="ref-service-operation">[IT Process Wiki - ITIL Service Operation]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation ITIL Service Operation]. - IT Process Maps; | *<span id="ref-service-operation">[IT Process Wiki - ITIL Service Operation]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Operation ITIL Service Operation]. - IT Process Maps; Lindau (Bodensee), Germany.</span> | ||
*<span id="ref-csi">[IT Process Wiki - ITIL CSI]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_CSI_-_Continual_Service_Improvement ITIL CSI - Continual Service Improvement]. - IT Process Maps; | *<span id="ref-csi">[IT Process Wiki - ITIL CSI]. -- S. Kempter: IT Process Wiki, "[https://wiki.en.it-processmaps.com/index.php/ITIL_CSI_-_Continual_Service_Improvement ITIL CSI - Continual Service Improvement]. - IT Process Maps; Lindau (Bodensee), Germany.</span> | ||
<p> </p> | <p> </p> | ||
Line 504: | Line 525: | ||
<p><small> | <p><small> | ||
<span itemscope="itemscope | <span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | ||
<a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#yasm-itil-differences | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
</span> | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#yasm-itil-differences"> | ||
<span | <span itemprop="name">Main differences</span></a> | ||
<a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#comparison-yasm-itil | <meta itemprop="position" content="1" /></span> › | ||
</span> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<span | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#comparison-yasm-itil"> | ||
<a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#yasm-goes-beyond-itil | <span itemprop="name">ITIL processes and related YaSM processes</span></a> | ||
<meta itemprop="position" content="2" /></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#video-itil-yasm"> | |||
<span itemprop="name">Video: ITIL vs. YaSM</span></a> | |||
<meta itemprop="position" content="3" /></span> › | |||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL#yasm-goes-beyond-itil"> | |||
<span itemprop="name">Where YaSM goes beyond ITIL</span></a> | |||
<meta itemprop="position" content="4" /></span> | |||
</span> | </span> | ||
</small></p> | </small></p> | ||
Line 520: | Line 550: | ||
<link itemprop="url" href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" /> | <link itemprop="url" href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" /> | ||
<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm.jpg" /> | <link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm.jpg" /> | ||
<link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" /> | <link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" /> | ||
<meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" /> | <meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" /> |
Revision as of 16:19, 12 June 2017
Comparison: YaSM and the IT Infrastructure Library ITIL®
Part of: YaSM vs. other service management frameworks and standards
YaSM® was designed to be well aligned with the IT Infrastructure Library ITIL® [1] so that users familiar with ITIL will instantly recognize the common principles.
YaSM, however, is somewhat leaner and less complex. This was important to us because we think both large and small organizations should be able to benefit from service management best practice.
- For a brief summary, watch our animated video about the differences between YaSM and ITIL® (9:28 min.).
YaSM and ITIL®: The main differences
This does not mean that YaSM is simplistic: Every ITIL process serves a purpose, so YaSM does not merely omit a number of ITIL processes, as a number of approaches for "light" or "lean" ITIL would advocate.
Rather, YaSM is less complex because it departs in some areas from ITIL's rigorous service lifecycle structure, and introduces a simpler and more intuitive process structure which distinguishes between service lifecycle processes and supporting service management processes.
To understand why this leads to more simplicity, consider the following example:
ITIL treats configuration management as part of service transition. But configuration management activities also occur elsewhere in the service lifecycle, and configuration information is needed as an input for virtually every ITIL process. This is why YaSM takes the view that it is more straightforward and intuitive to treat configuration management as a "supporting" process outside the service lifecycle.
What is more, the ITIL processes focus on managing services throughout their lifecycle, but there are no explicit processes for setting up and maintaining the service management processes themselves [2]. For example, ITIL describes an incident management process, but is less explicit about how the process comes into existence. YaSM addresses this issue by adding a number of additional supporting processes.
YaSM does not include the more "esoteric" details of ITIL, as it is meant to provide a streamlined and focused set of processes. YaSM's strategic process, for example, is considerably less extensive than in the ITIL books. Organizations using the YaSM model are thus able to start with a set of processes that is easy to understand and readily implementable. If more sophistication is needed in some process areas, users of YaSM can obtain additional guidance from various sources, including the ITIL publications.
Finally, ITIL and YaSM at times use different terminology because ITIL was originally written primarily for IT service providers, whereas YaSM is for any type of organization providing services. This often required the introduction of language that is more readily understood outside IT organizations.
Video: ITIL® vs. YaSM
In this video Stefan Kempter gives you a better understanding of the similarities and differences between YaSM and ITIL® by taking you through a couple of examples.
He shows you how we managed to create a streamlined framework that is in line with ITIL® and covers all key aspects of service management best practice.
- Watch the video: YaSM and ITIL® (9:28 min.)
ITIL processes and corresponding YaSM processes
As YaSM was written to be aligned with ITIL, there are one or several related YaSM service management processes for every ITIL process, as described in the following tables. The notes column contains further explanations on how YaSM relates to specific ITIL processes:
- YaSM vs. ITIL Service Strategy
- YaSM vs. ITIL Service Design
- YaSM vs. ITIL Service Transition
- YaSM vs. ITIL Service Operation
- YaSM vs. ITIL Continual Service Improvement (CSI).
See also:
Notes:
- YaSM is an independent framework and is not officially endorsed by the owners of ITIL.
- All ITIL processes in the following tables are linked to IT Process Map's ITIL® Wiki - the "IT Process Wiki" - where you can find the relevant descriptions of the ITIL processes.
- The process structure in this table is based on ITIL 2011 Edition.
YaSM vs. ITIL Service Strategy
ITIL® processes | Related YaSM processes | Notes |
---|---|---|
1.1 Strategy management for IT services |
| |
1.2 Service portfolio management |
| |
1.3 Financial management for IT services |
| |
1.4 Demand management |
|
|
1.5 Business relationship management |
|
References: [Cabinet Office, 2011a] and [IT Process Wiki - ITIL Service Strategy]
YaSM vs. ITIL Service Design
ITIL® processes | Related YaSM processes | Notes |
---|---|---|
2.1 Design coordination |
| |
2.2 Service catalogue management |
| |
2.3 Service level management |
| |
2.4 Availability management |
| |
2.5 Capacity management |
| |
2.6 IT service continuity management (ITSCM) |
| |
2.7 Information security management |
| |
2.8 Supplier management |
|
References: [Cabinet Office, 2011b] and [IT Process Wiki - ITIL Service Design]
YaSM vs. ITIL Service Transition
ITIL® processes | Related YaSM processes | Notes |
---|---|---|
3.1 Transition planning and support |
| |
3.2 Change management |
| |
3.3 Service asset and configuration management |
| |
3.4 Release and deployment management |
| |
3.5 Service validation and testing |
| |
3.6 Change evaluation |
| |
3.7 Knowledge management |
|
|
References: [Cabinet Office, 2011c] and [IT Process Wiki - ITIL Service Transition]
YaSM vs. ITIL Service Operation
ITIL® processes | Related YaSM processes | Notes |
---|---|---|
4.1 Event management |
| |
4.2 Incident management |
| |
4.3 Request fulfillment |
| |
4.4 Problem management |
| |
4.5 Access management |
|
References: [Cabinet Office, 2011d] and IT Process Wiki - ITIL Service Operation]
YaSM vs. ITIL Continual Service Improvement
ITIL® processes | Related YaSM processes | Notes |
---|---|---|
5.1 The seven-step improvement process |
|
References: [Cabinet Office, 2011e] and [IT Process Wiki - ITIL CSI - Continual Service Improvement]
Where YaSM goes beyond ITIL
While YaSM is somewhat more streamlined than ITIL in many areas, there are also a number of YaSM processes which go beyond the ITIL recommendations. These processes were mostly introduced to improve the alignment of YaSM with other service management standards and frameworks, such as ISO 20000, COBIT® [3], USMBOK™ [4] and CMMI-SVC® [5].
The following table provides an overview of the additional processes and explains their purpose within the YaSM model:
YaSM processes not specified in ITIL® | Notes |
---|---|
SP1: Set up and maintain the service management system |
|
SP6: Manage projects |
|
SP9: Ensure compliance |
|
SP10: Manage human resources |
|
ITIL functions and YaSM
Apart from a set of processes ITIL also describes a number of "functions". For instance, incident management is introduced as a process and facilities management as a function.
By definition, a function is an organizational entity, often characterized by a special area of knowledge or experience. Examples would be the human resources department or a team of experts operating a certain part of the technical infrastructure. Processes, in contrast, are clusters of activities which produce a defined outcome, like the incident resolution process. Several functions may play their part in a process (the team of technical experts may have to perform some activities within the incident resolution process).
Much confusion stems from the fact that in the real world there are often functions and processes with identical names: For example, the human resources management team (a "function") will perform a set of HR-related activities, which as a whole are called the human resources process.
In this context, YaSM consists of a set of processes and does not specifically relate to functions or organizational structures.
Roles are the only type of organizational information described in the YaSM model: For example, the role of 1st level support figures in the incident resolution process, because 1st level support needs to perform a number of activities in this process. This notwithstanding, 1st level support agents will typically belong to an organizational unit or function, such as a support team headed by a support manager.
Related articles
YaSM - an alternative to ITIL®?
by: Stefan Kempter
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? [...]
Is YaSM 'ITIL lite' or 'lean ITIL'?
by: Stefan Kempter
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: [...]
New initiative by AXELOS: ITIL® for non-IT service providers
by: Stefan Kempter
AXELOS announced a new 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. [...]
References
- [Cabinet Office, 2011a]. -- The Cabinet Office: ITIL® Service Strategy (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011b]. -- The Cabinet Office: ITIL® Service Design (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011c]. -- The Cabinet Office: ITIL® Service Transition (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011d]. -- The Cabinet Office: ITIL® Service Operation (2011 Edition). - The Stationery Office; London, UK, July 2011.
- [Cabinet Office, 2011e]. -- The Cabinet Office: ITIL® Continual Service Improvement (2011 Edition). - The Stationery Office; London, UK, July 2011.
External links
- [IT Process Wiki]. -- S. Kempter & Kempter, A.: "IT Process Wiki. -- The Wiki about the IT Infrastructure Library ITIL® (ITIL 2011, ITIL V3 & V2), ISO 20000 and IT Service Management (ITSM). - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Strategy]. -- S. Kempter: IT Process Wiki, "ITIL Service Strategy. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Design]. -- S. Kempter: IT Process Wiki, "ITIL Service Design. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Transition]. -- S. Kempter: IT Process Wiki, "ITIL Service Transition. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL Service Operation]. -- S. Kempter: IT Process Wiki, "ITIL Service Operation. - IT Process Maps; Lindau (Bodensee), Germany.
- [IT Process Wiki - ITIL CSI]. -- S. Kempter: IT Process Wiki, "ITIL CSI - Continual Service Improvement. - IT Process Maps; Lindau (Bodensee), Germany.
Notes
[1] ITIL® is a registered trade mark of AXELOS Limited. - IT Infrastructure Library® is a registered trade mark of AXELOS Limited.
[2] ISO 20000 refers to the service management processes - and other elements like service management policies and plans - as the "service management system (SMS)".
[3] COBIT® is a registered trademark of ISACA (Information Systems Audit and Control Association).
[4] USMBOK™ is a Registered Trade Mark of Virtual Knowledge Solutions International Incorporated (VKSII).
[5] CMMI® and Capability Maturity Model® are registered trademarks of Carnegie Mellon University.
Is based on: The YaSM Process Map - Document: "YaSM and ITIL®".
Main differences › ITIL processes and related YaSM processes › Video: ITIL vs. YaSM › Where YaSM goes beyond ITIL