Change Control Process

The Change Control Process includes the following steps:

The requirement for change or modification may arise as a result of customer feedback, bug reports, or business requirements, among other things.

Step 1: Identifying, Analyzing the Impact, and Initiation of Change Request

• The support team will identify the need for the change.
• The support team and development team will assess the possible impact on customers and make sure all appropriate safeguards are put in place to limit interruptions to their business operations prior to making any changes. This might entail informing clients of the changes beforehand, offering them training or assistance, and creating backup plans for potential problems.

Step 2: Change Request Evaluation

• The Change management team will evaluate the change request to ascertain its practicality, its effect on the system, and the resources needed.
• It will then either be authorized or refused by the Change Control Board.

Step 3: Change Management Strategy

• The modification will then be scheduled for execution after it is approved.
• The Change Control Board will form teams for all the tasks to be carried out.
• A change log that includes the date, the identity of the team who made the changes, and the modifications that were made will be maintained.
• Changes will only be made by an authorized development team or Senior Software Developer.
• Test cases will be written by the testing team.
• A method for reverting to an earlier version will also be listed.

Step 4: Test Cases

• The documentation team will make documents regarding the changes to be carried out.

Step 5: Change Implementation

• The Senior Software Developer will then carry out the implementation using the accepted standards.
• Before being implemented in the production environment, the modifications will be extensively tested by the testing team.
• The testing team will carry out the tests and check if everything is working properly.
• When the modification is put into place, it will be examined by the Change Control Board to make sure it complies with business needs and doesn't cause any new problems.

Step 6: Documentation

• The documentation team will form a document regarding the changes carried out. This documentation would in turn help out the customers under the changes carried out in a better way.
• The documentation can be in the form of a setup guide, article, blog, or email.

Step 7: Closure of Change Request

• The modification or changes will be closed when it has been confirmed.

Note: Changes are limited to app code, configurations, and admin-defined settings; no access to customer data beyond app scopes is performed. Documentation does not include sensitive user credentials or other PII.