VeriSM: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 5: Line 5:
<meta property="og:title" content="What is VeriSM™? | YaSM Service Management Wiki" />
<meta property="og:title" content="What is VeriSM™? | YaSM Service Management Wiki" />
<meta property="og:description" content="Introduction to the VeriSM approach and the 'VeriSM management mesh'. VeriSM stands for 'Value-driven Evolving Responsive Integrated Service Management'." />
<meta property="og:description" content="Introduction to the VeriSM approach and the 'VeriSM management mesh'. VeriSM stands for 'Value-driven Evolving Responsive Integrated Service Management'." />
<meta property="og:site_name" content="YaSM">
<meta property="og:site_name" content="YaSM Service Management">
<meta property="og:type" content="article" />
<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/verism/16x9/what-is-verism.jpg" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/16x9/what-is-verism.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="675" />
<meta property="og:image:height" content="675" />
<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="What is VeriSM™?">
<meta name="twitter:description" content="Introduction to the VeriSM model and the 'VeriSM service management mesh'.">
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/16x9/what-is-verism.jpg">
<meta name="twitter:image:alt" content="Introduction to the VeriSM™ approach and the 'VeriSM management mesh'. VeriSM stands for 'Value-driven Evolving Responsive Integrated Service Management'.">
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
<meta name="pinterest-rich-pin" content="false" />
<meta name="pinterest-rich-pin" content="false" />
</itpmch>
</itpmch>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/VeriSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/></html>
<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/VeriSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/></html>
<p>&nbsp;</p>


