| Table of Contents | ||||
|---|---|---|---|---|
|
Game Plan: Quality or speed?
...
Sprint Architecture
Backlog Item Breakdown
50% - 70% = Work for new features
30% = Other tech or sprint-related work including:
Ad-hoc testing
FR translation testing
Tech debt
Documentation
Release activities
Missed unit tests
Automated testing
Critical bug fixes
Required Backlog Items
Ad-hoc testing
FR translation testing
Daily Breakdown
Length: 10 business days
How to include: tech debt
Sprint Composition
Notes:
...
Day | Task | Team Members |
|---|---|---|
Day One | ||
Day Two | ||
Day Three | ||
Day Four | ||
Day Five | ||
Day Six | ||
Day Seven | ||
Day Eight | ||
Day Nine | ||
Day Ten |
Release Plan
Checklist
Category | Task | Team Members |
|---|---|---|
Testing | Feature, and features surrounding it, are fully tested | |
Sprint Composition
Every sprint: to release - need to make sure feature we release is fully tested, as well as features surrounding it:
Dev 1: Completes dev, bugs are fixed
Dev 2: write test case, automated testing, manual testing
New feature work 50%-70%; 30% might include tech debt, ad hoc testing, documentation, translation testing, release activities, missing unit tests and automated tests, critical bug fix
Might have a sprint where it is just bug fixes - might add all bug fixes in a specific sprint
Can we still use Ewa 4 days of the sprint - ad-hoc testing would really help - this would be very valuable. She could do ad hoc testing, writing test cases, etc. anything that is valuable. Even if she does a timeboxed one day ad hoc testing, that would be valuable - one day timebox on QA and one day timebox in ACC.
Need to communicate to the user that the cost might not be worth it to do non-valuable things.
Can use playwright for automated testing - have we solved the issue of authentication?
Change management - could write the ticket every sprint
If we follow this method, might not have to do a full regression test. But might want to do a 5 day regression.
Need - conversation about who will decide what is a bug or not or UI change we are not going to make. Action item: feature we will never fix - e.g. Here is a bug that is not a bug. Team can search to see what decisions were made.
...
B Unit testing - more like unit testing for the UI - not full UI automated testing
Regression Testing
Release Plan
Release Plan - brainstorming
...
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
...