| Table of Contents | ||||
|---|---|---|---|---|
|
...
Team Member | Task | |
|---|---|---|
| 1 | Dev #1 |
|
| 2 | Dev # 2 |
|
| 3 |
Shippable Stories
Type | Required to Ship |
|---|---|
Tech Debt |
|
PBI |
|
Bug |
|
One-off Sprints
Bug fix only sprint
Full regression test
...
Task | Branch | Team Member |
|---|---|---|
Create sprint branch {on first day of sprint?} | Sprint branch | Ashiq |
Push sprint code to sprint branch | Sprint branch | Dev team |
Question: How do we separate stories that are ready to ship from those that are not ready to ship from the sprint branch? Is this possible?
Sprint Environments
Task | Environment | Team Member |
|---|---|---|
Dev testing | Dev | Dev |
Manual QA test, automated test | {Test?} | Dev and QA |
{ACC?} | Dev and QA |
...
Weekday | Tasks | Team Member | |
|---|---|---|---|
| 1 | Wednesday | ||
| 2 | Thursday | ||
| 3 | Friday | ||
| 4 | Monday | ||
| 5 | Tuesday | ||
| 6 | Wednesday | ||
| 7 | Thursday | ||
| 8 | Friday | ||
| 9 | Monday | ||
| 10 | Tuesday |
Items to Action
...
Decision
...
Team Member
...
Status
...
Who will decide whether or not a bug or UI change suggestion will be added to the backlog
...
Create a feature to hold items we will never fix, so the team can use it as a reference in the future
...
In which environment should we test backlog items and Playwright tests - Test or ACC, or both?
...
Release Process
There are two processes to choose from:
Process | Task | |
|---|---|---|
| 1 | Ship once per sprint | Ship all shippable features once per sprint |
| 2 | Ship multiple times per sprint | Ship each story when it is ready |
We can ship in mid-sprint.
...
Day 1 - Discuss what we can ship in the morning (we can tack it on the scrum), and ship in the afternoon. PO can inform clients of shipment.
Sprint | Plan | Tasks |
|---|---|---|
Sprint 1 | ||
Sprint 2 | ||
Sprint 3 |
Individual Sprint Plan
Weekday | Tasks | Team Member | |
|---|---|---|---|
| 1 | Wednesday | Shipping option #1
| |
| 2 | Thursday |
| |
| 3 | Friday |
| |
| 4 | Monday |
| |
| 5 | Tuesday | Shipping option #2
| Jugraj, Steve |
Items to Action
Question | Decision | Status |
|---|---|---|
Who will decide whether or not a bug or UI change suggestion will be added to the backlog | ||
Create a feature to hold items we will never fix, so the team can use it as a reference in the future | ||
In which environment should we test backlog items and Playwright tests - Test or ACC, or both? | ||
If we have a single sprint branch, can we separate stories that are not ready to ship from stories that are ready to ship? | ||
Do we need an SMGS ticket for every time we ship an item (e.g. one every two weeks?) |
Release process with shippable feature
Day 2, 3 and 4:
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, PO, Ewa, Maggie - Ad-hoc testing of app (30min to 1 hr.)
Dev - meeting with dev and QA sprint tickets and identify test cases as a group - discuss possible test cases for each ticket, which tickets interact. Test cases stored in DevOps.
{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. One hour of testing only max. Perhaps we can send a copy of the weekly agenda, and they can test if they like.}
{Option 2: PO hosts regular bi-weekly testing session with users to test backlog items completed last sprint in ACC. Users only attend if they can. }
...
Testing - brainstorming only
Discussion with Grace - April 4
Bugs addressed during the sprint. Leave some space for bug testing during the sprint
...
How to track modifications to backlog items. E.g. when testing, if something needs to be added, what should we do?
Discussion with Ashiq
PO and users:
test in ACC
They can test on the first day of the next sprint - will will give them a list of what we completed and they can test if they can, if not, that is ok - maybe 1 hr of testing for them
Dev - send a screenshot of new UI before the functionality is built to get feedback from PO via email. Do not need to send screenshots for things such as bugs, and FR translations. Only things we need feeback on.
PO walkover - two days before the end of sprint - 15-30 min to take a quick look if screenshots are not enough - flexible. PO may not need it every week.
Can show him work still in progress
Users can test in test environment if they wish after sprint review. We can give them a few bullet points of what we worked on. Either at end of review or first day of sprint.
...
How would we work with dev’s only to write test cases?
Discussion with Ashiq
QA free from manual testing
...