Sl No | Checklist | Yes/No/ Partially | Reference link | Owner | Remarks | |
1 | Development is completed for all the features that are part of the release. | Yes | Kapil Gupta | |||
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 | Madan | |||
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 | Vehicle logging at FSTP decoupled from FSM module Unrestricted assignment of service requests to a single vehicle | Madan / Kapil / Satbir | The sprint/release showcase is scheduled for 12th Aug 2022. | |
4 | UI/UX Audit review by UX Architect is completed along with feedback incorporation for any changes in UI/UX. | Yes | Nabeel / Antriksh | UI/UX audit feedbacks is done on 20th June 2022. Majority of findings are common component observations and FSTPO screen observation. Rest of the Audits are from previous release. | ||
5 | Incremental demos to the product owners are completed as part of the sprint and feedbacks are incorporated. | Yes | Kapil / Satbir | Multiple Incremental demos were completed during the sprint cycle. But there was no end to end to flows are completed. | ||
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 | Madan | QA signoff was completed on the 29th of July 2022. | ||
7 | UI, API Technical documents are updated for the release along with the configuration documents. | Yes | Nabeel / Kapil | These docs will be Published to Gitbook within 2 working days of the release. | ||
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 | Madan | |||
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 | Madan |
| ||
10 | The API backward compatibility testing is completed. | No | Madan | No shared services APIs are changed in the current release for FSM. This release is bundled with the DIGIT 2.7 release and backward compatibility testing is completed for DIGIT 2.7. | ||
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 | Madan | UAT regression signoff was completed on the 22th of July 2022. | ||
12 | UAT Product Signoff communication is received from the Product owners along with the release notes and User guides (if applicable). | Yes | Vyshnavi | Signoff received on 29th Mar 2022. | ||
13 | The GIT tags and releases are created for the code changes for the release. | In Progress | fsm_v1.1 [TBD] | Kapil Gupta | updated once Gajendran C (Unlicensed) sync digit-dev mater repo to digit-oss | |
14 | Verify whether the Release notes are updated | Yes | Kapil Gupta / Satbir | |||
15 | Verify whether all UAT Builds are updated along with the GIT tag details. | Yes | Kapil Gupta | |||
16 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | Madan | |||
17 | Verify whether all docs will be Published to http://docs.digit.org by the Technical Writer as part of the release. | Anjoo Narayan | These docs will be Published to Gitbook within 2 working days of the release | |||
18 | Verify whether all test cases are up to date and updated along with necessary permissions to view the test cases sheet. | Yes | Madan | |||
19 | Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any | Yes | Madan | |||
20 | Verify whether all the localization data was added in UAT including Hindi and updated in Release Kits. | Yes | Madan | |||
21 | Verify whether the product release notes and user guides are updated and published | Yes | Vyshnavi | |||
22 | The Demo of released features is done by the product team as part of the Sprint/Release showcase. | No | Vyshnavi | The sprint/release showcase is scheduled for 12th Aug 2022. | ||
23 | Technical and Product workshops/demos are conducted by the Engineering and Product team based on the need from the implementation team and partners. | In Progress | The Product and Tech workshop will be arranged after the release communication. Tentative date is 5th to 8th Aug 2022. | |||
24 | Architect SignOff and Technical Quality Report | 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 | 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 | https://app.gitbook.com/o/-MEQmzNGXk5ajuZujG7E/s/UYtUmELy66UydIQtJOn5/~/changes/61/platform/release-notes https://digit-discuss.atlassian.net/wiki/spaces/DD/pages/2307457051/Program+Roll+Out+Plan#Adoption-Metrics | Adoption Metrics added in Program Roll Out Page | |||
27 | Program Roll-out Plan | |||||
28 | Implementation checklist | Yes | Prepared. | |||
29 | Implementation Roll-out plan | Yes | Will upgrade to UPYOG first by March 27th. | |||
30 | Gate 2 | Inprogress | planned on 20th-Feb-2023 | |||
31 | The Internal release communication along with all the release artefacts are shared by the Engineering/Product team. | Inprogress | After Gate 2 communication will be released | |||
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 | After upyog upgradation, will start this task after getting confirmation from marketing team. | |||
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. |
General
Content
Integrations
0 Comments