SP5: Assess and coordinate changes: Difference between revisions

From YaSM Service Management Wiki
No edit summary
No edit summary
Line 64: Line 64:


<p><i><u>Compatibility</u>: The YaSM change management process is <a href="/wiki/en/index.php/YaSM_and_ISO_20000#ISO_20000_requirements_and_related_service_management_processes" title="YaSM and ISO 20000">aligned with ISO 20000</a>, the international standard for service management (see ISO/IEC 20000-1:2018, sections <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Operational-planning-and-control" title="ISO 20000 section 8.1: Operational planning and control">8.1</a> and <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Service-design-build-and-transition" title="ISO 20000 section 8.5: Service design, build and transition">8.5</a>), and it <a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Change-enablement" title="ITIL 4 practices and YaSM processes: ITIL 4 change enablement">corresponds to the practice of 'ITIL 4 change enablement'</a>.</i></html>
<p><i><u>Compatibility</u>: The YaSM change management process is <a href="/wiki/en/index.php/YaSM_and_ISO_20000#ISO_20000_requirements_and_related_service_management_processes" title="YaSM and ISO 20000">aligned with ISO 20000</a>, the international standard for service management (see ISO/IEC 20000-1:2018, sections <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Operational-planning-and-control" title="ISO 20000 section 8.1: Operational planning and control">8.1</a> and <a href="/wiki/en/index.php/YaSM_and_ISO_20000#Service-design-build-and-transition" title="ISO 20000 section 8.5: Service design, build and transition">8.5</a>), and it <a href="/wiki/en/index.php/YaSM_and_ITIL#ITIL-4-Change-enablement" title="ITIL 4 practices and YaSM processes: ITIL 4 change enablement">corresponds to the practice of 'ITIL 4 change enablement'</a>.</i></html>
<p>&nbsp;</p>


==Sub-processes==
==Sub-processes==


<html>YaSM change management has the following sub-processes:</p>
<html>YaSM change management has the following sub-processes:</p>
<p>&#160;</p>


<!-- define schema.org/CreativeWork -->
<!-- define schema.org/CreativeWork -->
Line 78: Line 76:
<dd itemprop="description">Process objective: To set up and maintain the tools for an effective and efficient management of changes.</dd></dl>
<dd itemprop="description">Process objective: To set up and maintain the tools for an effective and efficient management of changes.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.2" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.2" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM change management process SP5.2" />
<meta itemprop="alternateName" content="YaSM change management process SP5.2" />
Line 84: Line 81:
<dd itemprop="description">Process objective: To filter out requests for change (RFCs) which do not contain all information required for assessment or which are deemed impractical.</dd></dl>
<dd itemprop="description">Process objective: To filter out requests for change (RFCs) which do not contain all information required for assessment or which are deemed impractical.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.3" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.3" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM change management process SP5.3" />
<meta itemprop="alternateName" content="YaSM change management process SP5.3" />
Line 90: Line 86:
<dd itemprop="description">Process objective: To assess and authorize emergency changes as quickly as possible. This process is invoked if normal change assessment procedures cannot be applied, for example because an emergency requires immediate action.</dd></dl>
<dd itemprop="description">Process objective: To assess and authorize emergency changes as quickly as possible. This process is invoked if normal change assessment procedures cannot be applied, for example because an emergency requires immediate action.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.4" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.4" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM change management process SP5.4" />
<meta itemprop="alternateName" content="YaSM change management process SP5.4" />
Line 96: Line 91:
<dd itemprop="description">Process objective: To determine the required level of authorization for the assessment of a proposed change. Significant changes are passed on to the CAB for assessment, while minor changes are immediately assessed and authorized by the change manager.</dd></dl>
<dd itemprop="description">Process objective: To determine the required level of authorization for the assessment of a proposed change. Significant changes are passed on to the CAB for assessment, while minor changes are immediately assessed and authorized by the change manager.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.5" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.5" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM change management process SP5.5" />
<meta itemprop="alternateName" content="YaSM change management process SP5.5" />
Line 102: Line 96:
<dd itemprop="description">Process objective: To assess and authorize a proposed change through the change advisory board (CAB). If required, higher levels of authority (e.g. the management board) are involved in the authorization process.</dd></dl>
<dd itemprop="description">Process objective: To assess and authorize a proposed change through the change advisory board (CAB). If required, higher levels of authority (e.g. the management board) are involved in the authorization process.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.6" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.6" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM change management process SP5.6" />
<meta itemprop="alternateName" content="YaSM change management process SP5.6" />
Line 108: Line 101:
<dd itemprop="description">Process objective: To constantly monitor outstanding changes with regards to their implementation status, and to take corrective action as appropriate.</dd></dl>
<dd itemprop="description">Process objective: To constantly monitor outstanding changes with regards to their implementation status, and to take corrective action as appropriate.</dd></dl>
</div>
</div>
<p><br /></p>
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.7" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.7" itemscope itemtype="https://schema.org/CreativeWork" itemref="md-type-subProcess">
<meta itemprop="alternateName" content="YaSM change management process SP5.7" />
<meta itemprop="alternateName" content="YaSM change management process SP5.7" />
Line 114: Line 106:
<dd itemprop="description">Process objective: To assess the course of the change implementation and the achieved results, in order to verify that a complete history of activities is present for future reference, and to make sure that any mistakes are analyzed and lessons learned.</dd></dl>
<dd itemprop="description">Process objective: To assess the course of the change implementation and the achieved results, in order to verify that a complete history of activities is present for future reference, and to make sure that any mistakes are analyzed and lessons learned.</dd></dl>
</div><!-- end of schema.org/CreativeWork --><p></html>
</div><!-- end of schema.org/CreativeWork --><p></html>
<p>&nbsp;</p>


==Process outputs==
==Process outputs==


<html><div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_outputs" itemscope="itemscope" itemtype="https://schema.org/CreativeWork"><!-- define schema.org/CreativeWork -->
<html><!-- define schema.org/DefinedTermSet -->
<div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-inputs-outputs" itemscope="itemscope" itemtype="https://schema.org/DefinedTermSet">
<link itemprop="additionalType" href="http://www.productontology.org/id/Input/output" />
<meta itemprop="name" content="YaSM process SP5: documents and records" />
<meta itemprop="name" content="YaSM process SP5: documents and records" />
<meta itemprop="name" content="Change assessment process outputs" />
<meta itemprop="name" content="Change assessment process outputs" />
<meta itemprop="alternateName" content="Change assessment data objects" />
<meta itemprop="alternateName" content="Change assessment data objects" />
<p><span itemprop="description">This section lists the documents and records produced by 'change management'.</span> YaSM data objects <a href="#ydo" title="YaSM data object">[*]</a> are marked with an asterisk, while other objects are displayed in gray.</p>
<p><span itemprop="description">This section lists the documents and records produced by 'change management'.</span> YaSM data objects <a href="#ydo" title="YaSM data object">[*]</a> are marked with an asterisk, while other objects are displayed in gray.</p>
<p>&#160;</p>


<dl id="CAB-meeting-minutes"><dt>CAB meeting minutes</dt>
<dl>
<dd>The CAB meeting minutes document the topics discussed in a change advisory board (CAB) meeting and any decisions taken. A draft of this document can be circulated in preparation of the CAB meeting to inform the CAB members of agenda items to be dealt with. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="CAB-meeting-minutes">CAB meeting minutes</dt>
<dl id="Change-assessment-report"><dt>Change assessment report</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The CAB meeting minutes document the topics discussed in a change advisory board (CAB) meeting and any decisions taken. A draft of this document can be circulated in preparation of the CAB meeting to inform the CAB members of agenda items to be dealt with. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>The results of a change assessment are documented in a change assessment report. Every non-standard change requires formal assessment before being authorized. Particular changes may require more extensive assessments than others, so the contents of the assessment report will depend on the nature and scope of the proposed change. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Change-assessment-report">Change assessment report</dt>
<dl id="Change-authorization-notice" style="color:#636363"><dt>Change authorization notice</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The results of a change assessment are documented in a change assessment report. Every non-standard change requires formal assessment before being authorized. Particular changes may require more extensive assessments than others, so the contents of the assessment report will depend on the nature and scope of the proposed change. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>Information related to the authorization status of a change. This information is sent to the initiator of a change to communicate that a change has been authorized or rejected. In case a change has been rejected, the notice may include recommendations on how the change must be modified before it can be authorized.</dd></dl>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Change-authorization-notice">Change authorization notice</dt>
<dl id="Change-model"><dt>Change model</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Information related to the authorization status of a change. This information is sent to the initiator of a change to communicate that a change has been authorized or rejected. In case a change has been rejected, the notice may include recommendations on how the change must be modified before it can be authorized.</dd></div>
<dd>Change models describe procedures for the handling of recurring changes. While change models can be created for changes of any scale, they are often used to define standard changes (low-risk, pre-authorized changes like installing additional hardware on a client PC). Change models are an important tool to reduce the workload of the change manager and the CAB. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Change-model">Change model</dt>
<dl id="Change-record"><dt>Change record</dt>
<dd itemprop="description" style="margin-bottom: 1em;">Change models describe procedures for the handling of recurring changes. While change models can be created for changes of any scale, they are often used to define standard changes (low-risk, pre-authorized changes like installing additional hardware on a client PC). Change models are an important tool to reduce the workload of the change manager and the CAB. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>A change record contains all details of a change, documenting the lifecycle of a single change. In its initial state, a change record describes a request for change (RFC) which is to be assessed and authorized prior to implementing the change. Further information is added as the change progresses through its lifecycle. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Change-record">Change record</dt>
<dl id="Change-schedule"><dt>Change schedule</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A change record contains all details of a change, documenting the lifecycle of a single change. In its initial state, a change record describes a request for change (RFC) which is to be assessed and authorized prior to implementing the change. Further information is added as the change progresses through its lifecycle. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>The change schedule lists all proposed and authorized changes, including their planned and actual implementation dates. It is sometimes called a forward schedule of change, even though it also contains information about changes that have already been implemented. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Change-schedule">Change schedule</dt>
<dl id="Post-implementation-review-report"><dt>Post-implementation review report</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The change schedule lists all proposed and authorized changes, including their planned and actual implementation dates. It is sometimes called a forward schedule of change, even though it also contains information about changes that have already been implemented. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>The results of a post-implementation review are documented in a post-implementation review report. Post-implementation reviews (PIR) take place after a change has been implemented. Their aim is to determine if the change was successful and to identify improvement opportunities for future changes. <a href="#ydo" title="YaSM data object">[*]</a></dd></dl>
<div itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
<p><br /></p>
<dt itemprop="name" id="Post-implementation-review-report">Post-implementation review report</dt>
<dl style="color:#636363"><dt>Suggested process modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">The results of a post-implementation review are documented in a post-implementation review report. Post-implementation reviews (PIR) take place after a change has been implemented. Their aim is to determine if the change was successful and to identify improvement opportunities for future changes. <a href="#ydo" title="YaSM data object">[*]</a></dd></div>
<dd>A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.</dd></dl>
<div style="color:#636363" itemprop="hasDefinedTerm" itemscope itemtype="https://schema.org/DefinedTerm">
</div><!-- end of schema.org/CreativeWork --><p>
<dt itemprop="name">Suggested process modification</dt>
<dd itemprop="description" style="margin-bottom: 1em;">A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.</dd></div>
</dl>
</div><!-- end of schema.org/DefinedTermSet --><p>


<p>&nbsp;</p>
<p>&nbsp;</p>
Line 156: Line 150:
</p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" title="Example: YaSM checklists and document templates">example</a>) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see <a href="https://yasm.com/wiki/en/img/yasm-project/Yasm-object-lifecycle-diagram.jpg" title="Example: YaSM object lifecycle diagram (.JPG)">example</a>).</span>
</p><p><span id="ydo"><strong>[*]</strong> <i>"YaSM data objects"</i> are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see <a href="https://yasm.com/wiki/en/index.php/Service_Management_Checklists" title="Example: YaSM checklists and document templates">example</a>) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see <a href="https://yasm.com/wiki/en/img/yasm-project/Yasm-object-lifecycle-diagram.jpg" title="Example: YaSM object lifecycle diagram (.JPG)">example</a>).</span>
</p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html>
</p><p><i>"Other objects"</i> are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.</html>
<p>&nbsp;</p>


