Tag: Change Control

  • Change Management

    Change control within is a formal process used to ensure that changes to a product or system are introduced in a controlled and coordinated manner. It reduces the possibility that unnecessary changes will be introduced to a system without forethought, introducing faults into the system or undoing changes made by other users of software. The goals of a change control procedure usually include minimal disruption to services, reduction in back-out activities, and cost-effective utilization of resources involved in implementing change. Change control is a major aspect of the broader discipline of change management.

    The following is an example of a change control process:

    Minimize Disruption

    • Work during off or down time.
    • Test changes first (if possible) and/or roll out to limited group first.
    • Notify users who will be affected and/or front-line staff.

    Reduce Any “Back-out” Time Activities

    • Create/save back-ups of any files changed.
    • Record what files are being changed any configuration changes to settings or within files.

    Efficient Utilization of Employees

    • Empower affected users and/or front-line staff to give feedback on any issues and/or improvements.
    • Have the most experienced person with the system make the changes.

    Review Process

    Before

    • Why is the change being made?
    • Is the change approved? By who?

    After

    • What was the effect? Was it the desired outcome or something different?
    • Do we need to roll back the changes?

    Report Process

    • What metrics to report?
    • Report to who?
    • How often to report?
    • Suggest or ask for needed or wanted changes.