Versions Compared

Old Version 1

changes.mady.by.user Radhakrishnan Gopalakrishnan

Saved on

compared with

New Version 2

changes.mady.by.user Khalilah Gambrell

Saved on

Key

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

Two sprints before feature freeze 

ActionResponsible
Sprint
Status
  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature
.  
  • and escalate to stakeholders
  •  Clean up backlog 
Product owner
  •  All user stories tied to features should be written and estimated. 
Product owner

Testing

  •  Identify features that require e2e
tests 
  • 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 tests
Team

One sprint before feature freeze 

ActionResponsible
Sprint
Status
  •  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 
  • cases. Please consider how to test long lists/
tables 
  • 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
    • instructions. 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

  •  OR conduct manual accessibility testing with Deque aXe 
Team
  •  Conduct or create user stories for performance/load testing. See
Types of testsTeam

Bugfest (aka Business Acceptance Testing) period 

ActionResponsible
Sprint
Status
  •  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 
  • notes
    •  Include any previous release notes that still relate to the
release flag
    • 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 
  • community
  •  Teams must document 
    • App/module not ready for testing 
    • Issues yet to be resolved
Team
  •  Conduct performance/load testing. See
Team


Sprint before GO-Live 

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


Go-Live sprint

ActionResponsible
Sprint
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
  •  Add/Review release
notes 
  • notes
    •  Include any previous release notes that still relate to the
release flag
    • release
    •  Flag any known items with the label  known-issue-<<release>>
Team