VeriSM: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
Line 43: Line 43:
__TOC__
__TOC__


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 is aligned with the key principles of established service management frameworks and standards such as [[YaSM and ITIL|ITIL®]], [[YaSM and COBIT|COBIT®]] 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 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.
Line 110: Line 110:
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.
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]].
In addition, there's a section explaining how VeriSM compares with established service management best practice such as [[YaSM and ITIL|ITIL®]] and [[ISO 20000]].
<p>&nbsp;</p>
<p>&nbsp;</p>


Line 147: Line 147:
*and [[VeriSM_and_YaSM#VeriSM_stage_4:_Respond|Respond]].  
*and [[VeriSM_and_YaSM#VeriSM_stage_4:_Respond|Respond]].  
This concept is in line with the time-tested [[YaSM_Processes#Service_lifecycle_processes|service lifecycle approach]] known from other service management frameworks and standards such as ITIL&reg;, COBIT&reg;, CMMI-SVC&reg; and ISO 20000.
This concept is in line with the time-tested [[YaSM_Processes#Service_lifecycle_processes|service lifecycle approach]] known from other service management frameworks and standards such as [[YaSM and ITIL|ITIL&reg;]], [[YaSM and COBIT|COBIT&reg;]], [[YaSM and CMMI for Services (CMMI-SVC)|CMMI-SVC&reg;]] and [[ISO 20000]].


For each stage, VeriSM describes  
For each stage, VeriSM describes  
Line 164: Line 164:
==Progressive practices and emerging technologies==
==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&reg;, Lean, and others.
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 [[YaSM and Agile Service Management|Agile]], [[DevOps and YaSM|DevOps]], [[SIAM|SIAM&reg;]], [[YaSM and Lean Service Management|Lean]], and others.


VeriSM encourages organizations to explore various practices, and to adopt whatever methods help them serve their customers better.
VeriSM encourages organizations to explore various practices, and to adopt whatever methods help them serve their customers better.
Line 179: Line 179:
<span id="COBIT">[3] COBIT&reg; is a registered trademark of ISACA.</span><br />
<span id="COBIT">[3] COBIT&reg; is a registered trademark of ISACA.</span><br />
<span id="ISO20000">[4] ISO/IEC 20000&reg; is a registered trademark of ISO.</span><br />
<span id="ISO20000">[4] ISO/IEC 20000&reg; is a registered trademark of ISO.</span><br />
<p>&nbsp;</p>


<html>By:&#160;&#160;Stefan Kempter&#160;<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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<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.
<html>By:&#160;&#160;Stefan Kempter&#160;<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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<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.

Revision as of 16:41, 29 September 2018

share this page on LinkedInshare this page on Twittershare this page
auf Deutsch


What is VeriSM?


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'.

 

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', due to be released in Q4 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. These certifications are expected to be available in the second half of 2018.

Since VeriSM is not an official standard, there are no certifications for bussinesses 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.

 

References

[1] IFDC (International Foundation for Digital Competences) (2017). 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   and  Andrea Kempter Contributor: Andrea Kempter, IT Process Maps GbR, IT Process Maps.

 

What is VeriSM?  › History  › Certification path  › VeriSM model  › Management mesh