cmm asia application change management process

BUSINESS OPERATING PROCEDURETitle: Application Change Management

Process

DOCUMENT NO:PAGE:ISSUE DATE:REVISON DATE:PREPARED BY:APPROVED BY:

1 of 5March 29, 2007DRAFTHong Chan ChuenLim Hock Chee

1.0 SCOPE :

1.1 To establish and maintain a process to ensure that any authorized changes to the applications are coordinated and documented properly. All changes to the applications are subjected to the various test processes before the tested changes can be released to the production environment.

1.2 This procedure applies to all the applications managed by IT Department.

2.0 RESPONSIBILITY & AUTHORITY

2.1 Application Developer (ATS Developer / Vendor)Perform Unit Test and System Integrated Test

2.2 Authorized User Leads / Users / IT Personnel Submit Change Request Forms

Perform User Acceptance Test (UAT)Confirm Application release in the Production Environment

2.3 Application Owner/Project OwnerReview and Approve/Reject Change Request (Change Committee)Authorize Application Release to Production Environment

2.4 IT ManagementReview and Approve/Reject Change Request (Change Committee)IT Project ManagerRelease and Verify Application in Production Environment

2.5 CMM IT RepresentativeIT Project ManagerDeploy Application in Staging/Testing EnvironmentRelease and Verify Application in Production Environment

3.0 REFERENCES

3.1

4.0 PROCEDURE


Process



4.1 Change Request

4.1.1 Whenever there is any change request to the application system, the user lead will need to submit the change request to the corresponding Change Committee for approval.

The Change Committee consists of the Key Business Owner, IT Management.

Upon approval of the change request, the change request will be passed to the IT team to follow-up.

4.1.2 If the change request is rejected, it will be feedback to the user.

4.1.3 Certain application issues rectification will require modification to the programs.

4.1.4 All approved change requests will go through the Application System Development Life Cycle.

4.1.5 The Developer/Vendor needs to complete their respective unit test and system integration test based on the test scenarios defined in the test scripts.

4.1.6 When the system integration test has completed successfully, the new applications/patches/upgrades will be deployed into the testing/staging server for user to conduct the User Acceptance Test. The deployment to the testing/staging server will be done by the CMM IT Representative.

4.2 Staging/Testing Environment

4.2.1 The authorized user will proceed to perform the UAT on the new applications/patches/upgrades. Only when the UAT is successful, the authorized UAT user lead will signed off the UAT scripts. The UAT will also need to be approved by the Application Owner/Project Owner.

4.2.2 CMM IT Representative/IT Project Manager will plan the outage (If required) together with the Application Owner/Project Owner.

4.2.3 The Application Release Form must be sign-off and approved by the various parties.Authorized By: Application Owner/Project OwnerReleased/Verified By: CMM IT Representative / IT Project ManagerConfirmed By: User Lead


Process



** The CMM IT Representative/IT Project Manager is not a developer.

4.2.4 A backup of the affected programs and database (If required) will be performed by the IT Administrator.

4.2.5 CMM IT Representative will proceed to deploy the new applications/patches/upgrades into the production environment.

4.3 Production Environment

4.3.1 The User Lead will confirm the new release in the production environment

4.3.2 If there is no problem with the new release, the CMM IT Representative will announce the availability of the application to the rest of the authorized users.

4.3.3 All the control documents will be updated accordingly. Example: Issue Log, Change Request Log, Application Release Log.

For Vendor and Corporate IT Driven Applications (New Release):

4.4 Vendor New Release / Corporate New Release

4.4.1 The Vendor or Corporate IT announces new release for deployment.

4.4.2 CMM IT deploy to Staging/UAT Environment.

Repeat step 4.2 to 4.3In this case, the Application Release Log will be updated with the supporting release notes.


Process



PROCESS FLOW

A. Process Flow

Process Workflow (High Level)

6.0 Document History


Process



Version Date Description Originator

cmm asia application change management process

Documents