Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

...

Sprint Architecture

Length: 10 business days

With QA resources

Day 1, 2 and 3:

  • QA - Any backlog items that need to be tested from days 9 and 10 of last sprint.

  • QA - Ad-hoc testing of app (30min to 1 hr.).

  • QA - UAT prep - Word doc and spreadsheet creation.

  • Dev - Work on top priority backlog items

  • {PO -

    • {Option 1:

...

QA:

Day 2:

Day 3:

Day 4:

Day 5:

Day 6:

...

    • Provide list of backlog items to users. They can test if they have time in ACC. If they do not have time, they do not have to test.}

    • {Option 2: PO hosts regular bi-weekly testing session with users to test backlog items completed last sprint. Users only attend if they can.}

Day 4, 5, 6, 7:

Without QA resources

Day 1, 2 and 3:

  • Dev - any backlog items that need to be tested from days 9 and 10 of last sprint. Dev cannot test backlog items they developed.

  • Dev - Ad-hoc testing of app (30min to 1 hr.).

  • {PO? - UAT prep - Word doc and spreadsheet creation.}

  • {PO -

    • {Option 1: Provide list of backlog items to users. They can test if they have time in ACC. If they do not have time, they do not have to test.}

    • {Option 2: PO hosts regular bi-weekly testing session with users to test backlog items completed last sprint. Users only attend if they can.}

Day 4, 5, 6, 7:

Day 8:

  • PO walkover (if needed) - 15 minutes max.

Day 9:

  • Dev: Sprint review planning - add items to present at sprint review to agenda

Day 10:

  • Dev: Sprint review dry run - prepare demo and participate in sprint review dry run

  • Dev: Sprint review - participate in sprint review

Definition of Ready

  • Dev sends screenshot of

Testing

Discussion with Grace - April 4

Bugs addressed during the sprint. Leave some space for bug testing during the sprint

...