Change Management Flashcards
Emergency change
Is one that must be assessed and implemented (without prior authorization) as quickly as possible to resolve a major incident
Rollback strategy
Strategies of recovery to previous state (black out plan)
Standard change
Is one that occurs frequently, is low risk and has pre-established procedure with documented tasks for completion
Change management
The objective of change management is to drastically minimize the risk and impact a change can have an business operations. Applies a financial process to an acceptable change
ITIL
Information technology infrastructure library
Normal change
Is one that is standard but not an emergency. Can be approved by a change control board or comitee
Chain of change management
Receive request=> test for feasibility => identify rollback options => document changes => finalize automatization => determine change window=>implement=> verify=> update change management baseline=> close and archive request
Regression testing
Regression and interoperability testing
Change testing
Use sandbox testing environment, this is an environment without connection to the real word or production system. Technological safe space. Using before making change in production. Can have duplicated environment and you can there test patch and confirm its safety before deployments.
Backout plan
Plan where you can revert back to previous configuration. This is plan where you prepare the worst scenario. Some changes are difficult to revert - so there must be different techniques.
Full backup must be prepared.
Maintenance window
Planned time where change is made, without disruption to working environment.
Sop - standards operating procedure
Process must be well documented, documentation available on the intranet, along with all standards and procedures. Changes to the process must be updated in the documentation