Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Two sprints before feature freeze 

Action
CategoryTimeframeResponsible
  •  Type your task here, using "@" to assign to a user and "//" to select a due date
Responsible
  • Update Features' statuses
  • Identify which features are at risk and the "at-risk" label to the feature.  
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
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 testsTeam

One sprint before feature freeze 

ActionResponsible
  • Update Features' statuses
  • Identify which features are at risk and the "at-risk" label to the feature.  
Product Owner
  • Test rails: Write/Review test cases 
    • Please consider how to test long lists/tables 
Product Owner/Manual QA/SIG
  • Prepare data for Bugfest
    • Create user stories for Kitfox that outline your needs and instructions 
      • FWIW - I think settings needs to be cleaned
    • Please consider how to test long lists/tables 
Team
  • Add release notes 
    • Include any previous release notes that still relate to the release 
    • flag any known items with the label  known-issue-<<release>>
Team

Accessibility Testing

Team
  • Conduct or create user stories for performance/load testing. See
Types of tests
Team

Bugfest (aka Business Acceptance Testing) period 

ActionResponsible
  • Update Features' statuses
  • Identify which features are at risk and the "at-risk" label to the feature.
Product Owner
  • User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 
Product Owner
  • Add release notes 
    • Include any previous release notes that still relate to the release 
    • flag any known items with the label  known-issue-<<release>>
Team

Team's accept Bugfest build. 

  • Teams must conduct smoke tests to verify key functionality works as expected BEFORE Bugfest is made available to community 
  • Teams must document 
    • App/module not ready for testing 
    • Issues yet to be resolved
Team
  • Conduct performance/load testing. See
Types of tests
Team


Sprint before GO-Live 

ActionResponsible
  • Update Features' statuses
  • There should be no at-risk features
Team
  • User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 
Product Owner
  • Add/Review release notes 
    • Include any previous release notes that still relate to the release 
    • flag any known items with the label  known-issue-<<release>>
Team
  • Complete remaining performance/load testing. See
Types of tests
Team/PTF


Go-Live sprint

ActionResponsible
Teams must conduct smoke tests to verify key functionality works as expectedTeam

Testing: All Karate tests and e2e tied to release functionality should be done and running 

Team
  • Add/Review release notes 
    • Include any previous release notes that still relate to the release 
    • flag any known items with the label  known-issue-<<release>>
Team