Tuesday, December 11, 2018

Remember That All Changes Involve Risk

Remember that all changes involve risk

In the Service Transition phase, there are seven processes we must learn: Change Management, Release and Deployment Management, Service Asset and Configuration Management, Service Validation and Testing, Transition Planning and Support, Evaluation, and Knowledge Management.


The Service V-Model defines progressive levels of activity and levels of testing/validation towards a defined objective, such as a release or major change. The testing that occurs at each level is imperative prior to moving to the next level in order to reduce overall risk during the implementation of a new or changed service.

As the stakeholders define the requirements and move down the Service V-Model, the service provider then moves up the right side of the model by conducting service validation and testing.


The Change Management Process controls the lifecycle of all changes in order to enable beneficial changes to be made with a minimal disruption of IT services. It is concerned with recording, evaluating, approving, testing, and reviewing changes to services, systems, and other configuration items.

What is change? Change is the addition, modification, or removal of anything that could have an effect on IT services. Remember that all changes involve risk!

To initiate a change in the Change Management Process, a Request for Change (RFC) must be submitted. A Request for Change (RFC) is a documented request to alter a service or other Configuration Item (CI). RFCs are issued by customers, IT staff, users, or others, and are received by the Service Desk.