| Action | Responsible | Status |
|---|
- Update Features' statuses
- Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
- Clean up Poppy backlog
| Product owner |
|
- All user stories tied to features should be written and estimated.
| Product owner |
|
Testing - Identify features that require e2e tests
- Identify features that require Karate tests
| Team | Need Karate tests for consortia > Action item to create consortia specific Karate tests stories. So no expectation that these stories will be ready for Dev freeze and for Go-Live? We probably need a "Q" feature? Will determine based on dependencies? What about consortia specific e2e tests > TBD but not considered for Poppy. |
- Conduct user acceptance testing
| - Product owner (maybe a SIG member can help write tasks?)
- Team needs to setup an environment for UAT
|
|
- Conduct or create user stories for performance/load testing. See
Types of tests | Product Owner writes user stories. TBD who will conduct. |
|
- Document Potential Risks and Risk Mitigation Plan
| Team |
|