I wanted to ask if anyone has experience with the role of the classic software tester in Scrum ?
Information My personal experience is that in the first days there is not much to do for software testers (of course this does not mean that they do nothing, there are also general tasks in the QA department, create test environment, update test cases and write new ones, etc.).
The first days of the Sprint are usually spent writing User Stories. These are then converted into solution specs and the implementation can begin. The software tester has little to do at the beginning, he starts to review and comment the specifications mostly between the 4th and 8th sprint day.
These are then rewritten by the developer or software tester into test cases, whereby another software tester reviews the test cases and, if necessary, corrects them with the help of the programmer.
Subsequently, the first builds are completed (Alpha 1, Alpha 2,....,Alpha n) and the first round of functional testing can be performed.
After the complete implementation of all features (alpha for all modules), the first bug party can take place to determine the quality of the implementation and, if necessary, decide to run a second round of functional testing. This is followed by the integration test regarding the communication of the different modules and their interfaces.
Then the first update and installation tests can be performed and the business verification tests.
And last but not least the user acceptance test at the customer site.
To reduce the time needed for testing and to focus it on the changed areas (cost reduction regarding the testing effort), we thought about copying the sprintbacklog tasks into an Excel sheet (Y-axis) and listing the modules of the program on the X-axis. Here the respective programmer can mark which areas have been changed by which task. Then the software tester can test the respective test cases at these modules due to this information.
The same applies to the user stories, here the test effort can also be reduced if these are brought into dependence with the changed modules and thereby an indication is created, which use case scenarios must be examined and tested.
Questions: I would be interested to know how you have accommodated testing activities in Scrum.