Planning implementation of change requests

The Change Assessment, Planning, and Scheduling stage, is one of the most important stages of the change control process. In this stage, the Change Manager, Coordinator, and Implementers plan a forward schedule of changes (FSC). They perform the following key activities:

• Plan all the requests approved for implementation, set target dates, and estimate the risks and costs involved. 
• Change impact analysis and re-evaluation of risk, if needed.
• Create key documents that can include:
  • Build or development plan
  • Test or QA plan
  • Install plan
  • Backout plan (This document is most important as it describes how to successfully get back to a working state again, in case of any failure.)
• Create, assign, and schedule the implementation tasks.
• Schedule the change request.
• Review the implementation approvers, as required.

For more information, see Planning change requests in the Assessment, Planning, and Scheduling stage in theBMC Helix ITSM: Change Management online documentation portal.

To plan the implementation of a change request

For more information, see Planning implementation of a change request in theBMC Helix ITSM: Change Management online documentation portal.

To detect collisions between change requests

A collision occurs when a CI is related to two or more change requests whose implementation schedules overlap. Change Management detects collisions between change requests automatically, and helps you to make decisions to manage and resolve the potentially harmful conflicts between these change requests. 

For more information, see Detecting collisions between change requests in theBMC Helix ITSM: Change Management online documentation portal.