15min | Process & status reporting Weekly bug triage: Sam, Wes & Mary Jo have a weekly bug triage, should there be a weekly or biweekly bug triage lead by Joanna with tech lead review? Organizing and labeling bugs: creating an epic vs keeping in the bug backlog alone, searching for quick wins, other questions about prioritizing Epics such as “requisition bugs”, “SM bugs” etc Working with dev team members to identify quick wins Trivial bugs - should we dead these? Aging of bugs: review bugs that have been reported in 2017 that still haven’t been completed. Should these still remain if we haven’t prioritized or worked on them? If they do remain, we should update the comments in the ticket. Bug root cause analysis - are we still doing this? This should be part of regression testing when bugs are found, and release testing.
Bug fix % each sprint and reporting the progress we are making each sprint Testing status & automating reporting for each sprint Automating regression and release candidate status for future testing and releases Functional Testing progress Review Bug priority (post in Discourse for agreement?) Monitoring tickets in QA (checking on other teams and making sure they are moving tickets and testing their team’s tickets as needed) What sprint will we do the next manual regression testing? What should we focus on testing? We will need to consider all team’s deliverables to decide what to test.
|
| |