YaSM and ITIL: Difference between revisions
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
<meta name="description" content="Comparison: YaSM® vs. ITIL®. - The differences and similarities of the two service management frameworks." /> | <meta name="description" content="Comparison: YaSM® vs. ITIL®. - The differences and similarities of the two service management frameworks." /> | ||
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" /> | <meta property="og:url" content="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" /> | ||
<meta property="og:title" content="YaSM and ITIL® | YaSM Service Management Wiki" /> | <meta property="og:title" content="Comparison: YaSM and ITIL® | YaSM Service Management Wiki" /> | ||
<meta property="og:description" content=" | <meta property="og:description" content="YaSM® vs. ITIL®. - Differences and similarities of the two service management frameworks." /> | ||
<meta property="og:site_name" content="YaSM"> | <meta property="og:site_name" content="YaSM"> | ||
<meta property="og:type" content="article" /> | |||
<meta property="article:publisher" content="https://www.facebook.com/yasmcom" /> | |||
<meta property="fb:admins" content="100002035253209" /> | |||
<meta property="fb:admins" content="100002592864414" /> | |||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm.jpg" /> | |||
<meta property="og:image:width" content="759" /> | |||
<meta property="og:image:height" content="450" /> | |||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm-service-management.jpg" /> | <meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm-service-management.jpg" /> | ||
<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" /> | ||
< | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
<html> | <html><a href="https://yasm.com/wiki/de/index.php/YaSM_und_ITIL"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/> | ||
<a href="https://yasm.com/wiki/de/index.php/YaSM_und_ITIL"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/> | |||
<p> </p> | <p> </p> | ||
<p><b>Comparison:</b | <p><b>Comparison:</b> YaSM and the IT Infrastructure Library ITIL<sup><small>®</small></sup></p> | ||
<p><b>Part of</b>: <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></p> | ||
<p> </p> | <p> </p> | ||
<div itemscope itemtype="https://schema.org/ImageObject"> | |||
<a href="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm.jpg" title="ITIL vs. YaSM service management" itemprop="contentUrl"> | |||
<meta itemprop="caption" content="ITIL vs. YaSM. - Service management frameworks compared - the differences and similarities." /> | |||
<meta itemprop="width" content="759" /> | |||
<meta itemprop="height" content="450" /> | |||
<meta itemprop="keywords" content="ITIL YaSM" /> | |||
<meta itemprop="keywords" content="ITIL vs YaSM" /> | |||
<meta itemprop="keywords" content="ITIL YaSM comparison" /> | |||
<img itemprop="thumbnailUrl" style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm-service-management.jpg" width="400" height="348" title="ITIL vs. YaSM service management" alt="ITIL vs. YaSM. - Service management frameworks compared - the differences and similarities." /></a></div> | |||
<p><span | <p><span id="md-webpage-description" itemprop="description">YaSM® was designed to be well aligned with the <a href="http://www.itil-officialsite.com" title="Go to the official ITIL site by Axelos">IT Infrastructure Library ITIL®</a> <a href="#ITIL">[1]</a> so that users familiar with ITIL will instantly recognize the common principles.</span></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.</html> | <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.</html> | ||
Line 45: | Line 57: | ||
==<span id="comparison-yasm-itil">ITIL processes and corresponding YaSM processes</span>== | ==<span id="comparison-yasm-itil">ITIL processes and corresponding YaSM processes</span>== | ||
<html><p>As YaSM was written to be aligned with ITIL, there are one or several related <a href="https://yasm.com/wiki/en/index.php/YaSM_Processes" title="YaSM service management processes">YaSM service management processes</a> for every ITIL process, as described in the following tables. The notes column contains further explanations on <span itemprop="educationalUse">how YaSM relates to specific ITIL processes</span></html>: | <html><p>As YaSM was written to be aligned with ITIL, there are one or several related <a href="https://yasm.com/wiki/en/index.php/YaSM_Processes" title="YaSM service management processes">YaSM service management processes</a> for every ITIL process, as described in the following tables. The notes column contains further explanations on <span id="md-webpage-educationalUse" itemprop="educationalUse">how YaSM relates to specific ITIL processes</span></html>: | ||
*[[#service-strategy|YaSM vs. ITIL Service Strategy]] | *[[#service-strategy|YaSM vs. ITIL Service Strategy]] | ||
Line 74: | Line 86: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL& | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL<sup><small>®</small></sup> processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | !style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/ITIL_Strategy_Management | |1.1 [https://wiki.en.it-processmaps.com/index.php/ITIL_Strategy_Management Strategy management for IT services] | ||
| | | | ||
*[[LP1: Set the strategic direction]] | *[[LP1: Set the strategic direction]] | ||
Line 85: | Line 97: | ||
*ITIL provides additional guidance and background information, for example about analyzing the internal and external environments and defining the service provider's position in the market spaces to be served. | *ITIL provides additional guidance and background information, for example about analyzing the internal and external environments and defining the service provider's position in the market spaces to be served. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Service_Portfolio_Management | |1.2 [https://wiki.en.it-processmaps.com/index.php/Service_Portfolio_Management Service portfolio management] | ||
| | | | ||
*[[LP1: Set the strategic direction]]; | *[[LP1: Set the strategic direction]]; | ||
Line 94: | Line 106: | ||
*Decisions about the composition of the service portfolio (i.e. the mix of services to be offered to customers) are the responsibility of YaSM's strategic process. | *Decisions about the composition of the service portfolio (i.e. the mix of services to be offered to customers) are the responsibility of YaSM's strategic process. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Financial_Management | |1.3 [https://wiki.en.it-processmaps.com/index.php/Financial_Management Financial management for IT services] | ||
| | | | ||
*[[SP12: Manage service financials]] | *[[SP12: Manage service financials]] | ||
Line 101: | Line 113: | ||
*ITIL offers more detailed advice in a number of areas: for example, it explains commonly used cost models and charging methods. | *ITIL offers more detailed advice in a number of areas: for example, it explains commonly used cost models and charging methods. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/ITIL_Demand_Management | |1.4 [https://wiki.en.it-processmaps.com/index.php/ITIL_Demand_Management Demand management] | ||
| | | | ||
*-/- | *-/- | ||
Line 108: | Line 120: | ||
*The ITIL publications provide additional guidance, for example on the concept of patterns of business activity. | *The ITIL publications provide additional guidance, for example on the concept of patterns of business activity. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Business_Relationship_Management | |1.5 [https://wiki.en.it-processmaps.com/index.php/Business_Relationship_Management Business relationship management] | ||
| | | | ||
*[[SP3: Manage customer relationships]] | *[[SP3: Manage customer relationships]] | ||
Line 127: | Line 139: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL& | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL<sup><small>®</small></sup> processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | !style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination | |2.1 [https://wiki.en.it-processmaps.com/index.php/ITIL_Design_Coordination Design coordination] | ||
| | | | ||
*[[LP2: Design new or changed services]]; | *[[LP2: Design new or changed services]]; | ||
Line 139: | Line 151: | ||
*A key output from YaSM's service design process is the "service implementation blueprint", which describes what capabilities are required in order to be able to offer a new or changed service, and outlines the approach to creating the required service infrastructure and other capabilities. The equivalent in ITIL is the "service design package (SDP)". The SDP is supposed to contain a considerable amount of additional information, such as various policies and plans. YaSM keeps such information in other documents. | *A key output from YaSM's service design process is the "service implementation blueprint", which describes what capabilities are required in order to be able to offer a new or changed service, and outlines the approach to creating the required service infrastructure and other capabilities. The equivalent in ITIL is the "service design package (SDP)". The SDP is supposed to contain a considerable amount of additional information, such as various policies and plans. YaSM keeps such information in other documents. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management | |2.2 [https://wiki.en.it-processmaps.com/index.php/Service_Catalogue_Management Service catalogue management] | ||
| | | | ||
*[[SP2: Maintain the service portfolio]] | *[[SP2: Maintain the service portfolio]] | ||
Line 146: | Line 158: | ||
*The YaSM process for maintaining the service portfolio contains activities for publishing service catalogs and keeping them consistent and up to date, in line with updates to the service portfolio. | *The YaSM process for maintaining the service portfolio contains activities for publishing service catalogs and keeping them consistent and up to date, in line with updates to the service portfolio. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Service_Level_Management | |2.3 [https://wiki.en.it-processmaps.com/index.php/Service_Level_Management Service level management] | ||
| | | | ||
*[[LP2: Design new or changed services]]; | *[[LP2: Design new or changed services]]; | ||
Line 160: | Line 172: | ||
*ITIL provides some additional advice, for example on the design of SLA frameworks. | *ITIL provides some additional advice, for example on the design of SLA frameworks. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Availability_Management | |2.4 [https://wiki.en.it-processmaps.com/index.php/Availability_Management Availability management] | ||
| | | | ||
*[[LP2: Design new or changed services]]; | *[[LP2: Design new or changed services]]; | ||
Line 171: | Line 183: | ||
*The ITIL books offer additional guidance, for example on how to design services and their underlying technical infrastructure for availability. | *The ITIL books offer additional guidance, for example on how to design services and their underlying technical infrastructure for availability. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|<span id="yasm-vs-itil-capacity-management">[https://wiki.en.it-processmaps.com/index.php/Capacity_Management | |<span id="yasm-vs-itil-capacity-management">2.5 [https://wiki.en.it-processmaps.com/index.php/Capacity_Management Capacity management]</span> | ||
| | | | ||
*[[LP2: Design new or changed services]]; | *[[LP2: Design new or changed services]]; | ||
Line 182: | Line 194: | ||
*The ITIL books may be consulted for additional advice, for example with regards to capacity monitoring, analysis and tuning. | *The ITIL books may be consulted for additional advice, for example with regards to capacity monitoring, analysis and tuning. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/IT_Service_Continuity_Management | |2.6 [https://wiki.en.it-processmaps.com/index.php/IT_Service_Continuity_Management IT service continuity management (ITSCM)] | ||
| | | | ||
*[[SP8: Prepare for disaster events]] | *[[SP8: Prepare for disaster events]] | ||
Line 192: | Line 204: | ||
*ITIL offers additional advice, such as examples of potential risks and threats as well as recovery options. | *ITIL offers additional advice, such as examples of potential risks and threats as well as recovery options. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/IT_Security_Management | |2.7 [https://wiki.en.it-processmaps.com/index.php/IT_Security_Management Information security management] | ||
| | | | ||
*[[SP7: Ensure security]] | *[[SP7: Ensure security]] | ||
Line 200: | Line 212: | ||
*The ITIL publications contain additional advice, such as a list of recommended (supporting) security policies, and an overview of risk assessment and management methods. | *The ITIL publications contain additional advice, such as a list of recommended (supporting) security policies, and an overview of risk assessment and management methods. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Supplier_Management | |2.8 [https://wiki.en.it-processmaps.com/index.php/Supplier_Management Supplier management] | ||
| | | | ||
*[[SP11: Manage suppliers]] | *[[SP11: Manage suppliers]] | ||
Line 222: | Line 234: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL& | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL<sup><small>®</small></sup> processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | !style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support | |3.1 [https://wiki.en.it-processmaps.com/index.php/Project_Management_-_Transition_Planning_and_Support Transition planning and support] | ||
| | | | ||
*[[SP6: Manage projects]] | *[[SP6: Manage projects]] | ||
Line 233: | Line 245: | ||
*ITIL takes a slightly different approach: The transition planning and support process is specifically meant to provide "overall planning for service transition projects". Some detailed transition planning is performed by two other ITIL processes, change management and release and deployment management. | *ITIL takes a slightly different approach: The transition planning and support process is specifically meant to provide "overall planning for service transition projects". Some detailed transition planning is performed by two other ITIL processes, change management and release and deployment management. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Change_Management | |3.2 [https://wiki.en.it-processmaps.com/index.php/Change_Management Change management] | ||
| | | | ||
*[[SP5: Assess and coordinate changes]] | *[[SP5: Assess and coordinate changes]] | ||
Line 244: | Line 256: | ||
*While ITIL stipulates that the change manager produce a list of projected service outages (PSO), YaSM suggests that operational staff is in a better position to maintain a "calendar of planned service outages". This calendar takes into account outages due to various reasons, such as change deployments, operational activities, security tests, ... | *While ITIL stipulates that the change manager produce a list of projected service outages (PSO), YaSM suggests that operational staff is in a better position to maintain a "calendar of planned service outages". This calendar takes into account outages due to various reasons, such as change deployments, operational activities, security tests, ... | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management | |3.3 [https://wiki.en.it-processmaps.com/index.php/Service_Asset_and_Configuration_Management Service asset and configuration management] | ||
| | | | ||
*[[SP4: Manage configuration information]] | *[[SP4: Manage configuration information]] | ||
Line 253: | Line 265: | ||
*With regards to status accounting, YaSM's configuration management process defines a suitable set of allowed states for each CI type, and relies on other service management processes to record the status changes. | *With regards to status accounting, YaSM's configuration management process defines a suitable set of allowed states for each CI type, and relies on other service management processes to record the status changes. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management | |3.4 [https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management Release and deployment management] | ||
| | | | ||
*[[LP3: Build new or changed services]]; | *[[LP3: Build new or changed services]]; | ||
Line 262: | Line 274: | ||
*ITIL offers additional advice, for example on the design of release packages and deployment options for IT infrastructure. | *ITIL offers additional advice, for example on the design of release packages and deployment options for IT infrastructure. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing | |3.5 [https://wiki.en.it-processmaps.com/index.php/Service_Validation_and_Testing Service validation and testing] | ||
| | | | ||
*[[LP3: Build new or changed services]] | *[[LP3: Build new or changed services]] | ||
Line 269: | Line 281: | ||
*The ITIL books contain additional information, such as an explanation of commonly used testing strategies and test types. | *The ITIL books contain additional information, such as an explanation of commonly used testing strategies and test types. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation | |3.6 [https://wiki.en.it-processmaps.com/index.php/ITIL_Change_Evaluation Change evaluation] | ||
| | | | ||
*[[SP5: Assess and coordinate changes]] | *[[SP5: Assess and coordinate changes]] | ||
Line 275: | Line 287: | ||
*ITIL stipulates that certain types of (significant) changes should be subjected to a formal change evaluation process. There is no separate change evaluation process in YaSM. Instead, YaSM treats change evaluation as part of its change assessment process. | *ITIL stipulates that certain types of (significant) changes should be subjected to a formal change evaluation process. There is no separate change evaluation process in YaSM. Instead, YaSM treats change evaluation as part of its change assessment process. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Knowledge_Management | |3.7 [https://wiki.en.it-processmaps.com/index.php/Knowledge_Management Knowledge management] | ||
| | | | ||
*-/- | *-/- | ||
Line 293: | Line 305: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL& | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL<sup><small>®</small></sup> processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | !style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Event_Management | |4.1 [https://wiki.en.it-processmaps.com/index.php/Event_Management Event management] | ||
| | | | ||
*[[LP4: Operate the services]] | *[[LP4: Operate the services]] | ||
Line 305: | Line 317: | ||
*The ITIL publications contain additional guidance, for example on event filtering and correlation rules. | *The ITIL publications contain additional guidance, for example on event filtering and correlation rules. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Incident_Management | |4.2 [https://wiki.en.it-processmaps.com/index.php/Incident_Management Incident management] | ||
| | | | ||
*[[LP4.6: Resolve incidents and service requests]] | *[[LP4.6: Resolve incidents and service requests]] | ||
Line 313: | Line 325: | ||
*ITIL states that incident management is about restoring services as quickly as possible, while problem management is about diagnosing and resolving the underlying causes of incidents. Individual organizations, however, are given some freedom regarding the precise rules on when to invoke problem management from incident management. In this respect, YaSM adopts a simple approach: The incident resolution process takes all necessary action to resolve an incident, possibly by applying a workaround and involving experts in 2nd and 3rd level support. The problem resolution process is called upon only after the incident has been closed, for example in cases where the underlying cause of an incident is unresolved or unclear. | *ITIL states that incident management is about restoring services as quickly as possible, while problem management is about diagnosing and resolving the underlying causes of incidents. Individual organizations, however, are given some freedom regarding the precise rules on when to invoke problem management from incident management. In this respect, YaSM adopts a simple approach: The incident resolution process takes all necessary action to resolve an incident, possibly by applying a workaround and involving experts in 2nd and 3rd level support. The problem resolution process is called upon only after the incident has been closed, for example in cases where the underlying cause of an incident is unresolved or unclear. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment | |4.3 [https://wiki.en.it-processmaps.com/index.php/Request_Fulfilment Request fulfillment] | ||
| | | | ||
*[[LP4.6: Resolve incidents and service requests]] | *[[LP4.6: Resolve incidents and service requests]] | ||
Line 320: | Line 332: | ||
*While ITIL suggests implementing two different processes for managing incidents and service requests, YaSM suggests that these processes are very similar in nature. There is thus one process in YaSM to deal with both incidents and service requests. | *While ITIL suggests implementing two different processes for managing incidents and service requests, YaSM suggests that these processes are very similar in nature. There is thus one process in YaSM to deal with both incidents and service requests. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Problem_Management | |4.4 [https://wiki.en.it-processmaps.com/index.php/Problem_Management Problem management] | ||
| | | | ||
*[[LP4.7: Resolve problems]] | *[[LP4.7: Resolve problems]] | ||
Line 329: | Line 341: | ||
*ITIL offers additional background information, especially on problem analysis techniques. | *ITIL offers additional background information, especially on problem analysis techniques. | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Access_Management | |4.5 [https://wiki.en.it-processmaps.com/index.php/Access_Management Access management] | ||
| | | | ||
*[[LP4: Operate the services]]; | *[[LP4: Operate the services]]; | ||
Line 351: | Line 363: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL& | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|ITIL<sup><small>®</small></sup> processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | !style="background:#379988; font-size: 110%; color:#ffffff; width:20%"|Related YaSM processes | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | !style="background:#379988; font-size: 110%; color:#ffffff; width:60%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
|[https://wiki.en.it-processmaps.com/index.php/Process_Evaluation | |5.1 [https://wiki.en.it-processmaps.com/index.php/Process_Evaluation The seven-step improvement process] | ||
| | | | ||
*[[LP5: Improve the services]] | *[[LP5: Improve the services]] | ||
Line 370: | Line 382: | ||
==<span id="yasm-goes-beyond-itil">Where YaSM goes beyond ITIL</span>== | ==<span id="yasm-goes-beyond-itil">Where YaSM goes beyond ITIL</span>== | ||
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& | 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<sup><small>®</small></sup> [[#COBIT|[3]]], USMBOK™ [[#USMBOK|[4]]] and CMMI-SVC<sup><small>®</small></sup> [[#CMMI|[5]]]. | ||
<p> </p> | <p> </p> | ||
Line 380: | Line 392: | ||
{| class="wikitable" style="background: white;" | {| class="wikitable" style="background: white;" | ||
|- | |- | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:25%"|YaSM processes not specified in ITIL& | !style="background:#379988; font-size: 110%; color:#ffffff; width:25%"|YaSM processes not specified in ITIL<sup><small>®</small></sup> | ||
!style="background:#379988; font-size: 110%; color:#ffffff; width:75%"|Notes | !style="background:#379988; font-size: 110%; color:#ffffff; width:75%"|Notes | ||
|-style="vertical-align:top" | |-style="vertical-align:top" | ||
Line 429: | Line 441: | ||
<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> | ||
<div style="margin-left: 30%; color:#636363"> | <div style="margin-left: 30%; color:#636363"> | ||
<p style="margin-top: 0;"><a href="https://yasm.com/en/blog/itil-alternative-yasm">YaSM - an alternative to ITIL& | <p style="margin-top: 0;"><a href="https://yasm.com/en/blog/itil-alternative-yasm">YaSM - an alternative to ITIL<sup><small>®</small></sup>?</a></p> | ||
<p><small>by: Stefan Kempter | <p><small>by: Stefan Kempter</small></p> | ||
<p>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? <a href="https://yasm.com/en/blog/itil-alternative-yasm">[...]</a></p></div> | <p>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? <a href="https://yasm.com/en/blog/itil-alternative-yasm">[...]</a></p></div> | ||
Line 438: | Line 450: | ||
<div style="margin-left: 30%; color:#636363"> | <div style="margin-left: 30%; color:#636363"> | ||
<p style="margin-top: 0;"><a href="https://yasm.com/en/blog/yasm-itil-lite">Is YaSM 'ITIL lite' or 'lean ITIL'?</a></p> | <p style="margin-top: 0;"><a href="https://yasm.com/en/blog/yasm-itil-lite">Is YaSM 'ITIL lite' or 'lean ITIL'?</a></p> | ||
<p><small>by: Stefan Kempter | <p><small>by: Stefan Kempter</small></p> | ||
<p>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: <a href="https://yasm.com/en/blog/yasm-itil-lite">[...]</a></p></div> | <p>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: <a href="https://yasm.com/en/blog/yasm-itil-lite">[...]</a></p></div> | ||
Line 445: | Line 457: | ||
<a href="https://yasm.com/en/blog/itil-non-it-services"><img src="https://yasm.com/en/content/blog/150503-itil-non-it-services/img-180x110.jpg" alt=" The usage of ITIL in non-IT environments" style="display: block; float: left; margin-right: 10px"/></a> | <a href="https://yasm.com/en/blog/itil-non-it-services"><img src="https://yasm.com/en/content/blog/150503-itil-non-it-services/img-180x110.jpg" alt=" The usage of ITIL in non-IT environments" style="display: block; float: left; margin-right: 10px"/></a> | ||
<div style="margin-left: 30%; color:#636363"> | <div style="margin-left: 30%; color:#636363"> | ||
<p style="margin-top: 0;"><a href="https://yasm.com/en/blog/itil-non-it-services">New initiative by AXELOS: ITIL& | <p style="margin-top: 0;"><a href="https://yasm.com/en/blog/itil-non-it-services">New initiative by AXELOS: ITIL<sup><small>®</small></sup> for non-IT service providers</a></p> | ||
<p><small>by: Stefan Kempter | <p><small>by: Stefan Kempter</small></p> | ||
<p>AXELOS announced a new initiative to promote the usage of ITIL& | <p>AXELOS announced a new initiative to promote the usage of ITIL<sup><small>®</small></sup> in non-IT environments: Their aim is provide additional guidance, so that non-IT service providers are better able to benefit from ITIL. <a href="https://yasm.com/en/blog/itil-non-it-services">[...]</a></p></div><p> | ||
</html> | </html> | ||
Line 453: | Line 465: | ||
==References== | ==References== | ||
*<span id="ref-cabinet-office-2011a">[Cabinet Office, 2011a]. -- The Cabinet Office: ITIL& | *<span id="ref-cabinet-office-2011a">[Cabinet Office, 2011a]. -- The Cabinet Office: ITIL<sup><small>®</small></sup> Service Strategy (2011 Edition). - The Stationery Office; London, UK, July 2011.</span> | ||
*<span id="ref-cabinet-office-2011b">[Cabinet Office, 2011b]. -- The Cabinet Office: ITIL& | *<span id="ref-cabinet-office-2011b">[Cabinet Office, 2011b]. -- The Cabinet Office: ITIL<sup><small>®</small></sup> Service Design (2011 Edition). - The Stationery Office; London, UK, July 2011.</span> | ||
*<span id="ref-cabinet-office-2011c">[Cabinet Office, 2011c]. -- The Cabinet Office: ITIL& | *<span id="ref-cabinet-office-2011c">[Cabinet Office, 2011c]. -- The Cabinet Office: ITIL<sup><small>®</small></sup> Service Transition (2011 Edition). - The Stationery Office; London, UK, July 2011.</span> | ||
*<span id="ref-cabinet-office-2011d">[Cabinet Office, 2011d]. -- The Cabinet Office: ITIL& | *<span id="ref-cabinet-office-2011d">[Cabinet Office, 2011d]. -- The Cabinet Office: ITIL<sup><small>®</small></sup> Service Operation (2011 Edition). - The Stationery Office; London, UK, July 2011.</span> | ||
*<span id="ref-cabinet-office-2011e">[Cabinet Office, 2011e]. -- The Cabinet Office: ITIL& | *<span id="ref-cabinet-office-2011e">[Cabinet Office, 2011e]. -- The Cabinet Office: ITIL<sup><small>®</small></sup> Continual Service Improvement (2011 Edition). - The Stationery Office; London, UK, July 2011.</span> | ||
<p> </p> | <p> </p> | ||
==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& | *<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; Pfronten, 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; Pfronten, 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; Pfronten, 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; Pfronten, 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; Pfronten, Germany.</span> | ||
Line 471: | Line 483: | ||
<p> </p> | <p> </p> | ||
== | == Notes == | ||
[1] <span id="ITIL">ITIL<sup><small>®</small></sup> is a registered trade mark of AXELOS Limited. - IT Infrastructure Library<sup><small>®</small></sup> is a registered trade mark of AXELOS Limited.</span><br /> | |||
[2] <span id="ISO20000">ISO 20000 refers to the service management processes - and other elements like service management policies and plans - as the "service management system (SMS)".</span><br /> | |||
[3] <span id="COBIT">COBIT<sup><small>®</small></sup> is a registered trademark of ISACA (Information Systems Audit and Control Association).</span><br /> | |||
[4] <span id="USMBOK">USMBOK™ is a Registered Trade Mark of Virtual Knowledge Solutions International Incorporated (VKSII).</span><br /> | |||
[5] <span id="CMMI">CMMI<sup><small>®</small></sup> and Capability Maturity Model<sup><small>®</small></sup> are registered trademarks of Carnegie Mellon University.</span> | |||
<p> </p> | <p> </p> | ||
== | <html><img src="https://yasm.com/wiki/en/img/yasm-frameworks/Itil-vs-yasm-180x110.jpg" width="180" height="110" title="ITIL vs. YaSM service management" alt="ITIL vs. YaSM. - Service management frameworks compared. - Thumbnail." style="display: block; float: left; margin-right: 10px" /></p> | ||
<div style="margin-left: 30%; color:#636363"> | |||
<p style="margin-top: 0;">Is based on: The <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a> - Document: "YaSM and ITIL<sup><small>®</small></sup>".</p> | |||
< | <p><small>By:  Andrea Kempter <a rel="author" href="https://plus.google.com/113316270668629760475/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Author: Andrea Kempter, IT Process Maps GbR" /></a>  and  Stefan Kempter <a href="https://plus.google.com/111925560448291102517/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Contributor: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</small><br style="clear:both;"/></div> | ||
<p> </p> | |||
</ | |||
</ | |||
<p><small> | <p><small> | ||
Line 516: | Line 512: | ||
</span> | </span> | ||
</small></p> | </small></p> | ||
</ | |||
<!-- define schema.org/WebPage --> <span itemid="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" itemscope itemtype="https://schema.org/WebPage" itemref="md-webpage-description md-webpage-educationalUse"> | |||
<meta itemprop="name Headline" content="YaSM and ITIL" /> | |||
<meta itemprop="alternativeHeadline" content="YaSM and the IT Infrastructure Library 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" /> | |||
<meta itemprop="significantLinks" content="https://yasm.com/en/blog/itil-alternative-yasm" /> | |||
<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="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://yasm.com/wiki/de/index.php/YaSM_und_ITIL" /> | |||
<link itemprop="publisher" href="https://yasm.com/en/#YaSMBrand" /> | |||
<link itemprop="copyrightHolder creator" href="https://yasm.com/en/contact#ITProcessMapsOrg" /> | |||
<link itemprop="author" href="https://yasm.com/en/misc/team#AndreaKempter" /> | |||
<link itemprop="contributor" href="https://yasm.com/en/misc/team#StefanKempter" /> | |||
</span><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:Service management frameworks and standards]] | [[Category:Service management frameworks and standards]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 09:19, 3 October 2016
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.
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.
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 "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 blog posts
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; Pfronten, Germany.
- [IT Process Wiki - ITIL Service Strategy]. -- S. Kempter: IT Process Wiki, "ITIL Service Strategy. - IT Process Maps; Pfronten, Germany.
- [IT Process Wiki - ITIL Service Design]. -- S. Kempter: IT Process Wiki, "ITIL Service Design. - IT Process Maps; Pfronten, Germany.
- [IT Process Wiki - ITIL Service Transition]. -- S. Kempter: IT Process Wiki, "ITIL Service Transition. - IT Process Maps; Pfronten, Germany.
- [IT Process Wiki - ITIL Service Operation]. -- S. Kempter: IT Process Wiki, "ITIL Service Operation. - IT Process Maps; Pfronten, Germany.
- [IT Process Wiki - ITIL CSI]. -- S. Kempter: IT Process Wiki, "ITIL CSI - Continual Service Improvement. - IT Process Maps; Pfronten, 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 › Where YaSM goes beyond ITIL