Gate 2 Release Checklist
@Sl No | Checklist | Yes/No/Partially | Reference link | Owner | Reviewer | Remarks |
1 | Development is completed for all the features that are part of the release. | Yes |
| Kaviyarasan P | Sathish P | Code was frozen on 10-Feb-2023 |
2 | Test cases are documented by the QA team, reviewed by the product owners and test results are updated in the test cases sheet. | Yes | Navyashree G Keerthi Bhaskara | P. Sankar | Test cases documents are reviewed and updated | |
3 | The incremental demo of the features showcased during the sprint showcase and feedback incorporated. If possible list out the JIRA tickets for feedback. | Yes |
Kaviyarasan P | P. Sankar Nirbhay Singh | Yes, incremental demos are shown during the development sprints. | |
4 | UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX. | Yes | JaganKumar Antriksh Kumar Vamshikrishna Kole | P. Sankar | UI/UX audit is done and review comments are incorporated. | |
5 | Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes | Kaviyarasan P | P. Sankar | Incremental demos are done as per sprint | |
6 | QA signoff is completed by the QA team and communicated to the product owners. All the tickets QA signoff status is updated in the JIRA. | Yes |
| Navyashree G Keerthi Bhaskara | P. Sankar | QA signoff was completed. Incremental sign-off dates 3rd Nov 2022
13th Dec 2022
2nd Feb 2023
|
7 | UI, API Technical documents are updated for the release along with the configuration documents. | Yes | Kaviyarasan P Vamshikrishna Kole |
| Featured in the release page and master migration document | |
8 | UAT promotion and regression testing from the QA team is completed. QA team has shared the UAT regression test cases with the product owners. | Yes | Navyashree KeerthiBhaskara-eGov |
P. Sankar | ||
9 | API Automation scripts are updated for new APIs or changes to any existing APIs for the release. API automation regression is completed on UAT, the automation test results are analyzed and necessary actions are taken to fix the failure cases. Publish the list of failure use cases with a reason for failure and the resolution taken to fix these failures for the release. | No |
| Navyashree G KeerthiBhaskara-eGov |
| Not picked up in this release due to lack of resources |
10 | The API backward compatibility testing is completed. | Yes | Navyashree G | Kaviyarasan P | Use cases ran with the existing scripts, no new API structure changes in the new release. new scripts for 2.8 will taken up in upcoming sprints | |
11 | The communication is shared with the product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a Product signoff within one week of this communication. | Yes |
| Navyashree G Keerthi Bhaskara | P. Sankar | UAT sign-off was completed. Incremental sign-off dates 13th Dec 2022
6th Feb 2023
6th Jan 2023
12th Jan 2023
9th Feb 2023
|
12 | UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable). | Yes | Kaviyarasan P Product Owners | P. Sankar | All prods are signed off , release notes and user guides are updates
| |
13 | The GIT tags and releases are created for the code changes for the release. | Yes | Kaviyarasan P | Sathish P |
| |
14 | Verify whether the Release notes are updated | Yes |
| Kaviyarasan P | Sathish P |
|
15 | Verify whether all UAT Builds are updated along with the GIT tag details. | Yes | Kaviyarasan P | Sathish P |
| |
16 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | Kaviyarasan P | Sathish P |
| |
17 | Yes |
| Kaviyarasan P Anjoo Narayan | Sankar Sathish P |
| |
18 | Verify whether all test cases are up to date and updated along with necessary permissions to view the test cases sheet. The test cases sheet is verified by the Test Lead. | Yes | Navyashree G Keerthi Bhaskara | Sankar |
| |
19 | Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any | Yes | Navyashree G Keerthi Bhaskara | Sankar | UAT creds shared internally to product & impel team | |
20 | Verify whether all the localisation data was added in UAT including Hindi and updated in Release Kits. | Yes | Navyashree G Keerthi Bhaskara | Kavi |
| |
21 | Verify whether the product release notes and user guides are updated and published | Yes | Nirbhay Singh Satish N Chandra Kiran Sankar Abhishek | P. Sankar | Release notes and user guides are published in gitbooks. | |
22 | The Demo of released features is done by the product team as part of the Sprint/Release showcase. | Yes | Nirbhay Singh Satish N Chandra Kiran Sankar Abhishek | P. Sankar | Yes - all features of 2.8 are demoed to the eGov team on 15th Feb 2023 | |
23 | Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Implementation handover) | Yes |
| Kaviyarasan P | Pradeep Kumar | Migration process has been explained, all docs are added to the master migration doc based on feedback from impel team |
24 | Architect SignOff and Technical Quality Report | Yes |
| Kaviyarasan P | Kaviyarasan P | Sign off is given with privacy disabled and encryption process disabled for W&S, PT modules. Redesign of privacy will be taken up by DPG based on the shortcomings shared in Tech council. |
25 | Success Metrics and Product Roadmap | Yes | Nirbhay Singh P. Sankar | Sankar | Product road map post digit 2.8 is not clear yet as we have less visibility and trimming down the operations/resources in urban team. | |
26 | Adoption Metrics | Yes | Ajay Rawat P. Sankar | Sankar |
| |
27 | Program Roll-out Plan | Yes | Ajay Rawat | Chandar |
| |
28 | Implementation checklist | Yes | Pradeep Kumar | Elzan |
| |
29 | Implementation Roll-out plan | Yes | Pradeep Kumar | Elzan |
| |
30 | Gate 2 | In-progress | Meeting scheduled on 20th Feb 2023 | Kaviyarasan P, Sathish P, Pradeep Kumar, Ajay Rawat, Sankar, Satish N, Nirbhay Singh, Anjoo Narayan | Approver will be added post meeting | |
31 | The Internal release communication along with all the release artefacts are shared by the Engineering/Product team. | In-progress |
| Kaviyarasan P, Sankar P, Sathish P | Sankar | Communication will be shared once Gate 2 is passed |
32 | Plan for upgrading the staging/demo instance with the release product - within 2-4 weeks based on the period where no demos are planned from staging for the previous version of the released product. |
|
| Pradeep Kumar | Elzan | Staging will be upgraded after the release |
33 | The Release communication to partners is shared by the GTM team and the Webinar is arranged by the GTM team after the release communication - within 2-4 weeks of the release. |
|
| Vibhor Bansal |
|
|
Last updated
