Home ยป Guidelines
Production bugs
The objective is to lower as much as we can the delay between the time a Critical bug is entering a feature team backlog, and the time that the fix is delivered as a new package.
QA team keeps a percentile of their weekly workload for the test of production bugfixes. Those tests cannot be planned in advance, and needs quick validation and approval.
GitHub boards
Github project boards have an automated process up to the Done column. The board owner should create a Closed column at the right of the Done column. Done column issues are those that can be QAified. If the QA is successful, QA team move the issue from Done to Closed. If not, the bug should be brought back at the very top of the Todo column.
Classical sprints
Feature Team Scrum Master sends a sprint planning summary email to lgs-openpaas-dev@linagora.com at the end of the sprint planning. QA should read the summary carefully and ask specific questions about the sprint backlog issues if it feels the need.
Big changes, new features
During the sprint planning, the Product Owner should identify the big changes that will happen in the software during the sprint. Product owner should have a specific communication with QA team about those big things, in order for QA to anticipate the test compaign.