VisionPLUS GEGDC

Date: 3rd January 2008

*This document covers a generic process which may incorporate changes depending on specific GE Money business. For further information on site specific processes please refer to the project documentation

Release Management

Table of Contents

1. 2. 3. 4. 5. 6. 7. 8. 9.

INTRODUCTION ...................................................................................................... 2 SCOPE....................................................................................................................... 2 FLOW DIAGRAM ..................................................................................................... 3 ROLES & RESPONSIBILITIES ............................................................................. 4 TOOLS USED ........................................................................................................... 4 DELIVERABLES....................................................................................................... 4 GENERIC EXAMPLE .............................................................................................. 4 MEASURES & METRICES ..................................................................................... 4 REFERENCES ......................................................................................................... 4

GEGDC - VisionPLUS

Release Management 1. INTRODUCTION The Implementation Process takes places when a new functionality or a new enhancement is made to the existing system before it moves to production. The primary objective is to reduce the production issues. There are three categories for Implementations: 1. Minor Implementation Any development with effort less than or equal to 1 month is considered as minor implementation. All minor implementations must be planned or raised with sufficient lead time (2 weeks) so that the support teams have adequate time to review the implementation plan, test results, etc. 2. Major Implementation Any development with effort of more than 1 month is considered as major implementation. All major implementations must be planned or raised with sufficient lead time (3 weeks) so that the support teams have adequate time to review the implementation plan, test results, etc. Description of projects, application impact, detailed test results, Back-out plan, PVT plan, and Business sign off must be provided along with the implementation plan. Development Team should provide knowledge transition to the production support team along with the test cases, test results and abend log from the UAT. 3. Quick fixes & Emergency Changes This refers to any fix or change to the production system to restore a service or to prevent any issue which is business critical. They must have approval prior to implementation from Business. Quick fixes should be provided with a lead time of 24 hrs and Emergency changes are done immediately with proper approvals from the business. 2. SCOPE This document describes the production rollout Process and the understanding between GE Money and Satyam to highlight places of improvement to better control the Implementations. This document also covers porting of any new code to Production region for all projects including but not limited to Issue Resolution, Development, Enhancement, Conversion, Compliance and Version Upgrade Projects. It also suggests the action items from Satyam and GE Money, which would mitigate and thereby streamline the process for porting any code to the production region.

GEGDC - VisionPLUS

Release Management 3. FLOW DIAGRAM

Development Team

Production Team

Production Team

Production Team

Raise a Change Request

Clarification meeting & Sign Off

Deploy Change

Track the Change

Sub Process Outline the changes in detail Circulate the implementation document to the Business & Production Team

Sub Process Review the requested changes Prepare questions for the meeting Conduct meeting with Business and Development Team Final CR document to be reviewed by the Business Approval & sign off to be sought from Business & Satyam Onsite Team Leader Knowledge Transfer

Sub Process Implement the change Pre-implementation checklist to be followed Communicate with Business regarding the implementation of the change

Sub Process Record the changes in the Implementation Log Track the implemented changes

Following are the detailed steps in this process: 1. 2. 3. 4. 5. 6. 7. Business prepares the Requirements Document. The Development and Production team (Onsite) participates in the walkthrough with business to understand the requirements. Once the requirements are signed off, the Development team develops the Code and tests in the Development region. Development Team migrates the Code into SIT region after Business Approval using Changeman. Development team verifies the Code in the SIT region and executes the batch. Development Team closes any identified bugs in the SIT batch run. Business in coordination with Development team confirms the Testing of the code in SIT and approves the results. The code is then promoted to UAT region. Test batches are executed and a detailed test result log is prepared from the batch results (including any batch ABEND issues). Based on the Final Confirmation on the Test results in the UAT from the Business, the implementation plan is prepared and shared with all the Stakeholders involved in the project.

GEGDC - VisionPLUS

Release Management 4. ROLES & RESPONSIBILITIES After the necessary approvals from business, a change is implemented into Production as shown below: All the Control parameter changes done by business All the PROC/PARM/JCL/Control-M/CICS changes done by CSC in Production Region upon final approvals. All the source code changes done by Source Management team.

5. TOOLS USED Changeman for Source Code migration.

6. DELIVERABLES Formal and comprehensive training or involvement during UAT phase for the production support team on any major enhancements made to the system. Implementation Plan walkthrough. UAT test cases, test results, test batch abend log, test issues tracker sheet. Traceability matrix document for any changes made to the system, which would provide a mapping of all the functional specifications to the technical changes made. It also would serve as a handover document for the ownership change of the code from the development team to the production support team. Implementation Log

7. GENERIC EXAMPLE N/A 8. MEASURES & METRICES N/A 9. REFERENCES This is the link for the Pre-Implementation Checklist used by Satyam for reference by GE team. This will help the production support team understand the dependencies and identifies the action items on production support required for the implementation.

Pre Production Checklist for Productio

GEGDC - VisionPLUS