Download as xls, pdf, or txt
Download as xls, pdf, or txt
You are on page 1of 11

Change Management - Checklist

Change number

3377860

Sl.No 1 2 3 4 5 6 7 8 9 10

11

12 13 14 15

16

17

18

19

20 21 22

Change Management - Checklist


Change description

SECURITY: Apply JUN 2012 MS Security patches on Windows servers PROD GROUP

Internal Change Review What is the lead time for the change? Who is the owner of the change? (e.g application team, middleware team etc) Please attach detailed implementaion document here consisting of step by step approach for implementation /verification/ fallback plan here. Please attach results of implementaion performed on test system or Pre-prod here. What is the OS version on Test and on Production? Please provide screen shot of OS level of both Test and Production here. What is the Middleware version on Test and on Production? Please provide screen shot of Middleware level of both Test and Production here. If it is Middleware upgrade, have you verified if system requirments (pre-required OS level on the system) is met. Verify in the below link for MQ http://www-01.ibm.com/software/integration/wmq/requirements/index.html If it is Application deployement/bar file deployment, do you have an understanding as to what the change is and its impact, expected behavior If it is Application deployment, has this been deployed on test system, Please provide test results here. What is time alloted for change/valiadation/rollback? Please provide splitup here Does the Outage time in the CR, include the time for reboot (Reboot of system/ Jobs/tasks/ other sub-components which may cause full/partial downtime), also considering the time taken for tasks done by other service lines working on dependent changes? Please mention the time here. Who are the resources from Middleware required for change implementation ? Are they available, engaged and are active members of the assessment, CAB meetings? who are the change approvers? Has it been approved by CAB and other approvers? Have the focal points for communications/customer contact details been identified and documented in the change record? Pls list them here Has the dependencies and/or conflicts with other pending/scheduled changes been identified and informed to CM? a)Please mention the dependent CR numbers, if any. B) Mention the conflicting CR numbers if any, and the reason for conflict.

If this change is related/dependent to set of other changes, is there a clear end to end plan of Change Implementation sequence, and have the internal coordination of the changes been agreed with the other teams? Have the attachments provided in the Change (FTP Sites/paths/files etc) been checked to make sure they contain all the necessary and correct scripts/instructions to implement the change? Has it been verified that the implementer has all the required access to the servers to perform this change? (Ex: userid /pwd to log into the servers, Privilege to run the scripts, permissions on system files, FTP Access, etc..) Has the versions of hardware and other dependant software component's compatibility been checked to support the change implementation? Is this change triggered by an incident or a problem? If yes, please mention the related ticket number If a similar change had failed in the recent past (in the last 3 months) please provide the Change Reference and Failure details. Else please type N/A (Not Applicable)

Account

FLM

Pool No

Change Implementer Name

Lead Time Available for Review

Michelin Comments/Artifacts/ test results

Balamurugan

7 Ramesh

Remarks

Proposed Teams involved Date of Change

SA Performing Change

June 28th 2012

Mqseries/Wintel

Yes

MW Scope

External Teams

Technology Dependencies Components Change Involved execution / preimplementa tions

To stop/start the Adapter

Adapter

Outage Risks / Issues Change Complexity Time

SME Availability

Internal Change Review Done by

Medium

You might also like