Two sprints before feature freeze (173)
Action | Responsible | Status |
---|---|---|
| Product owner | |
All user stories tied to features should be written and estimated. | Product owner | |
Testing
| Team | |
Conduct user acceptance testing |
| |
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 |
One sprint before feature freeze (174)
Action | Responsible | Status |
---|---|---|
| Product Owner | |
| Team | |
Migration/module upgrade documentation checklist Migration Plan
Migration Testing
| Team | |
Any breaking changes? | Team | |
Re-Indexing for release upgrade? For bugfest? Consortia test environment?
| ||
| PO and Dev lead | |
Accessibility Testing
| Team | |
| Team | |
Document Potential Risks and Risk Mitigation Plan | Team |
Feature freeze sprint (175)
Action | Responsible | Status |
---|---|---|
| Product Owner | |
| Team | |
| PO and Dev lead | |
Accessibility Testing
| Team | |
| Product Owner writes user stories. TBD who will conduct. |
Sprint before Bugfest (aka Business Acceptance Testing) period (176)
Action | Responsible | Status |
---|---|---|
| Product Owner | |
| Product Owner | |
| Team | |
| PO and Dev lead | |
| Team | |
Team meets with Kitfox to review upgrade instructions. Team's accept Bugfest build. Need to consider Consortia support.
| Team | |
Regression testing? | QA? | |
| Product Owner writes user stories. TBD who will conduct. |
Sprint before GO-Live (178)
Action | Responsible | Status |
---|---|---|
| Product Owner | |
| PO and Dev lead | |
| Product Owner writes user stories. TBD who will conduct. |
Go-Live sprint
Action | Responsible | Status |
---|---|---|
Teams must conduct smoke tests to verify key functionality works as expected | Team | |
Testing: All Karate tests and e2e tied to release functionality should be done and running | Team | |
| PO and Dev lead |