Document control

AreaCHM
Procedure status

FINALISED

OwnerMatthew Viljoen 
Approvers

Process Owner 

OMB

Approval status

APPROVED

Approved version and date

v13  

Statement

Procedure how standard changes list should be maintained

Dissemination Level

TLP:WHITE - Public

Next procedure reviewTogether with process review Change Management CHM


Overview

A standard change is a repeat change that is very similar in character to a previous change that has been submitted and pre-approved by the CAB. Standard changes exist to reduce operational overhead for everyone who works with changes within an operational environment.

The change should be considered a standard change if all of the following criteria are fulfilled:

  • It is very likely (or certain) that there will be multiple future occurrences of this change.
  • The risks associated with the change implementation are low.
  • The impact of the change is well-known and acceptable in terms of business criticality.
  • The situation in which the change may be needed
  • The specific steps to be performed to implement the change are well-known and can be documented in a way that supports an adequate level of consistency and repeatability.

All changes that are candidates for standard changes must be submitted to Jira with a Change Request (CR) as a normal change (see: CHM1 Manage changes including emergency changes) and be approved.  Before future repeat changes, somebody (possibly the Change Implementer, Service Owner) may decide to make the change a standard change by following the procedure listed below.

Standard changes are listed on the EGI Change Management CHM - Standard Changes dedicated to the service in question.  The lists of standard changes shall be regularly reviewed and updated, and consulted whenever a new change is being planned, in case the change is already a standard change.

Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Entities/roles involved in the procedure

Entity/roleDescription
Service OwnerThe person responsible for the service affected by the change or the line manager of the Change Owner

Change Advisory Board (CAB)

A group of technical and strategic experts (membership decided by SSB) is tasked with reviewing proposed change requests and reviewing them and approve or reject the changes. The CAB should either meet on a regular basis or on an 'ad-hoc' basis to review important changes.

Triggers

A past change that was completed successfully is decided to be a candidate for a Standard Change. This is possible because it is known that there will be multiple future occurrences of the change, or a similar change has already been submitted via multiple Change Requests (CRs) and it is likely that it will re-occur in the future.

Steps

Step# ResponsibleAction
1Service Owner

Decides whether the change should become a candidate for a standard change.  If not, the procedure terminates.

2CABThe CAB decides whether to approve the standard change. If not, the procedure terminates.
3Service Owner

Adds the standard change to the list of the Standard Changes corresponding to the service in question. The entry shall contain a reference to Jira ticket of the original CR the first time the standard change was reviewed and approved, along with who should approve the change (if anyone) and who should be notified and/or provide sign-off of the change.

Table of contents