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.
...
Story for release are detailed, completed and closed (before code freeze) | Almost a Go; issue in this ticket
| Done | 12th June | parent=rcf-31 and issuetype=story and fixVersion=RCF-0.10.0 | ||||||||
Pending task/story is segregated (before code freeze) | Done | 12th June | ||||||||||
Country reported bug has been listed and triaged | NA | NA | ||||||||||
All tasks “fix version“ is in line with the release number (before code freeze) | Done | 12th June | ||||||||||
Open bugs has been triaged (before code freeze) | Done | 3rd June | ||||||||||
Known bugs are listed in release notes (before code freeze) | Done | 3rd June | parent=rcf-31 and issuetype=bug and status not in (closed, Canceled) | |||||||||
Test cases are reviewed (1 month before release) | Done | 24th April | ||||||||||
UI workflow is reviewed as per the design (1 month before release) | Done | 24th April | ||||||||||
UX is in compliance with MOSIP standard (before code freeze) | Done | 24th April | ||||||||||
APIs are developed as per the requirement (before code freeze) | Done | 24th April | ||||||||||
Posted the invite on community for external demo (a couple of days before the release) | Pending | Planned for 2nd July21st June |
Legend
| Anchor | ||||
|---|---|---|---|---|
|
The list of tasks against which the status needs to be updated. Since it’s a template, go ahead to add/modify as required
...