===What is VeriSM?===
<span id="md-webpage-description" itemprop="description"><b><span style="color:#465674;">VeriSM&trade;</span></b> is a 'service management approach from the organizational level, looking at the end to end view rather than focusing on a single department' [[#IFDC-2017|[1]]]. The acronym VeriSM stands for '<b><span style="color:#465674;">Value-driven, Evolving, Responsive, Integrated, Service Management</span></b>'.</span>
----


<html><span id="md-webpage-description" itemprop="description">VeriSM&trade; is a <i>'service management approach from the organizational level, looking at the end to end view rather than focusing on a single department'</i> <a href="#IFDC-2017" title="IFDC, 2017: A Service Management Approach for the Digital Age">[1]</a>.<br/><br/>The acronym VeriSM stands for 'Value-driven, Evolving, Responsive, Integrated, Service Management'.</span></p>
<html><div style="float:right; margin-top:2em;"><div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" itemscope itemtype="https://schema.org/ImageObject">
 
<div id="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" title="What is VeriSM?" itemprop="contentUrl">
<meta itemprop="caption" content="What is VeriSM and the 'VeriSM service management mesh'?" />
<meta itemprop="caption" content="What is VeriSM and the 'VeriSM service management mesh'?" />
<meta itemprop="width" content="1200" />
<meta itemprop="width" content="1200" />
Line 37: Line 24:
<meta itemprop="dateCreated" content="2018-07-27" />
<meta itemprop="dateCreated" content="2018-07-27" />
<meta itemprop="datePublished" content="2018-07-27" />
<meta itemprop="datePublished" content="2018-07-27" />
<meta itemprop="dateModified" content="2022-07-09" />
<meta itemprop="representativeOfPage" content="true"/>
<meta itemprop="representativeOfPage" content="true"/>
<meta itemprop="keywords" content="What is VeriSM?" />
<meta itemprop="keywords" content="What is VeriSM?" />
Line 46: Line 34:
   <meta itemprop="dateCreated" content="2019-06-24" />
   <meta itemprop="dateCreated" content="2019-06-24" />
   <meta itemprop="datePublished" content="2019-06-24" />
   <meta itemprop="datePublished" content="2019-06-24" />
  <meta itemprop="dateModified" content="2022-07-09" />
</span>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/480px/what-is-verism.jpg" />
  <meta itemprop="width" content="480" />
  <meta itemprop="height" content="360" />
  <meta itemprop="dateCreated" content="2022-07-09" />
  <meta itemprop="datePublished" content="2022-08-12" />
</span>
<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/480px/what-is-verism.jpg" />
  <meta itemprop="width" content="400" />
  <meta itemprop="height" content="300" />
  <meta itemprop="dateCreated" content="2024-03-29" />
  <meta itemprop="datePublished" content="2024-04-03" />
</span>  
</span>  
<img style="margin:20px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" width="480" height="360" title="What is VeriSM?" alt="Introduction to the VeriSM model and the 'VeriSM service management mesh'." /></a></div></html>
<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl" href="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" title="What is VeriSM?"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/verism/400px/what-is-verism.jpg 400w, https://yasm.com/wiki/en/img/yasm-frameworks/verism/480px/what-is-verism.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" fetchpriority="high" decoding="async" width="480" height="360" class="mw-file-element" alt="Introduction to the VeriSM model and the 'VeriSM service management mesh'." /></a><figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/verism/what-is-verism.jpg" title="What is VeriSM?">What is VeriSM?</a></b><br />Introduction to VeriSM and the 'VeriSM Service Management Mesh'.</span></figcaption></figure></div></html>


<p>&nbsp;</p>
__TOC__
<br style="clear:both;"/>


__TOC__
==Overview==
<p>&nbsp;</p>


VeriSM is aligned with the key principles of established service management frameworks and standards such as [[YaSM and ITIL|ITIL&reg;]], [[YaSM and COBIT|COBIT&reg;]] and [[ISO 20000|ISO 20000]], but does not seek to replace them. Instead VeriSM aims to provide the 'glue' to bring the different practices together, so organizations can adopt them in a flexible way. These practices may include the traditional ITSM methodologies and also 'progressive practices' like [[DevOps and YaSM|DevOps]], [[YaSM and Agile Service Management|Agile]], [[YaSM_and_Agile_Service_Management#Kanban|Scrum]], Lean, [[YaSM_and_Agile_Service_Management#Kanban|Kanban]], etc. that are increasingly applied in the service management domain.
VeriSM is aligned with the key principles of established service management frameworks and standards such as [[YaSM and ITIL|ITIL&reg;]], [[YaSM and COBIT|COBIT&reg;]] and [[ISO 20000|ISO 20000]], but does not seek to replace them. Instead VeriSM aims to provide the 'glue' to bring the different practices together, so organizations can adopt them in a flexible way. These practices may include the traditional ITSM methodologies and also 'progressive practices' like [[DevOps and YaSM|DevOps]], [[YaSM and Agile Service Management|Agile]], [[YaSM_and_Agile_Service_Management#Kanban|Scrum]], Lean, [[YaSM_and_Agile_Service_Management#Kanban|Kanban]], etc. that are increasingly applied in the service management domain.


VeriSM also recognizes that service management is no longer just for IT, since the delivery of services to customers tends to involve many parts of the organization, such as finance, marketing, manufacturing, sales, legal, logistics etc.
VeriSM also recognizes that [[Service Management|service management]] is no longer just for IT, since the delivery of services to customers tends to involve many parts of the organization, such as finance, marketing, manufacturing, sales, legal, logistics etc.


==How was VeriSM created?==
==How was VeriSM created?==
Line 173: Line 176:
==Related articles==
==Related articles==


<html><a href="https://yasm.com/wiki/en/index.php/VeriSM_and_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-frameworks/verism/16x9/verism-service-management-process-templates-yasm.jpg" title="VeriSM vs. YaSM service management" alt="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects." style="display: block; float: left; border:1px solid #d9d9d9; margin-left: 10px; margin-right: 20px" width="320" height="180"/></a>
<html><figure class="mw-halign-left" typeof="mw:File/Thumb"><a href="https://yasm.com/wiki/en/index.php/VeriSM_and_YaSM" title="VeriSM vs. YaSM service management"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/verism/400px/verism-service-management-process-templates-yasm.jpg 400w, https://yasm.com/wiki/en/img/yasm-frameworks/verism/480px/verism-service-management-process-templates-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/verism/400px/verism-service-management-process-templates-yasm.jpg" decoding="async" width="400" height="300" class="mw-file-element" alt="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects." /></a><figcaption><span style="font-variant:small-caps;">Comparison: VeriSM and YaSM service management</span></figcaption></figure>
<div style="margin-left: 5%; color:#636363">
<p><a href="https://yasm.com/wiki/en/index.php/VeriSM_and_YaSM" title="Comparison: VeriSM and YaSM service management">Comparison: VeriSM and YaSM service management</a></p>
<p style="margin-top: 20px;"><a href="https://yasm.com/wiki/en/index.php/VeriSM_and_YaSM">Comparison: VeriSM and YaSM service management</a></p>
<p>Both YaSM&reg; and VeriSM&trade; are aligned with established service management best practice as described in ISO 20000, ITIL&reg;, CMMI-SVC&reg;, COBIT&reg;, etc. But they are not the same: <br /><a href="https://yasm.com/wiki/en/index.php/VeriSM_and_YaSM" title="Comparison: VeriSM and YaSM service management">[&nbsp;...&nbsp;Read more&nbsp;]</a></p></html>
<p>Both YaSM<sup><small>&#174;</small></sup> and VeriSM&trade; are aligned with established service management best practice as described in ISO 20000, ITIL<sup><small>&#174;</small></sup>, CMMI-SVC<sup><small>&#174;</small></sup>, COBIT<sup><small>&#174;</small></sup>, etc. But they are not the same: <a href="https://yasm.com/wiki/en/index.php/VeriSM_and_YaSM">[...]</a></p></div></html>
 
<p style="clear:both;">&nbsp;</p>
<p style="clear:both;">&nbsp;</p>


Line 195: Line 196:
<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/VeriSM#What_is_VeriSM.3F"> <span itemprop="name">What is VeriSM?</span></a>
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/VeriSM#Overview"> <span itemprop="name">Overview</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/VeriSM#How_was_VeriSM_created.3F"> <span itemprop="name">History</span></a>
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/VeriSM#How_was_VeriSM_created.3F"> <span itemprop="name">How was VeriSM created?</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">
Line 207: Line 208:
<meta itemprop="position" content="4" /></span> ›
<meta itemprop="position" content="4" /></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/VeriSM#VeriSM_management_mesh"> <span itemprop="name">Management mesh</span></a>
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/VeriSM#VeriSM_management_mesh"> <span itemprop="name">VeriSM management mesh</span></a>
<meta itemprop="position" content="5" /></span>
<meta itemprop="position" content="5" /></span>
</span>
</span>

Latest revision as of 14:18, 15 September 2024

auf Deutsch


 

VeriSM™ is a 'service management approach from the organizational level, looking at the end to end view rather than focusing on a single department' [1]. The acronym VeriSM stands for 'Value-driven, Evolving, Responsive, Integrated, Service Management'.

Introduction to the VeriSM model and the 'VeriSM service management mesh'.
Fig. 1: What is VeriSM?
Introduction to VeriSM and the 'VeriSM Service Management Mesh'.


Overview

VeriSM is aligned with the key principles of established service management frameworks and standards such as ITIL®, COBIT® and ISO 20000, but does not seek to replace them. Instead VeriSM aims to provide the 'glue' to bring the different practices together, so organizations can adopt them in a flexible way. These practices may include the traditional ITSM methodologies and also 'progressive practices' like DevOps, Agile, Scrum, Lean, Kanban, etc. that are increasingly applied in the service management domain.

VeriSM also recognizes that service management is no longer just for IT, since the delivery of services to customers tends to involve many parts of the organization, such as finance, marketing, manufacturing, sales, legal, logistics etc.

How was VeriSM created?

VeriSM service management was launched in 2017 by IFDC (International Foundation for Digital Competencies, a foundation based in the Netherlands). IFDC is a nonprofit organization whose members include several businesses, such as the examination institutes APMG, BCS and EXIN that offer VeriSM certifications. Also among IFDC's members are Van Haren Publishing, the Open Group and itSMF International.

The first official VeriSM publication ('VeriSM™ - A service management approach for the digital age' [IFD, 2017]) has been created by an international team of experts from the IT service management community. The VeriSM book was published in December 2017.

While the first publication explains the concepts behind VeriSM, the second book ('VeriSM™ Professional', released in December 2018) is focused on how to apply the VeriSM approach in the real world.

What's the VeriSM certification path?

The VeriSM certification scheme provides a modular approach and is comprised of a series of qualifications.

The Foundation exam is the entry level certification and consists of two parts: VeriSM Essentials and VeriSM Plus. VeriSM Foundation level exams have been available since January 2018.

VeriSM Professional and VeriSM Leader are open to those who have passed the Foundation exam. The VeriSM Professional certification has been available since October 2018 and VeriSM Leader is under development.

Since VeriSM is not an official standard, there are no certifications for businesses and other organizations. Service providers that wish to demonstrate excellence and good governance in service management may choose to get certified against ISO 20000.

What guidance is contained in VeriSM?

The main VeriSM publication [IFDC, 2017] is divided into three parts:

Services and service management

The first part of VeriSM introduces essential concepts around services and service management.

Part 1 starts with definitions of service management key terms, such as organization, consumer, asset, capability, outcome, service culture, etc.

This is followed by a section discussing the impact of digital transformation on service providers and services. New business models and advanced technologies mean increased competitive challenges for service providers, but also opportunities to gain a competitive edge. Technology is often at the heart of these new business models and permeates every part of the organization, which leads to the recognition that service management has to be an organizational capability, not an IT capability.

Service providers also need people with the right skills. VeriSM highlights what is necessary for organizations in terms of competencies and teams, touching on topics such as generic competencies, emotional intelligence, ethics, team building and learning paths.

Finally, VeriSM discusses common service provider challenges, such as relation management, communication, and organizational change management.

The VeriSM model

The VeriSM model is introduced as an 'operating model' for service provider organizations that consists of the following key areas:

Governance and service management principles

According to VeriSM, governance is a system by which organizations are directed and controlled. Organizations are advised to establish a governance framework that includes, among others, principles, policies, processes, plans and metrics.

Principles are typically drawn up for several areas such as security, risk, quality, etc., and then communicated to all staff who are involved in the development and operation of products and services.

Once the organizational principles are set, policies, processes, plans and metrics should be defined to translate the principles into detailed guidance.

VeriSM, however, does not prescribe specific principles, policies, etc., nor does it give advice about their content. Instead, readers will find summary information of what good governance means for service provider organizations.

In addition, there's a section explaining how VeriSM compares with established service management best practice such as ITIL® and ISO 20000.

Consumer

Service providers cannot do business without an understanding of customer requirements. This is why VeriSM starts with the consumer, who provides the requirements for the services to be delivered.

Consumers are also at the end of the VeriSM model, where they receive services and provide feedback.

In this context, VeriSM describes the relationship with the customer as a critical aspect, and provides some recommendations for the gathering of service requirements.

VeriSM management mesh

VeriSM introduces the management mesh as a concept providing the flexibility to manage and use various frameworks, standards, methodologies, management principles, philosophies, etc.

The management mesh can be adapted as necessary for a particular product or service; it includes

  • the resources,
  • environment,
  • tools,
  • processes,
  • technologies
  • and management practices used in the organization.

VeriSM, however, presents the management mesh as a somewhat vague concept and, for the most part, outlines what are the typical ingredients of the mesh.

Building the mesh essentially means selecting the right resources, processes, technologies, management practices etc., in line with the requirements of the organization and the services offered.

VeriSM stages of service development and provision

VeriSM defines four 'high-level stages' for services:

This concept is in line with the time-tested service lifecycle approach known from other service management frameworks and standards such as ITIL®, COBIT®, CMMI-SVC® and ISO 20000.

For each stage, VeriSM describes

  • its purpose,
  • the aspects to be considered,
  • the typical high-level activities
  • as well as the key inputs and outputs.

To bring the stage concept to life, organizations are advised to apply their (unique) management mesh and define tailor-made processes for each stage, as required.

See also:

Progressive practices and emerging technologies

The last part of VeriSM presents a selection of 'progressive management practices' and emerging technologies that often have their roots in other areas such as manufacturing and software development, and are increasingly applied in the field of service management. The practices covered include Agile, DevOps, SIAM™, Lean, and others.

VeriSM encourages organizations to explore various practices, and to adopt whatever methods help them serve their customers better.

Each of these practices is a substantial area of knowledge in its own right, so VeriSM can only provide summary information. But readers are offered a good overview of currently popular practices, and for each of them VeriSM explains how they can be applied in the service management domain.

Related articles

Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects.
Comparison: VeriSM and YaSM service management

Comparison: VeriSM and YaSM service management

Both YaSM® and VeriSM™ are aligned with established service management best practice as described in ISO 20000, ITIL®, CMMI-SVC®, COBIT®, etc. But they are not the same:
[ ... Read more ]

 

References

[1] IFDC (International Foundation for Digital Competences) (2017). VeriSM™ - A Service Management Approach for the Digital Age. Zaltbommel, Niederlande: Van Haren Publishing.

Notes

[1] VeriSM™ is a registered trademark of IFDC.
[2] ITIL® is a registered trademark of AXELOS Limited.
[3] COBIT® is a registered trademark of ISACA.
[4] ISO/IEC 20000® is a registered trademark of ISO.

By:  Stefan Kempter Author: Stefan Kempter, IT Process Maps GbR  and  Andrea Kempter Contributor: Andrea Kempter, IT Process Maps GbR, IT Process Maps.

 

Overview  › How was VeriSM created?  › Certification path  › VeriSM model  › VeriSM management mesh