SP5: Assess and coordinate changes: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
<meta name="keywords" content="assess and coordinate changes, yasm assess changes, yasm coordinate changes, yasm change management, service management change process" /> | <meta name="keywords" content="assess and coordinate changes, yasm assess changes, yasm coordinate changes, yasm change management, service management change process" /> | ||
<meta name="description" content="YaSM process: Assess and coordinate changes (SP5). - Definition, sub-processes, process outputs, process metrics and roles." /> | <meta name="description" content="YaSM process: Assess and coordinate changes (SP5). - Definition, sub-processes, process outputs, process metrics and roles." /> | ||
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes" /> | |||
<meta property="og:title" content="SP5: Assess and coordinate changes | YaSM Service Management Wiki" /> | |||
<meta property="og:description" content="YaSM process: Assess and coordinate changes (SP5). - Definition, sub-processes, process outputs, process metrics and roles." /> | |||
<meta property="og:site_name" content="YaSM"> | |||
<meta property="og:type" content="article" /> | |||
<meta property="fb:admins" content="100002035253209" /> | |||
<meta property="fb:admins" content="100002592864414" /> | |||
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" /> | |||
<meta property="og:image:width" content="625" /> | |||
<meta property="og:image:height" content="374" /> | |||
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" /> | |||
</itpmch> | </itpmch> | ||
<html> | <html><a href="https://yasm.com/wiki/de/index.php/SP5:_Bewerten_und_Koordinieren_von_Changes"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/></html> | ||
<a href="https://yasm.com/wiki/de/index.php/SP5:_Bewerten_und_Koordinieren_von_Changes"><img src="https://yasm.com/wiki/en/img/yasm-wiki/yasm-wiki-deutsch.png" width="48" height="30" style="float:right;" alt="auf Deutsch" title="diese Seite auf Deutsch" /></a><br style="clear:both;"/> | |||
<p> </p> | <p> </p> | ||
'''Process name:''' [[#Process_description|Assess and coordinate changes]] - '''Part of:''' [[YaSM_Processes#supporting-service-management-processes|Supporting service management processes]] | |||
'''Previous process:''' [[SP4: Manage configuration information|Manage configuration information]] | |||
'''Next process:''' [[SP6: Manage projects|Manage projects]] | |||
<p> </p> | <p> </p> | ||
Line 14: | Line 27: | ||
==Process description== | ==Process description== | ||
<html><div itemscope itemtype="https://schema.org/ImageObject"><a href="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" title="Assess and coordinate changes. - YaSM process SP5" itemprop="contentUrl"><img style="margin:20px 0px 10px 0px; float:left;" src="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" width="625" height="374" title="Assess and coordinate changes. - YaSM process SP5" alt="Fig. 1: Assess and coordinate changes. - YaSM change assessment process SP5." /></a><br style="clear:both;"/><div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 1:</b></span> <small><span itemprop="caption">"Assess and coordinate changes". - YaSM supporting service management process SP5.</span></small></div></div><br style="clear:both;"/> | <html><div itemid="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" itemscope itemtype="https://schema.org/ImageObject"> | ||
<a href="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" title="Assess and coordinate changes. - YaSM process SP5" itemprop="contentUrl"> | |||
<meta itemprop="width" content="625" /> | |||
<meta itemprop="height" content="374" /> | |||
<meta itemprop="keywords" content="yasm change assessment process" /> | |||
<meta itemprop="keywords" content="yasm change management" /> | |||
<meta itemprop="keywords" content="change management" /> | |||
<img style="margin:20px 0px 10px 0px; float:left;" src="https://yasm.com/wiki/en/img/yasm-process/Assess-and-coordinate-changes-yasm-sp5.jpg" width="625" height="374" title="Assess and coordinate changes. - YaSM process SP5" alt="Fig. 1: Assess and coordinate changes. - YaSM change assessment process SP5." /></a><br style="clear:both;"/> | |||
<div class="thumbcaption"><span style="font-variant:small-caps;"><b>Figure 1:</b></span> <small><span itemprop="caption">"Assess and coordinate changes". - YaSM supporting service management process SP5.</span></small></div></div><br style="clear:both;"/> | |||
<p><span itemprop="description">The YaSM process "<strong class="selflink | <p><span id="md-itempage-description" itemprop="description">The YaSM process "<strong class="selflink">SP5: Assess and coordinate changes</strong>" 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.</span></p> | ||
<p>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.</p> | <p>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.</p> | ||
Line 28: | Line 49: | ||
==Sub-processes== | ==Sub-processes== | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ | <html><!-- define schema.org/CreativeWork --><div itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Sub-processes" itemscope="itemscope" itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop=" | <link itemprop="additionalType" href="http://www.productontology.org/id/Business_process" /> | ||
< | <meta itemprop="name" content="Change assessment processes" /> | ||
<meta itemprop="alternateName" content="YaSM change management processes: definitions" /> | |||
<p><span itemprop="description">YaSM's change management process <i>'SP5: Assess and coordinate changes'</i> has the following sub-processes:</span> | |||
</p> | </p> | ||
<p> </p> | <p> </p> | ||
< | |||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.1" itemscope itemtype="https://schema.org/CreativeWork"> | ||
<meta itemprop="alternateName" content="YaSM change management process SP5.1" /> | |||
<dl id="SP5.1"><dt itemprop="name">SP5.1: Support the assessment of changes</dt> | |||
<dd itemprop="description">Process objective: To set up and maintain the tools for an effective and efficient management of changes.</dd></dl> | |||
</div> | |||
<p><br /></p> | <p><br /></p> | ||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.2" itemscope itemtype="https://schema.org/CreativeWork"> | ||
< | <meta itemprop="alternateName" content="YaSM change management process SP5.2" /> | ||
<dl id="SP5.2"><dt itemprop="name">SP5.2: Log and review RFCs</dt> | |||
<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> | |||
<p><br /></p> | <p><br /></p> | ||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.3" itemscope itemtype="https://schema.org/CreativeWork"> | ||
< | <meta itemprop="alternateName" content="YaSM change management process SP5.3" /> | ||
<dl id="SP5.3"><dt itemprop="name">SP5.3: Assess emergency changes</dt> | |||
<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> | |||
<p><br /></p> | <p><br /></p> | ||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.4" itemscope itemtype="https://schema.org/CreativeWork"> | ||
< | <meta itemprop="alternateName" content="YaSM change management process SP5.4" /> | ||
<dl id="SP5.4"><dt itemprop="name">SP5.4: Assess changes (change manager)</dt> | |||
<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> | |||
<p><br /></p> | <p><br /></p> | ||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.5" itemscope itemtype="https://schema.org/CreativeWork"> | ||
< | <meta itemprop="alternateName" content="YaSM change management process SP5.5" /> | ||
<dl id="SP5.5"><dt itemprop="name">SP5.5: Assess changes (CAB)</dt> | |||
<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> | |||
<p><br /></p> | <p><br /></p> | ||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.6" itemscope itemtype="https://schema.org/CreativeWork"> | ||
< | <meta itemprop="alternateName" content="YaSM change management process SP5.6" /> | ||
<dl id="SP5.6"><dt itemprop="name">SP5.6: Monitor open changes</dt> | |||
<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> | |||
<p><br /></p> | <p><br /></p> | ||
< | <div itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#process-SP5.7" itemscope itemtype="https://schema.org/CreativeWork"> | ||
< | <meta itemprop="alternateName" content="YaSM change management process SP5.7" /> | ||
</div><!-- end of schema.org/ | <dl id="SP5.7"><dt itemprop="name">SP5.7: Review and close changes</dt> | ||
<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> | |||
</div><!-- end of schema.org/CreativeWork --><p></html> | |||
<p> </p> | <p> </p> | ||
Line 59: | Line 104: | ||
==Process outputs== | ==Process outputs== | ||
<html><div itemscope="itemscope" itemtype="https://schema.org/ | <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 --> | ||
<meta itemprop=" | <meta itemprop="name" content="YaSM process SP5: documents and records" /> | ||
<p> | <meta itemprop="name" content="Change assessment process outputs" /> | ||
<meta itemprop="alternateName" content="Change assessment data objects" /> | |||
<p><span itemprop="description">This section lists the documents and records produced by <i>'Assess and coordinate changes'</i>.</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> </p> | <p> </p> | ||
< | |||
< | <dl id="CAB-meeting-minutes"><dt>CAB meeting minutes</dt> | ||
<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> | |||
<p><br /></p> | <p><br /></p> | ||
< | <dl id="Change-assessment-report"><dt>Change assessment report</dt> | ||
< | <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> | ||
<p><br /></p> | <p><br /></p> | ||
< | <dl id="Change-authorization-notice" style="color:#636363"><dt>Change authorization notice</dt> | ||
< | <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> | ||
<p><br /></p> | <p><br /></p> | ||
< | <dl id="Change-model"><dt>Change model</dt> | ||
< | <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> | ||
<p><br /></p> | <p><br /></p> | ||
< | <dl id="Change-record"><dt>Change record</dt> | ||
< | <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> | ||
<p><br /></p> | <p><br /></p> | ||
< | <dl id="Change-schedule"><dt>Change schedule</dt> | ||
< | <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> | ||
<p><br /></p> | <p><br /></p> | ||
< | <dl id="Post-implementation-review-report"><dt>Post-implementation review report</dt> | ||
< | <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> | ||
<p><br /></p> | <p><br /></p> | ||
< | <dl style="color:#636363"><dt>Suggested process modification</dt> | ||
< | <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><!-- end of schema.org/ | </div><!-- end of schema.org/CreativeWork --><p> | ||
<p> </p> | <p> </p> | ||
Line 99: | Line 147: | ||
<html><p>Process metrics are used, for example, to assess if the service management processes are running according to expectations.</p> | <html><p>Process metrics are used, for example, to assess if the service management processes are running according to expectations.</p> | ||
<p>For suggestions of <a | <p>For suggestions of <a href="https://yasm.com/wiki/en/index.php/YaSM_Metrics" title="How to measure the performance of the YaSM processes - Process metrics">suitable metrics</a>, please refer to the <a href="https://yasm.com/wiki/en/index.php/YaSM_Metrics/_Supporting_Service_Management_Processes#metrics-sp5" title="Metrics for the YaSM process SP5: Assess and coordinate changes.">list of metrics for YaSM's change assessment process</a>.</html> | ||
<p> </p> | <p> </p> | ||
Line 179: | Line 227: | ||
<p> </p> | <p> </p> | ||
==[ | == Notes == | ||
Is based on: The change assessment process from the [https://yasm.com/en/products/yasm-process-map YaSM Process Map]. | |||
<html>By:  Stefan Kempter <a rel="author" href="https://plus.google.com/111925560448291102517/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://plus.google.com/113316270668629760475/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps. | |||
< | <p> </p> | ||
</ | |||
<p><small> | <p><small> | ||
Line 217: | Line 251: | ||
</span> | </span> | ||
</small></p> | </small></p> | ||
</ | |||
<!-- define schema.org/ItemPage --> <span itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes" itemscope itemtype="https://schema.org/ItemPage" itemref="md-itempage-description"> | |||
<link itemprop="additionalType" href="http://www.productontology.org/id/Business_process" /> | |||
<meta itemprop="name Headline" content="SP5: Assess and coordinate changes" /> | |||
<meta itemprop="alternativeHeadline" content="YaSM's change assessment process" /> | |||
<link itemprop="url" href="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes" /> | |||
<span itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Sub-processes" itemscope itemtype="https://schema.org/CreativeWork"> | |||
</span> | |||
<span itemprop="hasPart" itemid="https://yasm.com/wiki/en/index.php/SP5:_Assess_and_coordinate_changes#Process_outputs" itemscope itemtype="https://schema.org/CreativeWork"> | |||
</span> | |||
<link itemprop="primaryImageOfPage" 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" /> | |||
<meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Metrics" /> | |||
<meta itemprop="significantLinks" content="https://yasm.com/wiki/en/index.php/YaSM_Metrics/_Supporting_Service_Management_Processes#metrics-sp5" /> | |||
<link itemprop="isPartOf" href="https://yasm.com/wiki/en/index.php/YaSM_Processes#supporting-service-management-processes" /> | |||
<meta itemprop="isBasedOnUrl" content="https://yasm.com/en/products/yasm-process-map" /> | |||
<meta itemprop="inLanguage" content="en" /> | |||
<link itemprop="citation" href="https://yasm.com/wiki/de/index.php/SP5:_Bewerten_und_Koordinieren_von_Changes" /> | |||
<link itemprop="publisher" href="https://yasm.com/en/#YaSMBrand" /> | |||
<link itemprop="copyrightHolder creator" href="https://yasm.com/en/contact#ITProcessMapsOrg" /> | |||
<link itemprop="author" href="https://yasm.com/en/misc/team#StefanKempter" /> | |||
<link itemprop="contributor" href="https://yasm.com/en/misc/team#AndreaKempter" /> | |||
</span><p></html> | |||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:YaSM process]] | [[Category:YaSM process]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 11:03, 15 November 2016
Process name: Assess and coordinate changes - Part of: Supporting service management processes
Previous process: Manage configuration information
Next process: Manage projects
Process description
The YaSM process "SP5: Assess and coordinate changes" 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.
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.
Sub-processes
YaSM's change management process 'SP5: Assess and coordinate changes' 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 'Assess and coordinate changes'. 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 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).
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 and Andrea Kempter , IT Process Maps.
Process description › Sub-processes › Process outputs › Metrics › Roles