Release Checklist
Checklist | Yes/No/Partially | Reference link | Owner | Reviewer | Remarks |
Development is completed for all the features that are part of the release. | Yes | March 14th, 2023 | |||
Test cases are documented by the QA team, reviewed by the product owners, and test results are updated in the test cases sheet. | Yes |
| |||
The incremental demo of the features are showcased during the sprint showcase, and feedback is incorporated. If possible. list out the JIRA tickets for feedback. | Yes |
| February 16th, 2023 | ||
UI/UX audit review by the UX architect is complete along with feedback incorporation for any changes in the UI/UX. | Yes | UI/UX audit was done on February 22nd, 2023, and review comments are incorporated. | |||
Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes |
| February 22nd, 2023 | ||
QA sign-off is completed by the QA team and communicated to the product owners. The QA sign-off status is updated on JIRA. | Yes | QA sign-off was completed. Sign-off date was February 22nd, 2023. | |||
UI, API technical documents are updated for the release along with the configuration documents. | Yes |
| |||
UAT promotion and regression testing from the QA team is completed. The QA team has shared the UAT regression test cases with the product owners. | Yes | March 7th, 2023 | |||
API automation scripts are updated for new APIs or changes to any existing APIs for the release. The 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. | No |
| Not picked up in this release as the automation scripts are not ready, and the platform is yet to be decided. | ||
The API backward compatibility testing is completed. | Yes | Use-cases are run with the updated scripts. | |||
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 on March 7th, 2023. | |||
UAT product sign-off communication is received from the product owners along with the release notes and user guides (if applicable). | Yes | All modules are signed off, release notes and user guides are updated. The product sign-off happened on March 16th, 2023. | |||
The GIT tags and releases are created for code changes for the release. | Yes |
| |||
Verify whether the release notes are updated | Yes |
| |||
Verify whether all UAT builds are updated along with the GIT tag details. | Yes |
| |||
Verify whether all MDMS, configs, infra-ops and configs updated. | Yes | Added as part of the builds sheet. | |||
Verify whether all docs will be published to http://sanitation.digit.org by the technical writer as part of the release. | In progress |
| All documents will be published after the release as the product is not circulated with any external partners. | ||
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 |
| |||
Verify whether the UAT credentials sheet is updated with the details of new users and roles, if any. | Yes | UAT credentials shared internally to product and implementation teams. | |||
Verify whether all the localisation data was added in UAT, including Hindi, and updated in the release kits. | Yes |
| |||
Verify whether the product release notes and user guides are updated and published. | Yes | Release notes and user guides are published on the Gitbook. | |||
The demo of the released features is done by the product team as part of the sprint/release showcase. | Yes |
| Planned for March 31st, 2023. | ||
Technical and product workshops/demos are conducted by the engineering and product teams to the implementation team (implementation handover). | Yes | Migration process has been explained. The documents are added to the master migration document based on feedback from the impel team. | |||
Architect sign-off and technical quality report. | In progress |
| Conditional sign-off for zero pricing by Ghanshyam. Sign off for FSM registry and advance balance from Phani (former architect). | ||
Success metrics and product roadmap. | Yes |
|
| ||
Adoption metrics. | Yes | Adoption M=metrics added in the program roll-out page. | |||
Program roll-out plan. | Yes |
| |||
Implementation checklist. | Yes |
| |||
Implementation roll-out plan. | Yes |
| |||
The Internal release communication along with all the release artefacts are shared by the engineering/product teams. | In progress |
| Planned for March 31st, 2023. | ||
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. |
|
|
|
|
|
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
