VeriSM and YaSM - Revision history

Andrea at 14:18, 15 September 2024

2024-09-15T14:18:12Z

Andrea at 15:22, 3 April 2024

2024-04-03T15:22:24Z

← Older revision		Revision as of 17:22, 3 April 2024
Line 17:		Line 17:
	<p><b>Comparison:</b> YaSM and VeriSM™</p>		<p><b>Comparison:</b> YaSM and VeriSM™</p>
	<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></html>		<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></html>
			<p> </p>

	Both ~~[[What is YaSM\|YaSM]]~~<~~sup~~><~~small~~>&~~#174~~;</~~small~~></~~sup~~> ~~and [[VeriSM]]™ [[#VeriSM\|[1]]]~~ are aligned with established service management best practice as described in [[ISO 20000]], [[ITIL]]<sup><small>®</small></sup>, [[YaSM_and_CMMI_for_Services_-_CMMI-SVC\|CMMI-SVC]]<sup><small>®</small></sup>, [[YaSM_and_COBIT\|COBIT]]<sup><small>®</small></sup>, etc. But they are not the same:		Both <b><span style="color:#465674;">YaSM and VeriSM™</span></b> are aligned with established service management best practice as described in [[ISO 20000]], [[ITIL]]<sup><small>®</small></sup>, [[YaSM_and_CMMI_for_Services_-_CMMI-SVC\|CMMI-SVC]]<sup><small>®</small></sup>, [[YaSM_and_COBIT\|COBIT]]<sup><small>®</small></sup>, etc. But they are not the same:

	<span id="md-webpage-description" itemprop="description">While VeriSM outlines an approach for managing services, [[What_is_YaSM\|YaSM]] is a concise and detailed process model with ready-to-use templates for [[Service Management\|service management]].</span>		<span id="md-webpage-description" itemprop="description">While [[VeriSM]]™ [[#VeriSM\|[1]]] outlines an approach for managing services, [[What_is_YaSM\|YaSM]]<sup><small>®</small></sup> is a concise and detailed process model with ready-to-use templates for [[Service Management\|service management]].</span>

	<html><div style="float:right; margin-top:2em;"><div id="https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">		<html><div style="float:right; margin-top:2em;"><div id="https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">
Line 49:		Line 50:
	<meta itemprop="datePublished" content="2022-08-12" />		<meta itemprop="datePublished" content="2022-08-12" />
	</span>		</span>
	<img itemprop="contentUrl" style="margin:0px 0px 15px 20px; float:right;" srcset="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/verism-service-management-process-templates-yasm.jpg" width="480" height="360" title="VeriSM vs. YaSM service management" alt="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects." /></a><br style="clear:both;"/>		<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
	<div class="thumbcaption" style="margin:0px ~~0px 20px~~ 20px"><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg" title="VeriSM vs. YaSM service management">VeriSM and YaSM service management</a></b></span><br />Process templates and diagrams for VeriSM projects.</div></div></div></html>		<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/400px/verism-service-management-process-templates-yasm.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>
			<img itemprop="contentUrl" style="margin:0px 0px 15px 20px; float:right;" 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/verism-service-management-process-templates-yasm.jpg" fetchpriority="high" decoding="async" width="480" height="360" title="VeriSM vs. YaSM service management" alt="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects." /></a><br style="clear:both;"/>
			<div class="thumbcaption" style="margin:5px 0px 10px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg" title="VeriSM vs. YaSM service management">VeriSM and YaSM service management</a></b></span><br />Process templates and diagrams for VeriSM projects.</div></div></div></html>
	<p> </p>		<p> </p>

Line 58:		Line 66:
	==What is the difference between YaSM and VeriSM?==		==What is the difference between YaSM and VeriSM?==

	~~<i>~~VeriSM~~</i>~~ helps service providers understand the challenges and key principles of service management. It shows organizations how they can adopt a range of management practices to deliver the right service at the right time to their users.		[[VeriSM]] helps service providers understand the challenges and key principles of service management. It shows organizations how they can adopt a range of management practices to deliver the right [[Service\|service]] at the right time to their users.

	VeriSM thus presents a high-level description of how services are defined, produced and provided, without being prescriptive about the low-level activities. Yet at some point, organizations need to go into detail and define their service management processes.		VeriSM thus presents a high-level description of how services are defined, produced and provided, without being prescriptive about the low-level activities. Yet at some point, organizations need to go into detail and define their service management processes.
Line 294:		Line 302:
	===YaSM documents and templates supporting the VeriSM Respond stage===		===YaSM documents and templates supporting the VeriSM Respond stage===
	The YaSM model provides several templates and checklists for the documents and records supporting the VeriSM Respond stage, for example:		The YaSM model provides several templates and checklists for the documents and records supporting the VeriSM Respond stage, for example:
	*Incident Record ~~<i>~~(see also: [[Incident Record - Template\|free Incident record ~~checklist~~]] in this wiki)~~</i>~~		*Incident Record (see also: [[Incident Record - Template\|free Incident record template]] in this wiki)
	*Incident model		*Incident model
	*Service request record		*Service request record
Line 347:		Line 355:
	<p> </p>		<p> </p>

	<html><a href="https://yasm.com/wiki/en/index.php/VeriSM"><img ~~src~~="https://yasm.com/wiki/en/img/yasm-frameworks/verism/480px/what-is-verism.jpg" title="What is VeriSM?" alt="What is VeriSM and the 'VeriSM service management mesh'?" ~~class~~="~~thumbimage~~" ~~style~~="~~display: block; float: left; border:1px solid #d9d9d9; margin-right: 15px~~" ~~width~~="~~320~~" ~~height~~="~~240~~"/></a>		<html><a href="https://yasm.com/wiki/en/index.php/VeriSM"><img style="display: block; float: left; margin-bottom: 10px; margin-right: 10px" 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" title="What is VeriSM?" alt="What is VeriSM and the 'VeriSM service management mesh'?" decoding="async" width="400" height="300" class="thumbimage"/></a>
	~~<div style="margin-left: 5%; color:#636363"~~>		<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/VeriSM">What is VeriSM™ - 'Value-driven, Evolving, Responsive, Integrated, Service Management'?</a></p>
	<p style="margin-top: 0; word-wrap:normal;"><a href="https://yasm.com/wiki/en/index.php/VeriSM">What is VeriSM™?</a></p>		<p>A short introduction to the VeriSM service management approach: <a href="https://yasm.com/wiki/en/index.php/VeriSM">[...]</a></p></html>
	<p>A short introduction to the VeriSM service management approach: <a href="https://yasm.com/wiki/en/index.php/VeriSM">[...]</a></p~~></div~~></html>
	<p style="clear:both;"> </p>		<p style="clear:both;"> </p>

Andrea at 16:04, 30 December 2023

2023-12-30T16:04:34Z

← Older revision		Revision as of 18:04, 30 December 2023
Line 6:		Line 6:
	<meta property="og:description" content="While VeriSM outlines an approach for managing services, YaSM is a concise and detailed process model with ready-to-use templates for service management." />		<meta property="og:description" content="While VeriSM outlines an approach for managing services, YaSM is a concise and detailed process model with ready-to-use templates for service management." />
	<meta property="og:site_name" content="YaSM Service Management">		<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/verism-service-management-process-templates-yasm.jpg" />		<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/16x9/verism-service-management-process-templates-yasm.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="VeriSM™ and YaSM">~~
	~~<meta name="twitter:description" content="While VeriSM outlines an approach for managing services, YaSM is a concise, detailed process model with ready-to-use templates for service management.">~~
	~~<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/verism/16x9/verism-service-management-process-templates-yasm.jpg">~~
	~~<meta name="twitter:image:alt" content="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and process diagrams for VeriSM projects.">~~
	<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" />

Stefan: Renamed process: SP8: Ensure continuity

2023-11-12T14:57:29Z

Renamed process: SP8: Ensure continuity

← Older revision		Revision as of 16:57, 12 November 2023
Line 138:		Line 138:
	*[[SP3: Manage customer relationships]]		*[[SP3: Manage customer relationships]]
	*[[SP7: Ensure security]]		*[[SP7: Ensure security]]
	*[[SP8: ~~Prepare for disaster events~~]]		*[[SP8: Ensure continuity]]
	\|-style="vertical-align:top"		\|-style="vertical-align:top"
	\|[[#VeriSM_stage_4:_Respond\|4 Respond]]		\|[[#VeriSM_stage_4:_Respond\|4 Respond]]
Line 176:		Line 176:
	*[[SP3: Manage customer relationships]]		*[[SP3: Manage customer relationships]]
	*[[SP7: Ensure security]]		*[[SP7: Ensure security]]
	*[[SP8: ~~Prepare for disaster events~~]]		*[[SP8: Ensure continuity]]
	*[[SP9: Ensure compliance]]		*[[SP9: Ensure compliance]]

Line 186:		Line 186:
	*Service implementation blueprint		*Service implementation blueprint
	*Register of security risks		*Register of security risks
	*Register of managed ~~disaster~~ events		*Register of managed critical events
	*Compliance register		*Compliance register

Line 245:		Line 245:
	In addition, the [[LP5: Improve the services\|service improvement process]] collects information about service quality, determines potentials for improvement, and takes corrective action if necessary.		In addition, the [[LP5: Improve the services\|service improvement process]] collects information about service quality, determines potentials for improvement, and takes corrective action if necessary.

	Security needs and service continuity requirements are addressed in the YaSM processes for [[SP7: Ensure security\|service security]] and [[SP8: ~~Prepare for disaster events~~\|continuity]].		Security needs and service continuity requirements are addressed in the YaSM processes for [[SP7: Ensure security\|service security]] and [[SP8: Ensure continuity\|continuity]].

	Marketing activities are mostly performed in the YaSM process for [[SP3: Manage customer relationships\|managing customer relationships]], which is responsible for acquiring new customers and establishing a mutually beneficial relationship with existing customers.		Marketing activities are mostly performed in the YaSM process for [[SP3: Manage customer relationships\|managing customer relationships]], which is responsible for acquiring new customers and establishing a mutually beneficial relationship with existing customers.
Line 264:		Line 264:
	*[[SP3: Manage customer relationships]]		*[[SP3: Manage customer relationships]]
	*[[SP7: Ensure security]]		*[[SP7: Ensure security]]
	*[[SP8: ~~Prepare for disaster events~~]]		*[[SP8: Ensure continuity]]

	===YaSM documents and templates supporting the VeriSM Provide stage===		===YaSM documents and templates supporting the VeriSM Provide stage===
Line 277:		Line 277:
	*Customer portfolio		*Customer portfolio
	*Register of security risks		*Register of security risks
	*Register of managed ~~disaster~~ events		*Register of managed critical events

	==VeriSM stage 4: Respond==		==VeriSM stage 4: Respond==

Andrea at 11:52, 30 September 2023

2023-09-30T11:52:55Z

Show changes

Andrea at 13:32, 12 August 2022

2022-08-12T13:32:11Z

Show changes

Andrea at 15:53, 24 June 2019

2019-06-24T15:53:52Z

Show changes

Andrea at 17:47, 28 March 2019

2019-03-28T17:47:32Z

← Older revision		Revision as of 19:47, 28 March 2019
Line 368:		Line 368:
	<p> </p>		<p> </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.		<html>By:  Stefan Kempter <a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter \| Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter \| Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.
	<p> </p>		<p> </p>

Andrea at 10:18, 11 October 2018

2018-10-11T10:18:33Z

← Older revision		Revision as of 12:18, 11 October 2018
Line 56:		Line 56:
	<p> </p>		<p> </p>

	<i>YaSM</i> describes a complete set of [[~~YaSM~~ Processes\|service management processes]], including their activities, responsibilities, inputs and outputs, and it provides ready-to-use process and document templates.		<i>YaSM</i> describes a complete set of [[Service Management Processes\|service management processes]], including their activities, responsibilities, inputs and outputs, and it provides ready-to-use process and document templates.

	<html>These <a href="https://yasm.com/en/products/yasm-process-map" title="Service management process templates - the YaSM Process Map">service management templates</a> are available in popular formats such as <a href="https://yasm.com/en/products/yasm-process-map-visio" title="Service management process templates for Visio">Visio</a><sup><small>®</small></sup>, Word<sup><small>®</small></sup>, Excel<sup><small>®</small></sup>, and the <a href="https://yasm.com/en/products/yasm-process-map-aris" title="Service management reference model for ARIS">ARIS Process Platform</a>™ and are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</html>		<html>These <a href="https://yasm.com/en/products/yasm-process-map" title="Service management process templates - the YaSM Process Map">service management templates</a> are available in popular formats such as <a href="https://yasm.com/en/products/yasm-process-map-visio" title="Service management process templates for Visio">Visio</a><sup><small>®</small></sup>, Word<sup><small>®</small></sup>, Excel<sup><small>®</small></sup>, and the <a href="https://yasm.com/en/products/yasm-process-map-aris" title="Service management reference model for ARIS">ARIS Process Platform</a>™ and are fully editable, allowing organizations to design tailor-made processes without having to start from nothing.</html>
Line 85:		Line 85:
	VeriSM describes <i>'high-level stages'</i> for products and services: Define, Produce, Provide and Respond.		VeriSM describes <i>'high-level stages'</i> for products and services: Define, Produce, Provide and Respond.

	These stages largely correspond to the [[~~YaSM_Processes~~#Service_lifecycle_processes\|service lifecycle]] that is the guiding principle of the YaSM process model, so the VeriSM stages are one area where VeriSM and YaSM are particularly well aligned.		These stages largely correspond to the [[Service_Management_Processes#Service_lifecycle_processes\|service lifecycle]] that is the guiding principle of the YaSM process model, so the VeriSM stages are one area where VeriSM and YaSM are particularly well aligned.
	<p> </p>		<p> </p>

	The table below provides a first overview of the VeriSM 'high-level stages' and how they are associated with the [[~~YaSM~~ Processes\|YaSM processes]].		The table below provides a first overview of the VeriSM 'high-level stages' and how they are associated with the [[Service Management Processes\|YaSM processes]].

	The subsequent sections will then outline in detail how the YaSM processes, documents and templates are aligned with the VeriSM stages, and how YaSM provides detailed guidance for organizations that wish to adopt the VeriSM approach.		The subsequent sections will then outline in detail how the YaSM processes, documents and templates are aligned with the VeriSM stages, and how YaSM provides detailed guidance for organizations that wish to adopt the VeriSM approach.
Line 128:		Line 128:
	<p> </p>		<p> </p>

	The subsequent sections will then outline in detail how the [[~~YaSM~~ Processes\|YaSM processes]], documents and templates are aligned with the VeriSM stages, and how YaSM provides detailed guidance for organizations that wish to adopt the VeriSM approach.		The subsequent sections will then outline in detail how the [[Service Management Processes\|YaSM processes]], documents and templates are aligned with the VeriSM stages, and how YaSM provides detailed guidance for organizations that wish to adopt the VeriSM approach.
	<p> </p>		<p> </p>

Line 392:		Line 392:
	<link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" />		<link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" />
	<meta itemprop="significantLinks" content="https://yasm.com/en/products/yasm-process-map" />		<meta itemprop="significantLinks" content="https://yasm.com/en/products/yasm-process-map" />
	<meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/~~YaSM_Processes~~" />		<meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/Service_Management_Processes" />
	<meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" />		<meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" />
	<meta itemprop="inLanguage" content="en" />		<meta itemprop="inLanguage" content="en" />

Andrea at 15:58, 29 September 2018

2018-09-29T15:58:58Z

← Older revision		Revision as of 17:58, 29 September 2018
Line 40:		Line 40:
	<img style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg" width="480" height="360" title="VeriSM vs. YaSM service management" alt="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects." /></a></div>		<img style="margin:5px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/verism/verism-service-management-process-templates-yasm.jpg" width="480" height="360" title="VeriSM vs. YaSM service management" alt="Comparison: VeriSM and YaSM service management. Ready-to-use process templates and diagrams for VeriSM projects." /></a></div>

	<p>Both YaSM<sup><small>®</small></sup> and <a href="https://yasm.com/wiki/en/index.php/VeriSM" title="What is VeriSM?">VeriSM™</a> <a href="#VeriSM">[1]</a> are aligned with established service management best practice as described in ISO 20000, ITIL<sup><small>®</small></sup>, CMMI-SVC<sup><small>®</small></sup>, COBIT<sup><small>®</small></sup>, etc. But they are not the same:</p>		<p>Both YaSM<sup><small>®</small></sup> and <a href="https://yasm.com/wiki/en/index.php/VeriSM" title="What is VeriSM?">VeriSM™</a> <a href="#VeriSM">[1]</a> are aligned with established service management best practice as described in <a href="https://yasm.com/wiki/en/index.php/ISO_20000" title="What is ISO 20000?">ISO 20000</a>, <a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" title="YaSM and ITIL">ITIL</a><sup><small>®</small></sup>, CMMI-SVC<sup><small>®</small></sup>, COBIT<sup><small>®</small></sup>, etc. But they are not the same:</p>

	<p><span id="md-webpage-description" itemprop="description">While VeriSM outlines an approach for managing services, YaSM is a concise and detailed process model with ready-to-use templates for service management.</span></html>		<p><span id="md-webpage-description" itemprop="description">While VeriSM outlines an approach for managing services, YaSM is a concise and detailed process model with ready-to-use templates for service management.</span></html>
Line 317:		Line 317:
	The Management Mesh allows for flexibility, so organizations are able to pick from a variety of management practices, technologies etc., as required.		The Management Mesh allows for flexibility, so organizations are able to pick from a variety of management practices, technologies etc., as required.

	<html>The YaSM model helps organizations that wish to include established service management best practice into their Management Mesh, by providing <a href="https://yasm.com/en/products/yasm-process-map" title="Service management process templates - the YaSM Process Map">a streamlined set of processes and templates</a> based on frameworks and standards such as ITIL<sup><small>®</small></sup>, ISO 20000, CMMI-SVC<sup><small>®</small></sup>, COBIT<sup><small>®</small></sup> etc.</html>		<html>The YaSM model helps organizations that wish to include established service management best practice into their Management Mesh, by providing <a href="https://yasm.com/en/products/yasm-process-map" title="Service management process templates - the YaSM Process Map">a streamlined set of processes and templates</a> based on frameworks and standards such as <a href="https://yasm.com/wiki/en/index.php/YaSM_and_ITIL" title="YaSM and ITIL">ITIL</a><sup><small>®</small></sup>, <a href="https://yasm.com/wiki/en/index.php/ISO_20000" title="What is ISO 20000?">ISO 20000</a>, CMMI-SVC<sup><small>®</small></sup>, COBIT<sup><small>®</small></sup> etc.</html>
	<p> </p>		<p> </p>

Line 342:		Line 342:
	===Progressive management practices===		===Progressive management practices===

	In addition to "traditional" service management guidance, VeriSM acknowledges that many organizations have started to adopt "progressive" practices in their quest to work smarter and become more flexible. These practices often have their roots in other areas such as manufacturing and software development, and include concepts such as DevOps, Agile, [https://en.wikipedia.org/wiki/Kanban Kanban], Lean etc.		In addition to "traditional" service management guidance, VeriSM acknowledges that many organizations have started to adopt "progressive" practices in their quest to work smarter and become more flexible. These practices often have their roots in other areas such as manufacturing and software development, and include concepts such as [[DevOps and YaSM\|DevOps]], [[YaSM and Agile Service Management\|Agile]], [https://en.wikipedia.org/wiki/Kanban Kanban], Lean etc.

	As a rule, the progressive management practices don't offer detailed guidance such as specifications of low-level activities to be carried out. They rather describe		As a rule, the progressive management practices don't offer detailed guidance such as specifications of low-level activities to be carried out. They rather describe
Line 351:		Line 351:
	*And even philosophies.		*And even philosophies.

	[~~https://en~~.~~wikipedia.org/wiki/DevOps~~ DevOps], for example, introduces the concept of cross-functional teams who manage a service across the whole lifecycle. And it puts the emphasis on automated and frequent deployment, helped by technologies such as virtualization and containerization. So DevOps is not an alternative to time-tested service management guidance, but a source of ideas for the design of better, leaner processes.		[[DevOps_and_YaSM#What_is_DevOps.3F\|DevOps]], for example, introduces the concept of cross-functional teams who manage a service across the whole lifecycle. And it puts the emphasis on automated and frequent deployment, helped by technologies such as virtualization and containerization. So DevOps is not an alternative to time-tested service management guidance, but a source of ideas for the design of better, leaner processes.

	Since there is no fixed list of "progressive management practices" and every organization will have its own requirements, the YaSM process model is not specifically adapted to any such practice. Rather, YaSM provides a streamlined, straightforward set of processes and templates that give organizations the flexibility to build practices such as DevOps and Agile into their service management procedures.		<html>Since there is no fixed list of "progressive management practices" and every organization will have its own requirements, the YaSM process model is not specifically adapted to any such practice. Rather, YaSM provides a streamlined, straightforward set of processes and templates that give organizations the flexibility to build practices such as <a href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#Can_YaSM_and_DevOps_go_together.3F" title="Can YaSM and DevOps go together?">DevOps</a> and <a href="https://yasm.com/wiki/en/index.php/YaSM_and_Agile_Service_Management#Are_the_YaSM_process_templates_compatible_with_Agile_principles.3F" title="Are the YaSM process templates compatible with Agile principles?">Agile</a> into their service management procedures.</html>
	<p> </p>		<p> </p>