Gate 2 Release Checklist
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
# | Checklist | Sign-off Status | Reference link | Owner | Reviewer | Remarks |
---|---|---|---|---|---|---|
1
Development is completed for all the features that are part of the release.
Yes
Shailesh and Subhashini
Sathish P
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
Vasanth
Nirbhay, Subhashini
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
Vasanth
Nirbhay
4
UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX.
Yes
Jagan
Andrew
5
Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated.
Yes
Vasanth
Nirbhay
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
Vasanth
Sathish P
7
UI, API Technical documents are updated for the release along with the configuration documents.
Yes
Jagan, Shailesh and Subhashini
Sathish P
8
UAT promotion and regression testing from the QA team are complete. The QA team has shared the UAT regression test cases with the product owners.
Yes
Vasanth
Nirbhay
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
Vasanth/Subhashini
Karate Automation is not taken up in this release due to time constraints.
10
The API backward compatibility testing is completed.
No
Vasanth
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
Vasanth
Nirbhay
QA Sign off given on below dates August 21st 2023 August 25th 2023
12
UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable).
Yes
Nirbhay
Prashanth
13
The GIT tags and releases are created for the code changes for the release.
Yes
Shailesh and Subhashini
Sathish P
14
Verify whether the Release notes are updated
Yes
Shailesh and Subhashini
Sathish P
15
Verify whether all UAT Builds are updated along with the GIT tag details.
Yes
Vasanth, Shailesh and Subhashini
Sathish P
16
Verify whether all MDMS, Configs, InfraOps configs updated.
Yes
Vasanth
Subhashini/ Jagan
17
Verify whether all docs are published to Works website by the Technical Writer as part of the release.
Yes
Nirbhay, Shailesh, Jagan, Sathish P, Subhashini, Vasanth, Shivani, Arindam, Anjoo
Anjoo
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 Product owner.
Yes
Vasanth
Nirbhay
19
Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any
No
Vasanth
Jagan
It will be internally shared
20
Verify whether all the localization data was added in UAT including Hindi and updated in Release Kits.
Yes
Vasanth
Jagan & Sathish P
21
Verify whether the product release notes and user guides are updated and published
Yes
Nirbhay
Prashanth
22
The Demo of released features is done by the product team as part of the Sprint/Release Showcase.
Yes
Nirbhay
Release showcase was conducted on 1st Sept 2023.
23
Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Impel handover)
Yes
Shailesh, Subhashini and Nirbhay
Arindam
Implementation handover done on - 19 July, 29 Aug 2023.
24
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.
No
No demo environment present for works hence not applicable for now.
25
Architect SignOff and Technical Quality Report
Yes
Subhashini
Ghanshyam
Issues are documented in Known Issues. Also documenting this in JIRA for tech debt fixes.
26
Success Metrics and Product Roadmap
Yes
Nirbhay
Prashanth
27
Adoption Metrics
Yes
Nirbhay
Prashanth
28
Program Roll-out Plan
Yes
Shivani
Prashanth
29
Impel checklist
Yes
Arindam
Elzan
30
Impel roll-out plan
Yes
Arindam
Elzan
31
Gate 2
In progress
Shivani, Nirbhay, Sathish P, Arindam
Ex co
Gate 2 is scheduled on 4th Sept 2023
32
The Internal release communication along with all the release artefacts are shared by the Engineering team.
Nirbhay and CK
This will be shared after Gate 2.