Page Comparison

1-3

• Write change management ticket for release in two weeks (not next release but the following release)

• Maggie & Jugraj

• Create sprint branch

• Ashiq

• Confirm user stories that will go in next release

• Jugraj, Ashiq & Maggie

• Finish UAT spreadsheet - based on users stories confirmed in the spreadsheet

• Send UAT spreadsheet to users

• QA & Steve

• Distribute tickets in the sprint to the team:

  • Write test case

  • Manually test

• Maggie

• QA & dev meeting to identify possible test cases as a group

• QA & Dev

• Complete any additional testing of backlog items from previous sprint (if required)

• Add backlog items in current sprint to UAT spreadsheet (preparation for next release)

• Write test cases for PBI and bugs in current sprint

• Ad-hoc testing in QA environment (30min-1hr)

• Test backlog items as needed

• Ewa & Tarek

• Develop backlog items

• Write test cases as needed

• Test each other’s backlog items as needed

• Dev team

Day 4

• Final sign off on backlog items to ship

• Jugraj, Ashiq and Maggie

• ACC smoke test

• QA, dev and Maggie

Day 5-8

• Day 5 - Release ACC to prod

• Jugraj & Ashiq

• Write test cases for PBI and bugs in current sprint as needed

• Test backlog items as needed

• Ewa & Tarek

• Develop backlog items

• Write test cases as needed

• Test each other’s backlog items as needed

• Dev team

Day 9

• Identify what has met the definition of done that can be shipped on day 5 of next sprint

• Anything else that is not done will be completed and shipped the following sprint.

• Jugraj, Ashiq and Maggie

• Write test cases for PBI and bugs in current sprint as needed

• Test backlog items as needed

• Maggie & Tarek

• Develop backlog items

• Write test cases as needed

• Test each other’s backlog items as needed

• Dev Team

Day 10

• Sprint review & sprint planning

• Finish and wrap up what can be done

• QA & dev team