Thunderjet Release Readiness Checklist - Poppy

Two sprints before feature freeze 

ActionResponsibleStatus
  • 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

DONE

  • All user stories tied to features should be written and estimated. 
Product owner

DONE

Testing

  • Identify features that require e2e tests
  • Identify features that require Karate tests
Team


  • Conduct user acceptance testing 

Product owner

DONE

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

One sprint before feature freeze 

ActionResponsibleStatus
  • 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

DONE

  • Test rails: Write/Review test cases. Please consider how to test long lists/tables.
Product Owner/Manual QA/SIG

REVIEW

  • Prepare data for Bugfest
    • Create user stories for Kitfox that outline your needs and instructions. Please consider how to test long lists/tables 
Team

DONE

Migration/module upgrade documentation checklist 

Migration Plan

  • Step by Step instructions for module upgrade
  • New Infrastructure: N/A 
  • Config Changes:
  • Schema Changes: JIRA issues created 
  • Data Migration:

Migration Testing

  • What are the configuration Changes?
  • What are the schema Changes?
  • How do we test?
Team
  • Document breaking changes > Breaking API changes are documented in the Release Notes.
Team

IN PROGRESS

  • Re-Indexing for release upgrade required? Timing considerations?
    • Production tenants
    • For bugfest
    • Consortia (TBD) environment(s)
Team

NA

  • 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

IN PROGRESS

Accessibility Testing

Team

TODO

  • Conduct or create user stories for performance/load testing. See
Types of tests
Team
  • Document Potential Risks and Risk Mitigation Plan
Team

Bugfest (aka Business Acceptance Testing) period 

ActionResponsibleStatus
  • 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
  • User stories: update Release field for those stories/bugs/tasks/etc that will not be done for the release. 
Product Owner
  • Generate Release Artifacts (see Orchid) and link to Release notes 


  • 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

Modules Ready for deployment

  • Review test status - Unit, Integration, e2e tests
Team
  • Team meets with Kitfox to review upgrade instructions. 
  • Team's accept Bugfest build. Need to consider Consortia support. 
  • 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
  • Deployment verification? 
Team
  • Regression testing
Team
Team

Sprint before GO-Live 

ActionResponsibleStatus
  • 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

ActionResponsibleStatus
  • 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
    • Include any previous release notes that still relate to the release
    • Flag any known items with the label  known-issue-<<release>>
Team