Change Management
A change management process is designed to control and manage the propagation of software and infrastructure changes to a production environment. Different kinds of changes may warrant different refinements or variants of the process, depending on the nature of the changes and their potential impacts. This process prevents the uncoordinated changes that might not be in-line with the requirements outlined by the owners of the system. It also provides feedback into our project management allowing for proper planning for any changes to the system being developed.
The following practices are integral to a SlashRoot’s change management process:
-
Authorization—Any changes to the production environment should be subject to review by a responsible party within the organization. The depth of the review performed should align with the magnitude of the proposed change.
-
Auditability—The establishment of procedures for communicating requirements, changes and functionality related to their proprietary software and technical infrastructure. The team should also maintain a historical audit trail of material changes made to their proprietary software, allowing them to accurately determine:
-
When a change was made
-
Who made the change
-
The nature of the change
-
Document Management tools have added features that allow for clear and easy document auditing. One such recommended tool is Google™ Drive.
