| Table of Contents | ||||
|---|---|---|---|---|
|
Sprint Architecture
Backlog Item Breakdown
Percent | Task |
|---|---|
50% - 70% |
...
New releasable feature work | |
30% |
...
Other tech or sprint-related work including:
|
...
Tech debt
|
...
|
...
|
Required Backlog Items
Ad-hoc testing
FR translation testing
...
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
...