My understanding is that it's advised testers are separate from developers, i.e you obviously have developers testing their code but then dedicated testers as well.
How does that actually work in practice on a small project, say 5 developers people or less? It seems unlikely you could keep a tester occupied full-time, and while you could bring in random short-term people I'd argue a tester should understand the app well - its intended usage, its users, its peculiarities - just like you don't want developers to be transient on the project.
QA is not a separate team, so its efficiency can be negatively impacted by delays in development, changes to product features, etc. Since QAs are tightly bound with a module, the verification of that module can become monotonous. This might impact performance of long-term projects.
First, testing is an important part of development. No one in their right mind would suggest that testing doesn't occur in Scrum. The Scrum Team is responsible for all the work needed to develop the increment of the product. Since that includes testing, the Scrum Team is responsible for testing.
Testing is essential because we all make mistakes. Some of those mistakes are not important, but some are expensive or could be life-threatening. We have to test everything that we produce because things can go wrong; humans can make mistakes at any time. Why is Testing Necessary?
You can definitely keep a tester working full time - they should be testing the product throughout the development process, not just at the end. In fact leaving testing to the end of a project is absolutely the worst thing you can do.
I have worked in a couple of companies that have typically 1 tester for every 2 developers, and there has never been an issue with them running out of things to do - in fact quite the opposite.
Both of these have been small companies with 10-20 developers and 5-10 testers.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With