the given settings and planned run schedules.
In Stage 4, The RM team gets the approval of the DBA team w.r.t the database impacts of the release of the software code into the Production environments. This approval focuses on the performance aspects of the software code at points where it interacts with the database.
In Stage 5, Once the RM team gets an approval from the QA , Production Support and DBA teams , the RM team presents the release of this software code to the Change Control/Request Board (CCB) for approval of the release of this software code into production. This approval focuses on the Enterprise level impacts of the release of this software code into production.
In Stage 6, The RM team performs the relevant Configuration Management processes for complying with the Release after the Change Control Board approves the release of the software code into Production.
In Stage 7, The RM team co-ordinates with the Operations team to release the software code into the Production environment.
Shown below is the RM process flow diagram:
Finally in Stage 8, Post the release of the software code into Production, the RM team (in conjunction with the Development team) monitors the behaviour of the newly released Job/Software code in Production for a period of "N" consecutive successful runs. After "N" successful runs, the RM team flags off the release as a success and hands over the support of this job/software code (in conjunction with the Development team) to the Production Support team.
The RM team profile
The RM roles that can be defined are Release Coordinator , Release Manager.
The RM responsibilities can include:
- Being well versed with the various documentations and artifacts needed to be presented to the Change Control Board
- Represent the Software Group to the Change Control Board
- Enforce the various Release Guidelines and Processes internally with the Development , QA , Production Support and DBA teams
- Interact with the Operations team for the physical code release process ( i.e migration processes ) into the Production environment
- Being well versed with the various Operating systems , the programming languages and software that is being used to develop the software code
- Equipped with positive and aggressive communication skills
Tracking the RM process
The RM team can track the status of the various software codes being released into Production by using a Dashboard. This Dashboard can give information like Name of the Software Code, The Developer who developed it ,The Software Group he belongs to,The Development team member who gave the KT to the RM team member ,The RM team member who performed the RM process The approval status of the QA, DBA, Production Support teams, The approval datetime and status of the Change Control Board ,The status of the software code after the release/migration into Production, The status/history of the software code until the "N" successful runs are achieved, The Handover status of the software code to the Production Support team .
The RM team also carries out a periodic analysis of the status of the various software code releases that were done. Based on the analysis, the RM team gives a constant feedback and learning experiences, back to the Development, QA, Production Support and DBA teams, which in turn helps them to improvise their internal approval and documentation processes.
Critical Success Factors for the successful implementation of the RM process
The most important factor for the successful implementation of the RM process is the management buy-in and support for a dedicated staff to perform the RM function.There should be a willingness of IT staff to perform this
|An Effective Production Rollout using a Hub-N-Spoke Release Management Process||103 KB|