Gate 2 Checklist
1
Development is completed for all the features that are part of the release.
Yes
@ Pritish.Rath
Code was frozen by 10-01-2024.
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
All test cases are reviewed by the Product Owner and results have been updated in the sheet. QA sign-off is given accordingly.
3
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback.
Yes
Demo given on 20-12-2023 for PQM, and 02-01-2024 for Sanitation Worker.
4
UI/UX audit review by UX architect is completed along with feedback incorporation for any changes in UI/UX.
Yes
@ AndrewJones
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
Demo given on 20-12-2023 for PQM, and 02-01-2024 for Sanitation Worker.
6
QA sign-off is completed by the QA team and communicated to the product owners. All the tickets' QA sign-off status is updated in JIRA.
Yes
All test cases are reviewed by the Product Owner and QA sign-off is given accordingly.
7
UI, API technical documents are updated for the release along with the configuration documents.
Yes
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
All test cases are reviewed by the Product Owner.
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 analysed, 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.
Yes
ULB User: Search, Create, Update PQM Service: Adhoc Create, Search, Update PQM Quality Criteria
Automation script is reviewed by the Tech Lead.
10
The API backward compatibility testing is completed.
Yes
Tested on 05-JAN-2024.
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 sign-off within one week of this communication.
Yes
UAT sign-off was completed. Sign-off dates 10th JAN 2024 for PQM and Sanitation Worker Welfare.
12
The UAT product sign-off communication is received from the product owners along with the release notes and user guides (if applicable).
Yes
UAT sign-off was completed. Sign-off dates 10th April 2023 for PQM and Sanitation Worker Welfare.
13
The GIT tags and releases are created for the code changes for the release.
Yes
Added a new git tag V1.4
15
Verify whether all UAT builds are updated along with the GIT tag details.
Yes
All the budils are added with release tag V1.4
17
Verify whether all docs will be published to http://sanitation.digit.org by the Technical Writer as part of the release.
Yes
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
19
Verify whether the UAT credentials sheet is updated with the details of new users and roles, if any.
Yes
20
Verify whether all the localisation data was added in UAT, including Hindi, and updated in the release kits.
Yes
All localisations added as part of the release.
21
Verify whether the product release notes and user guides are updated and published.
Yes
22
The demo of the released features is done by the product team as part of the sprint/release showcase.
Yes
23
Technical and product workshops/demos are conducted by the engineering and product teams to the implementation team (Implementation handover).
Yes
Technical and product handover to impel conducted on 24-11-2023, and 04-01-2024. Signoff on handover is given on 11-01-2024
24
Architect sign-off and technical quality report.
Yes
Signed off on 02-Jan-2024.
30
Gate 2
31
The internal release communication along with all the release artefacts are shared by the engineering/product teams.
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.
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.
Last updated