Change management is the practice of ensuring all CI alterations are carried out in a planned and authorized manner. Change can occur for various reasons including response to business process needs, the availability and introduction of new technologies, as well as normal business growth. Changes can be permanent or temporary. However, change management procedures should reduce and provide adequate responses to anticipated or unanticipated incidents as well as problems.
Receiving the request for change (RFC), logging the RFC, assessing the incident or problem, obtaining authorization to perform the change, and planning the change are procedures that should precede change construction. Minimally, the RFC should provide the business or technology reason behind each change; identify the specific CIs and IT services affected by the change; cost estimates; risk assessment; resource requirements; and support process approvals. Logging the change permits tracking and records the RFC has passed initial documentation requirements. Assessing the incident or problem provides analysis and evaluation enabling change prioritization and categorization. To construct the change, IT service support should obtain proper authorizations for the change from the appropriate business and technical experts responsible for change deployment. Furthermore, change planning provides the means to ensure successful change development.