Business Analyst (BA) of the project to ensure all the below checklist tasks are performed and the status is updated before the Go/NoGo release call.
Owner : Pragya
Story for release are detailed, completed and closed (before code freeze) | |||
Pending task/story is segregated (before code freeze) | |||
Country reported bug has been listed and triaged | |||
All tasks “fix version“ is in line with the release number (before code freeze) | |||
Open bugs has been triaged (before code freeze) | |||
Known bugs are listed in release notes (before code freeze) | |||
Test cases are reviewed (1 month before release) | |||
UI workflow is reviewed as per the design (1 month before release) | |||
UX is in compliance with MOSIP standard (before code freeze) | |||
APIs are developed as per the requirement (before code freeze) | |||
Posted the invite on community for external demo (a couple of days before the release) |
|
Legend
Tasks:
The list of tasks against which the status needs to be updated. Since it’s a template, go ahead to add/modify as required
Status:
Go - Go ahead from the stake holder to release for a given stream
NoGo - Stake holder does not want the release to go for a given stream
In-progress - Work is in progress to provide final decision for a given stream
NA - Specific part of section is not applicable for this release for a given stream
Status Date:
Enter the date when the Status was provided for a given stream
Comments:
Enter the comments as relevant for a given stream