Table of Contents
Advertisement
Change control
Change history archive
The change controller is also responsible for archiving the change history. Creating a
spreadsheet with functional group success and failure columns and month rows is sufficient for
archival. Change history archives can help identify current issues that are based on past
change rates and available resources. The information can also be used to investigate change
rates in general for overall planning purposes.
Change planning archive
The change controller should archive change planning documentation, such as network
engineering documents, to create a reference of examples for future successful projects. If the
change controller notices change problems, the controller can refer to the change planning
document to investigate how well the particular issue was documented before the change. Over
time, the change controller might ask to have additional information added to future change
planning documents for higher-risk changes to help ensure success.
Periodic performance meeting
Each month, it is important to review the metrics that you collect, including the following:
Change quantity and risk level
Change failure quantity and post mortems
Emergency changes and post mortems
Change management goals
Undocumented changes
The functional manager should review the metrics, and report to the appropriate teams for
improvement.
386 Avaya Application Solutions IP Telephony Deployment Guide
Advertisement
Table of Contents
