Versions Compared

Old Version 29

changes.mady.by.user Magdalene Schifferer (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Magdalene Schifferer (Unlicensed)

Saved on

Key

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

...

Day

Task

Team Members

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

...

  • Product Owner or QA:

    • Provide list of backlog items to users

    • Users can test in ACC if they have time

    • If users do not have time, they do not have to test (not required)

    • Users should only test one hour max.

Sprint Testing

  • UAT testing sheet

  • Smoke testing

Sprint Branches

Task

Branch

Team Member

Create sprint branch

Sprint branch

Ashiq

Push sprint code to sprint branch

Sprint branch

Dev team

...

  • Acceptance criteria is complete

  • PO (or equivalent) has approved screenshot of UI for new work (as needed)

  • Unit test is complete

  • Test case is written

  • {Automated test is complete}

  • QA manual Playwright test is written

  • Changes don’t introduce any new security defects, code-quality issues, or lower the code-coverage percentage

  • QA manual (main functionality and other components it interacts with) test is complete in correct branch

  • Documentation for security groups

  • As needed: Dev sends screenshot of new UI work for which feedback is needed, to PO

  • When a story is done, and anything around it is tested so it is shippable

Future consideration

Definition of done future consideration

...

Task

Team Member

Ad-hoc testing

QA

Writing test cases

QA & Dev

Unit test

Dev

Automated - Playwright (B-unit test - UI based)

Dev

Manual test

QA & Dev

UAT prep

QA

UAT

QA or PO

Smoke test

QA & Dev

Regression test

QA & Dev

...