What is YaSM: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<itpmch><title>What is YaSM Service Management? | YaSM Service Management Wiki</title> | <itpmch><title>What is YaSM Service Management? | YaSM Service Management Wiki</title> | ||
<meta name="keywords" content="what is yasm, yasm idea, about yasm" /> | <meta name="keywords" content="what is yasm, yasm idea, about yasm" /> | ||
<meta name="description" content="The | <meta name="description" content="The YaSM model is a translation of service management 'best practice' into a streamlined, accessible set of processes and ready-to-use templates." /> | ||
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/What_is_YaSM" /> | <meta property="og:url" content="https://yasm.com/wiki/en/index.php/What_is_YaSM" /> | ||
<meta property="og:title" content="What is YaSM Service Management? | YaSM Service Management Wiki" /> | <meta property="og:title" content="What is YaSM Service Management? | YaSM Service Management Wiki" /> | ||
<meta property="og:description" content="The | <meta property="og:description" content="The YaSM model is a translation of service management 'best practice' into a streamlined, accessible set of processes and ready-to-use templates." /> | ||
<meta property="og:site_name" content="YaSM"> | <meta property="og:site_name" content="YaSM"> | ||
<meta property="og:type" content="article" /> | <meta property="og:type" content="article" /> | ||
Line 16: | Line 16: | ||
<meta name="twitter:creator" content="@yasmcom"> | <meta name="twitter:creator" content="@yasmcom"> | ||
<meta name="twitter:title" content="What is YaSM Service Management?"> | <meta name="twitter:title" content="What is YaSM Service Management?"> | ||
<meta name="twitter:description" content="The | <meta name="twitter:description" content="The YaSM model is a translation of service management 'best practice' into a streamlined, accessible set of processes and ready-to-use templates."> | ||
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/what-is-yasm/Yasm-and-other-service-management-frameworks.jpg"> | <meta name="twitter:image" content="https://yasm.com/wiki/en/img/what-is-yasm/Yasm-and-other-service-management-frameworks.jpg"> | ||
<meta name="twitter:image:alt" content="YaSM and other service management frameworks. - YaSM vs. ITIL®, COBIT®, CMMI-SVC® | <meta name="twitter:image:alt" content="YaSM and other service management frameworks. - YaSM vs. ITIL®, ISO 20000 (ISO/IEC 20000), COBIT®, CMMI-SVC® and USMBOK™."> | ||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | <link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | ||
</itpmch> | </itpmch> | ||
Line 27: | Line 27: | ||
<img style="margin:0px 25px 20px 0px; float:left;" src="https://yasm.com/wiki/en/img/logo-yasm-wiki.png" width="135" height="135" title="YaSM - Yet another Service Management Model" alt="Fig. 1: YaSM® - Yet another Service Management Model." /> | <img style="margin:0px 25px 20px 0px; float:left;" src="https://yasm.com/wiki/en/img/logo-yasm-wiki.png" width="135" height="135" title="YaSM - Yet another Service Management Model" alt="Fig. 1: YaSM® - Yet another Service Management Model." /> | ||
<p | <p>Why 'Yet another Service Management Model'?</p> | ||
<p>The idea behind YaSM<sup><small>®</small></sup> <a href="#YaSM" title="YaSM trademark">[1]</a> is not to add yet another service management framework to the many that are already in existence, but to describe a straightforward set of processes that enables organizations to learn by example and bridge the gap between theory and practice.</html> | |||
To this end we assessed the most often used frameworks and standards for | To this end we assessed the most often used frameworks and standards for service management and ITSM, in particular ITIL<sup><small>®</small></sup> [[#ITIL|[2]]], ISO 20000, COBIT<sup><small>®</small></sup> [[#COBIT|[3]]], USMBOK™ [[#USMBOK|[4]]], CMMI-SVC<sup><small>®</small></sup> [[#CMMI|[5]]], SIAM™ [[#SIAM|[6]]] and VeriSM™ [[#VeriSM|[7]]], and assimilated the common principles. | ||
The result of this effort - <i>the YaSM model</i> - is streamlined insofar as it has a | The result of this effort - <i>the YaSM model</i> - is streamlined insofar as it has a perfectly clear [[YaSM_Processes|structure]] that makes it easy to understand the purpose of each process. For each process, YaSM provides a detailed template, describing the activities to be performed, the required inputs and the resulting outputs, as well as the responsibilities. | ||
<p> </p> | <p> </p> | ||
Line 42: | Line 43: | ||
<p> </p> | <p> </p> | ||
==<span id="yasm-idea">YaSM | ==<span id="yasm-idea">YaSM isn't about blindly following 'best practice'</span>== | ||
The YaSM processes are not prescriptive. YaSM is rather a basis for defining tailor-made processes that work in your organization. | |||
YaSM | And YaSM doesn't have to be 'implemented' in full. You can start small, concentrating on those process improvements that offer the most benefits. | ||
Giving the YaSM model a clear, easily understood structure was important to us because we wanted to ensure the model can be adopted in a flexible way: In our experience it is almost impossible to simplify a complex system - while starting with something simple and adding more sophistication where needed is relatively easy. | |||
For a first introduction to the YaSM processes, please refer to | For a first introduction to the YaSM processes, please refer to the overview of "[[YaSM_Processes|YaSM service management processes]]" in this Wiki. | ||
<p> </p> | <p> </p> | ||
==<span id="framework-for-service-provider">A | ==<span id="framework-for-service-provider">A model for everyone in the business of providing services</span>== | ||
<html>Service management frameworks (especially <a href="https://wiki.en.it-processmaps.com/index.php/ | <html>Service management frameworks (especially <a href="https://wiki.en.it-processmaps.com/index.php/History_of_ITIL" title="IT Process Wiki: What is ITIL®?">ITIL</a>) have until recently been used mainly in the domain of information technology (IT) services, for whom these frameworks were originally created.</p> | ||
<p> | <p>As ITIL grew popular, more and more organizations realized that ITIL and service management best practice can be applied to all types of services, such as HR, financial, healthcare, etc. (a trend that is often referred to as "enterprise service management"). So we made a point of ensuring that YaSM is accessible and easy to understand for everyone providing services.</html> | ||
<p> </p> | <p> </p> | ||
==<span id="yasm-other-service-management-frameworks">YaSM and | ==<span id="yasm-other-service-management-frameworks">YaSM and ITIL, ISO 20000, SIAM, VeriSM, DevOps, …</span>== | ||
Time never stands still, and the service management discipline keeps evolving. ITIL started some 30 years ago with a focus on operating IT infrastructure. Today many service providers are better described as 'service integrators', as their customer-facing services are based on supporting services supplied by third parties. What's more, service management best practice is increasingly applied in other areas outside of the IT organization (see above). | |||
< | This has led to the emergence of new concepts, each with its own focus: | ||
SIAM, for example, contains guidance specifically for service integration, and VeriSM introduces the <i>'management mesh'</i> as a management approach from the organizational level. At the same time, service providers discovered that they can greatly benefit from concepts such as Agile, Lean, DevOps, Kanban, etc. | |||
As a result, the service management discipline is now getting more diverse. But its key principles are well established, as enshrined in ISO 20000, the international standard for service management. We have thus ensured the YaSM model is perfectly aligned with ISO 20000. | |||
Everyone versed in ITIL, ISO 20000, SIAM or VeriSM will instantly feel at home, and you can easily extend the YaSM processes with inputs from these frameworks - or indeed with any other concepts and ideas that help you with providing better services. | |||
<html> </p> | |||
<div itemscope itemtype="https://schema.org/ImageObject"><a href="https://yasm.com/wiki/en/img/what-is-yasm/Yasm-and-other-service-management-frameworks.jpg" title="YaSM and other service management frameworks" itemprop="contentUrl"> | <div itemscope itemtype="https://schema.org/ImageObject"><a href="https://yasm.com/wiki/en/img/what-is-yasm/Yasm-and-other-service-management-frameworks.jpg" title="YaSM and other service management frameworks" itemprop="contentUrl"> | ||
Line 77: | Line 86: | ||
<div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 2:</b> </span><small><span itemprop="caption">YaSM and other service management frameworks. - YaSM vs. ITIL®, COBIT®, CMMI-SVC®, USMBOK™ and ISO 20000.</span></small></div></div> | <div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 2:</b> </span><small><span itemprop="caption">YaSM and other service management frameworks. - YaSM vs. ITIL®, COBIT®, CMMI-SVC®, USMBOK™ and ISO 20000.</span></small></div></div> | ||
<br style="clear:both;"/><p></html> | <br style="clear:both;"/><p></html> | ||
Please refer to the following wiki pages for more details on how the most popular service management standards and frameworks relate to YaSM: | Please refer to the following wiki pages for more details on how the most popular service management standards and frameworks relate to YaSM: | ||
Line 94: | Line 99: | ||
==<span id="yasm-process-map">YaSM and the YaSM Process Map</span>== | ==<span id="yasm-process-map">YaSM and the YaSM Process Map</span>== | ||
YaSM is a | <html>The main product in the YaSM product family is the <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map">YaSM Process Map</a>: For each process and sub-process, the process model defines in the form of a diagram the activities to be performed, the required inputs and the resulting outputs. It also contains a full set of detailed document templates ("checklists") for the documents and records produced by the YaSM processes.</p> | ||
The | <p>The YaSM Process Map is currently available for two platforms, <a href="https://yasm.com/en/products/yasm-process-map-visio" title="The YaSM Process Map for Visio">Microsoft Visio</a><sup><small>®</small></sup> and <a href="https://yasm.com/en/products/yasm-process-map-aris" title="The YaSM Process Map for ARIS">ARIS</a>™. All diagrams and documents are completely editable, which makes the process model the ideal starting point for developing a set of processes tailored to the needs of specific organizations.</p> | ||
< | <p>An additional component (the "<a href="https://yasm.com/en/products/yasm-iso-20000-bridge">YaSM - ISO 20000 Bridge</a>") relates the YaSM processes to the ISO 20000 requirements and specifically addresses the needs of organizations that wish to achieve certification against ISO 20000. It's the perfect companion as you get ready for the ISO 20000 audit.</p> | ||
<p> | <p>For more information on the <a href="https://yasm.com/en/products/yasm-process-map">YaSM Process Map</a> and the <a href="https://yasm.com/en/products/yasm-iso-20000-bridge">ISO 20000 Bridge</a>, please refer to the product pages on the YaSM web site - or explore our <a href="https://yasm.com/en/videos" title="YaSM service management videos and demos">video tutorials about YaSM and the YaSM process model</a>!</html> | ||
<p> | <p> </p> | ||
< | ==<span id="yasm-history">History of YaSM</span>== | ||
<p>& | <html><p>Since 2006 we have been supplying an officially accredited process model for ITIL (the <a href="https://en.it-processmaps.com/products/itil-process-map.html">ITIL® Process Map</a>) to help IT service providers with understanding the principles behind ITIL and designing their ITIL-aligned processes and documents. Our approach to presenting the ITIL concepts in the form of process diagrams has been well received and is used by hundreds of organizations world-wide.</p> | ||
<p>But from countless conversations with our customers it became clear that many find the existing guidance useful in principle, but too complex and difficult to understand. So we decided that, after some 20 or 30 years, it was time for a fresh start with a new, streamlined process model that is easier to understand, has a perfectly clear and pragmatic structure, and is supported by a full set of ready-to-use templates.</p> | |||
<p>What's more, we wanted to offer a model that can be used for business service management/ enterprise service management, as well as ITSM. And that's how the idea for YaSM was born.</p> | |||
<p>We spent two years developing the YaSM model and published the initial version of YaSM 1.0 in 2014: <span id="md-webpage-description" itemprop="description">The YaSM model is a translation of service management 'best practice' into a streamlined, accessible set of processes and ready-to-use templates.</span></html> | |||
The first major update was completed in 2018 to incorporate user feedback and align the [[YaSM Processes|YaSM processes]] with [[ISO 20000 - 2018|the latest edition of ISO 20000:2018]]. | |||
<p> </p> | <p> </p> | ||
Line 124: | Line 129: | ||
<p style="margin-top: 0;"><a href="https://yasm.com/en/blog/why-yasm">Why 'Yet another Service Management Model'?</a></p> | <p style="margin-top: 0;"><a href="https://yasm.com/en/blog/why-yasm">Why 'Yet another Service Management Model'?</a></p> | ||
<p><small>by: Stefan Kempter | July 25, 2014</small></p> | <p><small>by: Stefan Kempter | July 25, 2014</small></p> | ||
<p>This first post marks the launch of YaSM. We are very excited about reaching this big milestone: Getting there meant several years of hard work, but now we are able to present a shiny new service management | <p>This first post marks the launch of YaSM. We are very excited about reaching this big milestone: Getting there meant several years of hard work, but now we are able to present a shiny new service management model with lots of fresh ideas. <a href="https://yasm.com/en/blog/why-yasm">[...]</a></p></div> | ||
<p> </p> | <p> </p> | ||
Line 132: | Line 137: | ||
<p style="margin-top: 0;"><a href="https://yasm.com/en/blog/yasm-wiki-launch">Launch of the free YaSM Wiki</a></p> | <p style="margin-top: 0;"><a href="https://yasm.com/en/blog/yasm-wiki-launch">Launch of the free YaSM Wiki</a></p> | ||
<p><small>by: Stefan Kempter</small></p> | <p><small>by: Stefan Kempter</small></p> | ||
<p>We have been running an ITIL Wiki in three languages for many years and received a lot of positive feedback. So setting up the YaSM Wiki was a natural thing to do once YaSM was ready to be launched. <a href="https://yasm.com/en/blog/yasm-wiki-launch">[...]</a></p></div> | <p>We have been running an ITIL Wiki in three languages for many years and received a lot of positive feedback. So setting up the YaSM Wiki was a natural thing to do once YaSM was ready to be launched. <a href="https://yasm.com/en/blog/yasm-wiki-launch">[...]</a></p></div><p> | ||
</html> | |||
<p> </p> | <p> </p> | ||
== Notes == | == Notes == | ||
<span id="ITIL">[ | <span id="YaSM">[1] YaSM® is a registered trademark of IT Process Maps GbR.</span><br /> | ||
<span id="COBIT">[ | <span id="ITIL">[2] ITIL® is a registered trademark of AXELOS Limited.</span><br /> | ||
<span id="USMBOK">[ | <span id="COBIT">[3] COBIT® is a registered trademark of ISACA.</span><br /> | ||
<span id="CMMI">[ | <span id="USMBOK">[4] USMBOK™ is a registered trade mark of Virtual Knowledge Solutions International Incorporated (VKSII).</span><br /> | ||
<span id="CMMI">[5] CMMI® and Capability Maturity Model® are registered trademarks of Carnegie Mellon University.</span><br /> | |||
<span id="SIAM">[6] SIAM® is a registered trademark of EXIN.</span><br /> | |||
<span id="VeriSM">[7] VeriSM® is a registered trademark of IFDC.</span> | |||
<html>By:  Stefan Kempter <a rel="author" 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="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a 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="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | <html>By:  Stefan Kempter <a rel="author" 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="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a 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="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p> | ||
Line 157: | Line 157: | ||
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | <span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList"> | ||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM# | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#YaSM_isn.27t_about_blindly_following_.27best_practice.27"> | ||
<span itemprop="name">YaSM - the idea</span></a> | <span itemprop="name">YaSM - the idea</span></a> | ||
<meta itemprop="position" content="1" /></span> › | <meta itemprop="position" content="1" /></span> › | ||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM# | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#A_model_for_everyone_in_the_business_of_providing_services"> | ||
<span itemprop="name"> | <span itemprop="name">Model for service provider</span></a> | ||
<meta itemprop="position" content="2" /></span> › | <meta itemprop="position" content="2" /></span> › | ||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM# | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#YaSM_and_ITIL.2C_ISO_20000.2C_SIAM.2C_VeriSM.2C_DevOps.2C_.E2.80.A6"> | ||
<span itemprop="name">YaSM | <span itemprop="name">YaSM and ITIL, ISO 20000, ...</span></a> | ||
<meta itemprop="position" content="3" /></span> › | <meta itemprop="position" content="3" /></span> › | ||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | <span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | ||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm | <a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#YaSM_and_the_YaSM_Process_Map"> | ||
<span itemprop="name">YaSM | <span itemprop="name">YaSM Process Map</span></a> | ||
<meta itemprop="position" content=" | <meta itemprop="position" content="4" /></span> › | ||
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> | |||
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#History_of_YaSM"> | |||
<span itemprop="name">History of YaSM</span></a> | |||
<meta itemprop="position" content="5" /></span> | |||
</span> | </span> | ||
</small></p> | </small></p> |
Revision as of 11:59, 5 July 2018
Why 'Yet another Service Management Model'?
The idea behind YaSM® [1] is not to add yet another service management framework to the many that are already in existence, but to describe a straightforward set of processes that enables organizations to learn by example and bridge the gap between theory and practice.
To this end we assessed the most often used frameworks and standards for service management and ITSM, in particular ITIL® [2], ISO 20000, COBIT® [3], USMBOK™ [4], CMMI-SVC® [5], SIAM™ [6] and VeriSM™ [7], and assimilated the common principles.
The result of this effort - the YaSM model - is streamlined insofar as it has a perfectly clear structure that makes it easy to understand the purpose of each process. For each process, YaSM provides a detailed template, describing the activities to be performed, the required inputs and the resulting outputs, as well as the responsibilities.
If you are new to YaSM service management, start here - in this video Stefan Kempter explains what YaSM is about and what is the best way to get started with YaSM.
Watch the video: "Introduction to YaSM Service Management" [Duration: 7:41 min.]
YaSM isn't about blindly following 'best practice'
The YaSM processes are not prescriptive. YaSM is rather a basis for defining tailor-made processes that work in your organization.
And YaSM doesn't have to be 'implemented' in full. You can start small, concentrating on those process improvements that offer the most benefits.
Giving the YaSM model a clear, easily understood structure was important to us because we wanted to ensure the model can be adopted in a flexible way: In our experience it is almost impossible to simplify a complex system - while starting with something simple and adding more sophistication where needed is relatively easy.
For a first introduction to the YaSM processes, please refer to the overview of "YaSM service management processes" in this Wiki.
A model for everyone in the business of providing services
Service management frameworks (especially ITIL) have until recently been used mainly in the domain of information technology (IT) services, for whom these frameworks were originally created.
As ITIL grew popular, more and more organizations realized that ITIL and service management best practice can be applied to all types of services, such as HR, financial, healthcare, etc. (a trend that is often referred to as "enterprise service management"). So we made a point of ensuring that YaSM is accessible and easy to understand for everyone providing services.
YaSM and ITIL, ISO 20000, SIAM, VeriSM, DevOps, …
Time never stands still, and the service management discipline keeps evolving. ITIL started some 30 years ago with a focus on operating IT infrastructure. Today many service providers are better described as 'service integrators', as their customer-facing services are based on supporting services supplied by third parties. What's more, service management best practice is increasingly applied in other areas outside of the IT organization (see above).
This has led to the emergence of new concepts, each with its own focus:
SIAM, for example, contains guidance specifically for service integration, and VeriSM introduces the 'management mesh' as a management approach from the organizational level. At the same time, service providers discovered that they can greatly benefit from concepts such as Agile, Lean, DevOps, Kanban, etc.
As a result, the service management discipline is now getting more diverse. But its key principles are well established, as enshrined in ISO 20000, the international standard for service management. We have thus ensured the YaSM model is perfectly aligned with ISO 20000.
Everyone versed in ITIL, ISO 20000, SIAM or VeriSM will instantly feel at home, and you can easily extend the YaSM processes with inputs from these frameworks - or indeed with any other concepts and ideas that help you with providing better services.
Please refer to the following wiki pages for more details on how the most popular service management standards and frameworks relate to YaSM:
- Comparison: YaSM vs. ITIL®
- Comparison: YaSM and ISO/IEC 20000
- YaSM and COBIT® (Control Objectives for Information and Related Technologies)
- YaSM and CMMI® for Services (CMMI-SVC)
- YaSM and USMBOK™ (Universal Service Management Body of Knowledge)
YaSM and the YaSM Process Map
The main product in the YaSM product family is the YaSM Process Map: For each process and sub-process, the process model defines in the form of a diagram the activities to be performed, the required inputs and the resulting outputs. It also contains a full set of detailed document templates ("checklists") for the documents and records produced by the YaSM processes.
The YaSM Process Map is currently available for two platforms, Microsoft Visio® and ARIS™. All diagrams and documents are completely editable, which makes the process model the ideal starting point for developing a set of processes tailored to the needs of specific organizations.
An additional component (the "YaSM - ISO 20000 Bridge") relates the YaSM processes to the ISO 20000 requirements and specifically addresses the needs of organizations that wish to achieve certification against ISO 20000. It's the perfect companion as you get ready for the ISO 20000 audit.
For more information on the YaSM Process Map and the ISO 20000 Bridge, please refer to the product pages on the YaSM web site - or explore our video tutorials about YaSM and the YaSM process model!
History of YaSM
Since 2006 we have been supplying an officially accredited process model for ITIL (the ITIL® Process Map) to help IT service providers with understanding the principles behind ITIL and designing their ITIL-aligned processes and documents. Our approach to presenting the ITIL concepts in the form of process diagrams has been well received and is used by hundreds of organizations world-wide.
But from countless conversations with our customers it became clear that many find the existing guidance useful in principle, but too complex and difficult to understand. So we decided that, after some 20 or 30 years, it was time for a fresh start with a new, streamlined process model that is easier to understand, has a perfectly clear and pragmatic structure, and is supported by a full set of ready-to-use templates.
What's more, we wanted to offer a model that can be used for business service management/ enterprise service management, as well as ITSM. And that's how the idea for YaSM was born.
We spent two years developing the YaSM model and published the initial version of YaSM 1.0 in 2014: The YaSM model is a translation of service management 'best practice' into a streamlined, accessible set of processes and ready-to-use templates.
The first major update was completed in 2018 to incorporate user feedback and align the YaSM processes with the latest edition of ISO 20000:2018.
Related articles
Why 'Yet another Service Management Model'?
by: Stefan Kempter | July 25, 2014
This first post marks the launch of YaSM. We are very excited about reaching this big milestone: Getting there meant several years of hard work, but now we are able to present a shiny new service management model with lots of fresh ideas. [...]
by: Stefan Kempter
We have been running an ITIL Wiki in three languages for many years and received a lot of positive feedback. So setting up the YaSM Wiki was a natural thing to do once YaSM was ready to be launched. [...]
Notes
[1] YaSM® is a registered trademark of IT Process Maps GbR.
[2] ITIL® is a registered trademark of AXELOS Limited.
[3] COBIT® is a registered trademark of ISACA.
[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.
[6] SIAM® is a registered trademark of EXIN.
[7] VeriSM® is a registered trademark of IFDC.
By: Stefan Kempter and Andrea Kempter , IT Process Maps.
YaSM - the idea › Model for service provider › YaSM and ITIL, ISO 20000, ... › YaSM Process Map › History of YaSM