Gate 2 Release Checklist
DIGIT 2.9 Gate 2 Release Checklist
1
Development is completed for all the features that are part of the release.
Yes
@Kaviyarasan P
@Kaviyarasan P
Code is frozen by APR-2023
2
Test cases are documented by the QA team, and reviewed by the product owners and test results are updated in the test cases sheet.
Yes
@Gurjeet Singh
@Priyanka Samantaroy
No new test cases for central instance are there. All existing test cases should work as is.
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
Demo given on 18-APR-2023 for Citizen Feedback Citizen Consent Form DSS New KPIs. Central Instance - No demo required.
4
UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX.
Yes
@Andrew Jones
@Vamshikrishna Kole
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
@Megha S @P. Sankar
@P. Sankar
Demo given on 18-APR-2023 for Citizen Feedback Citizen Consent Form DSS New KPIs. Central Instance - No demo required.
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
@Gurjeet Singh
QA signoff was completed. Sign-off dates 14th April 2023 Citizen Feedback Citizen Consent Form DSS New KPIs Central Instance - 15th September 2023
7
UI, API Technical documents are updated for the release along with the configuration documents.
Yes
@Kaviyarasan P
@Vamshikrishna Kole
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
@Gurjeet Singh
No new test cases for central instance are there. All existing test cases should work as is.
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
@Gurjeet Singh
Not picked up in this release due to lack of resources. We do not have QA resource who can write automation scripts.
10
The API backward compatibility testing is completed.
Yes
@Gurjeet Singh
@Kaviyarasan P
Tested on 25-AUG-2023
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
@Gurjeet Singh
@KeerthiBhaskara-eGov
@Megha S
UAT signoff was completed. Sign-off dates 14th April 2023 Citizen Feedback Citizen Consent Form DSS New KPIs
Central Instance- No communication required
12
UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable).
Yes
@Megha S
@P. Sankar
UAT product signoff for Citizen Feedback Citizen Consent Form DSS New KPIs
given on 19th April 2023
Central Instance - UAT product signoff not needed. Central Instance is a separate environment
13
The GIT tags and releases are created for the code changes for the release.
Yes
@Priyanka Samantaroy
@Kaviyarasan P
14
Verify whether the Release notes are updated
Yes
@Priyanka Samantaroy
@Kaviyarasan P
15
Verify whether all UAT Builds are updated along with the GIT tag details.
Yes
@Priyanka Samantaroy
@Kaviyarasan P
16
Verify whether all MDMS, Configs, InfraOps configs updated.
Yes
@Priyanka Samantaroy
@Kaviyarasan P
17
Yes
@Kaviyarasan P,
@Pradeep Kumar,
@Ajay Rawat, @Megha S
@Anjoo Narayan
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
@Gurjeet Singh
No new test cases for central instance are there. All existing test cases should work as is.
19
Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any
Yes
@Gurjeet Singh
No new credentials required for - Citizen Feedback Citizen Consent form DSS New KPIs
New credential for Central Instance Attached
20
Verify whether all the localization data was added in UAT including Hindi and updated in Release Kits.
Yes
@Priyanka Samantaroy
@Kaviyarasan P
No new localization added for the central instance
21
Verify whether the product release notes and user guides are updated and published
Yes
Product Owners
22
The Demo of released features is done by the product team as part of the Sprint/Release showcase.
Yes
Demo given on 18-APR-2023 for Citizen Feedback Citizen Consent Form DSS New KPIs. Central Instance - No demo required.
23
Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Implementation handover)
Yes
@Kaviyarasan P
@Kaviyarasan P
Technical and Product workshops/demo conducted on 23-July-2023
24
Architect SignOff and Technical Quality Report
Yes
@Kaviyarasan P
@Ghanshyam Rawat
Signed off by @Kaviyarasan P on 31-July-2023
25
Success Metrics and Product Roadmap
Yes
@Ajay Rawat
26
Adoption Metrics
Yes
@Ajay Rawat
27
Program Roll-out Plan
Yes
@Ajay Rawat
@Pradeep Kumar
28
Implementation checklist
Yes
@Pradeep Kumar/@Vinoth
Prepared.
29
Implementation Roll-out plan
Yes
@Pradeep Kumar/@Vinoth
30
Gate 2
Yes
@Ajay Rawat
31
The Internal release communication along with all the release artefacts are shared by the Engineering/Product team.
Yes
@Priyanka Samantaroy
@Kaviyarasan P
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.
Yes
@Pradeep Kumar/@Vinoth
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.
No
