CHANGE REQUEST IN APPLICATIONS

Change requests are raised so that the business works in a well-mannered way. Change request in application should be managed in such a way that everyone involved understands the changes to be made their importance and impact on other Business Users and applications. If these change requests are not handled properly then it may significantly affect the business.

Steps for executing a Change Request in Application:

It includes initiation, review, plan, implementation and close. This steps can be explained in detail as follows:

STEP 1: Determining the Scope of the Change

• This step includes understanding the requirement of the Change request and how it can be helpful to the business.
• The requirements should be analysed. Also the benefit for making a change should be known.

STEP 2: Reviewing a Change Request

• Understanding the Change request and respective change is very important
• Change requests are generally of two types viz: Standard Changes and Non-Standard changes
• Standard changes are pre-approved changes which are raised on a regular basis and can be executed with any further approvals. Normally, these are small changes and require less effort
• Non-Standard changes are generally enhancements which can impact other applications and Processes. Hence, these changes are discussed in forums (CAB Calls) for approval from the impacting Business users and Decision makers of the Organization
• Hence, Application support team should be able to review the changes correctly and follow the correct process based on the type of the change.

STEP 3: Approval or Rejection

• The Non-standard changes request has to be presented to the change advisory board team.
• The change request may be a low level or minor change request or it can be a high level or major change request
• The change request gets approved by the higher authorities
• The time for approval depends on whether the change request is major or minor
• Ideally the approving team understands the Business benefit of the change from the Requester (Business User), its impact on other applications and the cost and time that will be incurred to develop and implement the respective change request

STEP 4: Communication and Implementation

• The below shown flowchart explains the step 4 in detail:

 Team members should communicate with the higher authorities

Change request should be approved by the higher authorities

Project team needs to be identified and notified

 The project deliverables should be updated

Change request should be implemented and closed

 Conclusion:

• A ticket should be raised for the change request in Application.
• The change request in applications should be proposed only if required.
• Change request should be made considering the time requirement, efforts, process etc.
• After the implementation, the change request should be closed.

About Author:
Mikhil Chauhan is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, he actively contributes to the areas of Technology and Information Security. He can be contacted at: mikhil.chauhan@spluspl.com