==Process metrics==
==Process metrics==
Line 164: Line 156:


For suggestions of [[Service Management Metrics|suitable metrics]], please refer to the [[Service_Management_Metrics#Metrics_for_the_change_assessment_process|list of metrics for YaSM's change assessment process]].
For suggestions of [[Service Management Metrics|suitable metrics]], please refer to the [[Service_Management_Metrics#Metrics_for_the_change_assessment_process|list of metrics for YaSM's change assessment process]].
<p>&nbsp;</p>


==Roles and responsibilities==
==Roles and responsibilities==
Line 247: Line 237:
<html><div itemid="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject">
<html><div itemid="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" title="Change management: process definition" itemprop="contentUrl">
<a href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" title="Change management: process definition" itemprop="contentUrl">
<img style="display: block; float: left; margin-right: 20px" src="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" width="320" height="160" title="Change management: process definition" alt="What is change management? Definition of the change management process SP5 from the YaSM framework." />
<img style="display: block; float: left; margin-left: 10px; margin-right: 20px" src="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" width="320" height="160" title="Change management: process definition" alt="What is change management? Definition of the change management process SP5 from the YaSM framework." />
<meta itemprop="caption" content="Assess and coordinate changes | YaSM change management | Process definition SP5" />
<meta itemprop="caption" content="Assess and coordinate changes | YaSM change management | Process definition SP5" />
<meta itemprop="width" content="1050" />
<meta itemprop="width" content="1050" />
<meta itemprop="height" content="525" /></a></div>
<meta itemprop="height" content="525" /></a></div>
<div style="margin-left: 30%; color:#636363">
<div style="margin-left: 5%; color:#636363">
<p style="margin-top: 0;">Is based on: The Change assessment process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p>
<p style="margin-top: 0; word-wrap:normal;">Is&nbsp;based on: The Change assessment process from the <a href="https://yasm.com/en/products/yasm-process-map" title="YaSM Process Map">YaSM Process Map</a>.</p>


<p>By:&#160;&#160;Stefan Kempter&#160;<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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<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.<br style="clear:both;"/></div><p>
<p>By:&#160;&#160;Stefan Kempter&#160;<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>&#160;&#160;and&#160;&#160;Andrea Kempter&#160;<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.<br style="clear:both;"/></div><p>
Line 259: Line 249:


<p><small>
<p><small>
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<span itemprop="breadcrumb" itemscope itemtype="https://schema.org/BreadcrumbList">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemprop="itemListElement" itemscope itemtype="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_description">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_description">
<span itemprop="name">Process description</span></a>
<span itemprop="name">Process description</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="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Sub-processes">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Sub-processes">
<span itemprop="name">Sub-processes</span></a>
<span itemprop="name">Sub-processes</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="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_outputs">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_outputs">
<span itemprop="name">Process outputs</span></a>
<span itemprop="name">Process outputs</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="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_metrics">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_metrics">
<span itemprop="name">Metrics</span></a>
<span itemprop="name">Metrics</span></a>
<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="https://schema.org/ListItem">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Roles_and_responsibilities">
<a itemprop="item" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Roles_and_responsibilities">
<span itemprop="name">Roles</span></a>
<span itemprop="name">Roles</span></a>
Line 307: Line 297:
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.6">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.6">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.7">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#SP5.7">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_outputs">
  <link itemprop="hasPart" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-inputs-outputs">
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" />
  <link itemprop="image" href="https://yasm.com/wiki/en/img/yasm-process-definition/what-is-change-management-process.jpg" />
Line 324: Line 314:
[[Category:YaSM process]]
[[Category:YaSM process]]
<!-- --- -->
<!-- --- -->

Revision as of 18:00, 3 February 2021

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


 

Process name: Assess and coordinate changes - Part of: Supporting processes

Previous process: Manage configuration information

Next process: Manage projects

 

Process description

The change management process in YaSM (fig. 1) acts as a gate-keeper, ensuring that modifications to the service provider's range of services and its underlying components are made only after risks and potential side-effects have been carefully considered.

Fig. 1: Assess and coordinate changes. - YaSM change management process SP5. - Related with: Practice of ITIL 4 change enablement.
Fig. 1: 'Assess and coordinate changes':
YaSM change management process SP5.


To this end, other YaSM processes requiring a change will submit a request for change (RFC) to the change manager. The RFC will then be assessed by the change manager or the CAB, depending on the required level of authority for approval.

A special procedure is called upon for assessing emergency changes, for example if the resolution of a major incident requires the implementation of a non-standard change on an urgent basis.

In this context, change models are an important tool for reducing the workload of the change manager and the CAB. Change models are used to define "standard changes" - types of well-known, low-risk changes which may be implemented without the involvement of the formal change assessment process.

 

Compatibility: The YaSM change management process is aligned with ISO 20000, the international standard for service management (see ISO/IEC 20000-1:2018, sections 8.1 and 8.5), and it corresponds to the practice of 'ITIL 4 change enablement'.

Sub-processes

YaSM change management has the following sub-processes:

SP5.1: Support the assessment of changes
Process objective: To set up and maintain the tools for an effective and efficient management of changes.
SP5.2: Log and review RFCs
Process objective: To filter out requests for change (RFCs) which do not contain all information required for assessment or which are deemed impractical.
SP5.3: Assess emergency changes
Process objective: To assess and authorize emergency changes as quickly as possible. This process is invoked if normal change assessment procedures cannot be applied, for example because an emergency requires immediate action.
SP5.4: Assess changes (change manager)
Process objective: To determine the required level of authorization for the assessment of a proposed change. Significant changes are passed on to the CAB for assessment, while minor changes are immediately assessed and authorized by the change manager.
SP5.5: Assess changes (CAB)
Process objective: To assess and authorize a proposed change through the change advisory board (CAB). If required, higher levels of authority (e.g. the management board) are involved in the authorization process.
SP5.6: Monitor open changes
Process objective: To constantly monitor outstanding changes with regards to their implementation status, and to take corrective action as appropriate.
SP5.7: Review and close changes
Process objective: To assess the course of the change implementation and the achieved results, in order to verify that a complete history of activities is present for future reference, and to make sure that any mistakes are analyzed and lessons learned.

Process outputs

This section lists the documents and records produced by 'change management'. YaSM data objects [*] are marked with an asterisk, while other objects are displayed in gray.

CAB meeting minutes
The CAB meeting minutes document the topics discussed in a change advisory board (CAB) meeting and any decisions taken. A draft of this document can be circulated in preparation of the CAB meeting to inform the CAB members of agenda items to be dealt with. [*]
Change assessment report
The results of a change assessment are documented in a change assessment report. Every non-standard change requires formal assessment before being authorized. Particular changes may require more extensive assessments than others, so the contents of the assessment report will depend on the nature and scope of the proposed change. [*]
Change authorization notice
Information related to the authorization status of a change. This information is sent to the initiator of a change to communicate that a change has been authorized or rejected. In case a change has been rejected, the notice may include recommendations on how the change must be modified before it can be authorized.
Change model
Change models describe procedures for the handling of recurring changes. While change models can be created for changes of any scale, they are often used to define standard changes (low-risk, pre-authorized changes like installing additional hardware on a client PC). Change models are an important tool to reduce the workload of the change manager and the CAB. [*]
Change record
A change record contains all details of a change, documenting the lifecycle of a single change. In its initial state, a change record describes a request for change (RFC) which is to be assessed and authorized prior to implementing the change. Further information is added as the change progresses through its lifecycle. [*]
Change schedule
The change schedule lists all proposed and authorized changes, including their planned and actual implementation dates. It is sometimes called a forward schedule of change, even though it also contains information about changes that have already been implemented. [*]
Post-implementation review report
The results of a post-implementation review are documented in a post-implementation review report. Post-implementation reviews (PIR) take place after a change has been implemented. Their aim is to determine if the change was successful and to identify improvement opportunities for future changes. [*]
Suggested process modification
A suggestion for modifying one or several service management processes. Suggestions for process modifications or improvements may originate from anywhere within the organization.

 


Notes:

[*] "YaSM data objects" are those documents or records for which the YaSM model provides detailed recommendations: Every YaSM object has an associated checklist (see example) describing its typical contents, and an associated lifecycle diagram depicting how the status of the object changes as it is created, updated, read and archived by various YaSM processes (see example).

"Other objects" are mostly informal data or information where YaSM has less strong views about their contents. There are no associated lifecycle diagrams or checklists.

Process metrics

Process metrics are used, for example, to assess if the service management processes are running according to expectations.

For suggestions of suitable metrics, please refer to the list of metrics for YaSM's change assessment process.

Roles and responsibilities

Process owner: Change manager

  • The Change manager controls all changes across their lifecycle. His primary objective is to enable beneficial changes to be made, with minimum disruption to services. For important changes, the change manager will refer the authorization of changes to the change advisory board (CAB).

 

Responsibility matrix: "SP5: Assess and coordinate changes"
YaSM role / sub-process CAB Change mgr. Change owner Config. mgr. ECAB
SP5.1 Support the assessment of changes R AR - - -
SP5.2 Log and review RFCs - AR R - -
SP5.3 Assess emergency changes - AR - - R
SP5.4 Assess changes (change manager) - AR - R -
SP5.5 Assess changes (CAB) R AR - R -
SP5.6 Monitor open changes - AR - - -
SP5.7 Review and close changes R AR R - -

 

Notes

Is based on: The Change assessment process from the YaSM Process Map.

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

 

Process description  › Sub-processes  › Process outputs  › Metrics  › Roles