Release Management PDF

Release Management Release management plays an important role in every software project since it is concerned with the delivery of a high quality product to end-users.  Release Management is the process of managing software releases from development stage to software rel...

Release Management Release management plays an important role in every software project since it is concerned with the delivery of a high quality product to end-users.  Release Management is the process of managing software releases from development stage to software release. «controls release of software & hardware to implement the change»  FREEZE & RELEASE  FREEZE : This is the process that the Projects which will be delivered to Production with the next RELEASE are separated from the other Projects and deployed to another test environment.  RELEASE : The Production deployment of the various Projects that are FREEZED on a certain date as a whole. Test Management  Test Deployment – What kind of things should be looked at after you have deployed a new system? – Things to check:  Check it deploys to right folder  Check deploying correct Clearcase,SVN  Check that the changes made our present and test for any bugs.  Check that deploy to Application after unit test  Performance Issues (slow, crashes etc)  Release Planning What are the systems? Is there a grouping of systems? How many releases? When to release? How much overlap? Release Planning What are the systems? Is there a grouping of systems? How many releases? When to release? How much overlap? Q1 05 Q2 05 Q3 05 Q4 05 Q1 06 J F MA M JJ A SO N DJ F M Release 1 Release 2 Release 3 Release 4  Release Plan Release contents & schedule Roll-out planning – Phasing over time and by geographical location, business unit and customers – Site surveys/audits – Obtaining quotes for new hardware, software or installation services Quality plan Back-out plans Acceptance criteria  Release Calender How can we create Release Deployment Calender? It shouldnt be same day with important flow executions ( exp.Billing Flow) It shouldnt be same day Financial Reporting It shoundnt be same day with traditional days It should be sunday night or thuesday night at 3 am.  Test Environments 1) Stable : After development complated, projects and FT code changes deploy stable enviroment for testing. 2) Preproduction :Before production deployment all freezed codes are testing via prp. 3) Bugfix : PRP test environment of High and Critical defects before release date.  LABEL : STB Test Environment Deployment FREEZE : If all tests are complated successfully, codes are ready for Pre Production Environment RELEASE : If Pre Production test executions are complated successfully, codes are ready for Production Developlent  Criteria for Deployment to PRP  Test Request ID with a status «Ready to PROD».  Test Set that is associated with the Test Request ID.  No Critical/High Test Defect that is associated with the Test Request ID.  All the Test Cases on the Test Set must be Run.  Min %90 of Test Cases on the Test Set must be successfully Passed.  TO_UCCSPROD labels on the coding. PRP Deployment COMPLETED Functional Test Complete COMPLETED Code Freeze COMPLETED Regression Test Complete COMPLETED Build COMPLETED Performans Test Complete COMPLETED GO/NOT GO COMPLETED Executive Approval COMPLETED RELEASE COMPLETED Release Manageme nt Release Management Tools