Versions Compared

Old Version 1

changes.mady.by.user Radhakrishnan Gopalakrishnan

Saved on

compared with

New Version Current

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 user stories backlog 
Product owner
  •  Make sure all stories assigned to the release is associated with a feature
  •  Make sure all stories that have been merged to master is has a Fix Version
Scrum-master and 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

    • owner   


    •  Conduct or create user stories for performance/load testing. See Types of tests
    		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

    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
    .
    • and escalate to stakeholders
    •  Clean up backlog   
    		Product Owner
    •  Test rails: Write/Review test
    cases 
    • cases. Please consider how to test long lists/
    tables 
    • tables.
    		Product Owner
    /Manual QA/SIG
    and QA 
    •  Review and revise current help/product documentation on wiki. 
    		Product owner 
    •  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

    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
    •  Re-Indexing for release upgrade required? Timing considerations?
      •  Production tenants
      •  Bugfest environments 
      •  Consortia (TBD) environment(s)
    		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
    •  Document Potential Risks and Risk Mitigation Plan
    		Team

    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
    .
    • and escalate to stakeholders
    •  Clean up user stories 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 
    • 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

    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.
    • builds
    •  
    • 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 
    •  Deployment verification? 
    		Team
    •  Regression testing
    		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