Management Practice - Change Enablement

Question 1

Management Practice - Change Enablement

Answer 1

To maximize the number of successful IT changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing a change schedule.

Question 2

Change Definition

Answer 2

The addition, modification, or removal of anything that could have a direct or indirect effect on services.

Changes could affect a service directly or indirectly.
Scope defined by each organization but generally includes changes to:
* IT infrastructure
* Applications
* Documentation
* Processes
* Supplier relationships
* Anything else that might directly or indirectly impact a product or service

NOT AT SAME LEVEL IN PLAN OR ENGAGE

Balance between beneficial changes and the adverse effects of change (value/risk balance)

Change Assessment (IMPORTANT)
All changes should be assessed by people who are able to understand the risks and expected benefits and then authorized before deployment.

Change Authorization (IMPORTANT)
The person who authorizes a change is known as a change authority. It is essential that the correct change authority is assigned to each type of change to ensure that change enablement is both efficient and effective. (Change advisory board)

Question 3

Change Schedule

Answer 3

Is used to:
* Plan changes
* Assist in communication
* Avoid conflicts
* Assign resources

Supports risk assessment to gather input from many stakeholders.

Raises awareness and facilitates readiness.

Question 4

Types of Change

Answer 4

1. Standard change (low risk, pre-authorized changes that are well-understood and fully documented and can be implemented without additional authorization)
2. Normal change (need to be scheduled, assessed, and authorized following a standard process)
3. Emergency change (must be implemented as soon as possible to perhaps resolve an incident or implement a security patch. EXPEDITE)