| Table of Contents | ||||
|---|---|---|---|---|
|
...
Percent | Task |
|---|---|
50% |
|
10% |
|
30% 20% | Other tech or sprint-related work including:
|
10% |
|
10% |
|
Required Backlog Items
...
Ad-hoc testing
...
Release Process
We will ship once per sprint.
Process | Task |
|---|---|
Ship once per sprint | Ship all shippable features once per sprint |
Daily Breakdown
Length: 10 business days
WeekdayDay | Task | Team Members | ||||||
|---|---|---|---|---|---|---|---|---|
1 | Wednesday | Maggie / Jugraj - write -3 |
|
| ||||
| 2 |
| Thursday |
| Ewa | 3 | Friday | 4 | Monday |
| 5 | Tuesday |
| Ewa | 6 | Wednesday | |||
| 7 | Thursday |
| Ewa | |||||
| 8 | Friday | 9 | Monday | 10 | Tuesday |
| Ewa
| |
| ||||||||
|
| |||||||
|
| |||||||
|
| |||||||
Day 4 |
|
| ||||||
|
| |||||||
Day 5 |
|
| ||||||
|
| |||||||
|
| |||||||
Day 6-8 |
|
| ||||||
|
| |||||||
Day 9 |
|
| ||||||
|
| |||||||
|
| |||||||
Day 10 |
|
|
Dev - Backlog item checklist
Team Member | Task | 1||
|---|---|---|---|
Dev #1 |
| ||
| 2 | Dev # 2 |
| 3
Shippable Stories
Type | Required to Ship |
|---|---|
Tech Debt |
|
PBI |
|
Bug |
|
...
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
Sprint Environments
Task | Environment |
|---|---|
Dev testing & Playwright | DevDev |
Current Release | ACC |
...
Next Release* | QA |
...
*When work in QA is ready for next release, we they will send it to ACC.
Tickets
...
Switch endpoints for test environment.
...
be pushed to ACC
Sprint decision-makers
Task | Team Member |
|---|---|
Whether or not a bug or UI change suggestion will be added to the backlog |
...
Weekday | Tasks | Team Member | |
|---|---|---|---|
| 1 | Wednesday | ||
| 2 | Thursday | ||
| 3 | Friday | ||
| 4 | Monday | ||
| 5 | Tuesday | ||
| 6 | Wednesday | ||
| 7 | Thursday | ||
| 8 | Friday | ||
| 9 | Monday | ||
| 10 | Tuesday |
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.
...
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
...