Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
4 views2 pages

Change Management

Change management involves upgrading software, modifying configurations, and requires a formal approval process to minimize risks and impacts on enterprise systems. The process includes completing request forms, analyzing risks, and ensuring stakeholder involvement. Effective change management is critical to avoid disruptions and should include testing, a backout plan, and maintenance windows to mitigate risks.

Uploaded by

sangkim0707
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views2 pages

Change Management

Change management involves upgrading software, modifying configurations, and requires a formal approval process to minimize risks and impacts on enterprise systems. The process includes completing request forms, analyzing risks, and ensuring stakeholder involvement. Effective change management is critical to avoid disruptions and should include testing, a backout plan, and maintenance windows to mitigate risks.

Uploaded by

sangkim0707
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

change management

- updgrade software, patch and application


change firewall configuration modify switch ports

occurs very frequently


affect many systems user in enterprise

need formal process have clear policies


sometimes extremely difficulty to implement

change approval process

typical approval process

1. complete the request forms


2. purpose of the change
3. scope of change
4. schedule time of change
5. determine affected systems impact
6. analyze the risk
7. get approval

ownership
-owner who manages the process not actual perform
-responsible of the process

stakeholder
-impacted by the changes
-a single change can impact many different indivi department

impact analysis
- risk value
- can be mess up existing
- risk value NOT making changing

test
- sandbox testing
- test tech in no connection to real word
-can make changes without affected in real world
-backout plan

you need backout plan to bring back everything to normal and original

need plan and tech back ups

maintenance window
schedule without too much risk and impacts
etc overnight holiday
time of year when not busy

change management very critical when not done in procedure


standard operating procedure

You might also like