Date: Thu, 28 Mar 2024 22:40:45 +0100 (CET) Message-ID: <602725981.275.1711662045356@czmuims01.ops.egi.eu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_274_1472425669.1711662045356" ------=_Part_274_1472425669.1711662045356 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Ensuring effective change management within the EGI=E2=80=99s production= IT environment is extremely important in ensuring high-quality delivery of= IT services.
The purpose of the IT Change Management Policy is to manage changes to CIs in the Internal CMDB= span> in a planned and predictable manner in order to assign resources, ass= ess risk and minimize any potential negative impact to services.
This policy applies specifically to the IMS owner and IMS Manager, the Qua=
lity and Risk Manager, all Process owners, Process managers, Service owners=
, Service Suppliers and all EG=
I staff involved in a change affecting EGI branded services in the service catalogue of EGI Foundation. <=
span style=3D"color: rgb(255,0,0);">C=
hanges to CIs in the Internal CMDB are under scope of Change Manag=
ement. Of partic=
ular importance are changes which have the potential to directly affect oth=
er services under the scope of CHM. Other EGI federated services are covered within CHM of the respective SMS of=
the service supplier.
Major changes to services that affect the EGI Service Portfolios are tho= se having a high-risk (see procedure CHM1) to impact the business outco= me of the EGI Federation and they should be within the scope of Servic= e Portfolio Management SPM. These changes should be tracked via Servic= e Design and Transition Package documents within the SPM process and are su= bject to approved by the Services and Solutions Board (SSB). Examples of su= ch changes include:
If such changes are brought directly to the attention of the CAB (i.e. n= ot from SPM), then the CAB will request that they require additional approv= al by SPM.
All changes (including urgent chan= ges) to CIs in the Internal CMDB must follow a= standard process to ensure appropriate planning, resourcing and execution.=
Normal change: Ch= ange is created by the Change Requester (usually the service supplier) and = is approved by the Change Owner (a member of the CAB, normally the service = owner).
Standard change: Recurrent changes may be classified as= 'standard' or pre-approved changes and do not need to be explicitly approv= ed by the CAB on subsequent occasions. A Standard change is created by the Change Requester and approved by the = Change Owner. The Change Requester should never be the same person as the C= hange Owner.
Emergency change: In exception to the above, Emergency = changes may be applied with only asse= ssment and approval by the Change Owner and without prior assessment and approval from th= e CAB. However, these Emergency changes shall still be recorded and reviewe= d. Emergency changes may be requested= and applied by the supplier or exceptionally by EGI Foundation staff. = ;
Change Advisory Board: The Change Advisory Board (CAB) along with the Change Manage= ment Process Manager are the stewards of this process. Changes to CIs in the Internal C= MDB must be presented to the CAB for assessment and approval in = order to coordinate timelines, avoid conflict and maintain a complete and c= ontrolled view of changes at EGI.