Steps of a Formal Change Control System
- A problem and or defect is discovered.
- A change request is logged.
- The change is either implemented immediately e.g. security patches ... or the request goes through an approval process.
- The change is scheduled.
- Change is implemented (in a production environment alone or a dev environment first) and all necessary documentation is attached to the change request.
- The assignee verifies that the expected outcome is achieved.
- Handoff for UAT.
- Release new feature or product to customer.
An early introduction and acceptance of change control in an organization proves to be beneficial, because a lot of the things people usually complicate would be simplified and in turn uncomplicated. The establishment of a change control system should be a company-wide effort. All departments who the change might affect should be aware and kept up to date on any changes. It's simple, if problems are addressed, then you can always guarantee successful change control.