We have a problem in our development team, the development throughput is much higher than our QA members can test.
Our test team found itself in a situation where a new feature needs to be tested every two days.
So we have to do function, regression, exploration, and other testing, this loop takes a lot of time because any change or commit in the source code forces it to repeat everything.
They are now waiting for the developer to run his tests in the middle and before the end of the sprint. Is there some kind of best practice for such bottlenecks in the agile environment?
So one should rather solve the problem from the Project Owner side. Plan fewer tasks in sprint planning?
Should tasks be rejected in order to avoid this bottleneck?
Should sprint planning be further punished?
I already described the problem in the retro, the solution was a shortened sprint planning. But, depending on the effort, we still have the problem that we run into this bottleneck over and over again.
But the problem is, we also write and review the test automation. But we simply can't keep up with passing the "normal" test, adapting the automatic test at the same time or creating a new one, everything together is simply no longer achievable.
- So should the execution of the test automation also be included in the sprint planning?
- But wouldn't this even worsen the problem?
- Where exactly are the priorities to be defined now? Write and adapt the test automation, or just normal test, i.e. Explorative, Functional.
- What is important Whitebox or Blackbox test?
Especially small teams with few testers and a lot of tasks have these problems in front of them. On the one hand we all know that in the agile world speed is everything, but it is forgotten that the QA is sometimes simply too much burdened. We are only human beings!
Even if the project owner is looking for solutions and everything was reported in the retro, not everything can be solved. Depending on the size of the project, you always have a bottleneck somewhere, and yes it is somehow desperate!