Walkthru of the Release Management Process
The request for change in application is procured by the Business, depending upon the nature of change such as performance enhancements or addressing any ongoing or critical issues.
A Release scope document is, then, handed over to Release Management which comprises of the list of changes and their criticality. Based on such a request a GCM is created, and is kept in Draft status until the timelines and deployment order are finalized.
A meeting is commenced between all the teams (especially Development, Testing, Deployment and Service Operation) in order to discuss the timelines of various milestones (DEV, SIT, UAT, etc.), Support Matrix, Technical Handovers and other important aspects related to the release.
Once the development commences, we monitor the progress by scheduling periodic calls with Development team and Business. Upon completion of Development, the code is pushed to SIT environment for System Integration Testing. Based on the test case document shared by the testing team before the commencement of testing, SIT & Regression testing is carried out. Any bugs encountered during SIT are referred to DEV in order to fix the particular component. Once the issue is fixed, the specific component undergoes the SIT once again and the testers sign-off the SIT after a successful test completion.
Meanwhile, a draft version of the production deployment plan is prepared by the Release Manager with the help of Deployment Team and Application Services. This includes the migration order instructions handover from Application Services to Deployment Team. And Monitoring Checklist handover from Application Services to Service Operations team (L2/L3).
Upon completion of SIT, the code is pushed to UAT environment for User Acceptance Testing. UAT is carried out and any bugs/issues encountered during the testing are referred to DEV. Upon fixing the issue, the specific component undergoes SIT and later reaches...
Please join StudyMode to read the full document