| Table of Contents | ||||
|---|---|---|---|---|
|
...
Weekday | Task | Team Members | |
|---|---|---|---|
| 1 | Wednesday |
| Maggie / Jugraj |
| 2 | Thursday |
| Ewa |
| 3 | Friday | ||
| 4 | Monday | ||
| 5 | Tuesday |
| Ewa |
| 6 | Wednesday | ||
| 7 | Thursday |
| Ewa |
| 8 | Friday | ||
| 9 | Monday | ||
| 10 | Tuesday |
| Ewa |
Dev - Backlog item checklist
Team Member | Task | |
|---|---|---|
| 1 | Dev #1 |
|
| 2 | Dev # 2 |
|
| 3 |
...
Can use playwright for automated testing - have we solved the issue of authentication?
Sprint Branches
Task | Branch | Team Member |
|---|---|---|
Create sprint branch {on first day of sprint?} | Sprint branch | |
Push sprint code to sprint branch | Sprint branch | Dev team |
Sprint Environments
Task | Environment | Team Member |
|---|---|---|
Dev testing | Dev | Dev |
Manual QA test, automated test | {Test? |
...
} | Dev and QA | |
{ACC?} | Dev and QA |
Sprint decision-makers
Task | Team Member |
|---|---|
Whether or not a bug or UI change suggestion will be added to the backlog | |
Regression Test
Tasks
Schedule
...
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? |
Without QA resources
Dev work for each sprint will be pushed into a sprint branch (e.g. sprint 29 branch). Tested in the dev environment, then to QA, ACC and prod.
...
Release process with shippable feature
...
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
...