Versions Compared

Old Version 5

changes.mady.by.user Natalia Zaitseva

Saved on

compared with

New Version 6

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 (184) 

ActionResponsibleStatus
  •  Update Features' statuses
  •  Identify which features are at risk and the "at-risk" label to the feature and escalate to stakeholders
  •  Clean up Q backlog 
Product owner

feature list is accurate and up-to-date


Natalia: to move tickets with release field "R" to the next release

  •  All user stories tied to features should be written and estimated. 
Product ownerNatalia: to double -ckeck user stories 

Testing

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

From Poppy Release notes discussion

Need Karate tests for consortia > Action item to create consortia specific Karate tests stories. So no expectation that these stories will be ready for Dev freeze and for Go-Live?  

What about consortia specific e2e tests 

  •  Conduct user acceptance testing 
  • Product owner (maybe a SIG member can help write tasks?) 
  • Team needs to setup an environment for UAT
Goal Sprint 186  - need rancher environment to be updated. 
  •  Conduct or create user stories for performance/load testing. See
Types of tests		Product Owner writes user stories. TBD who will conduct. no need in PTF testing, Valery will create his own tests
  •  Document Potential Risks and Risk Mitigation Plan
Team

...