Testing in Scrum

Last post 09:35 pm November 13, 2017
by Timothy Baffa
2 replies
03:18 pm November 13, 2017

We have an issue in our development team, the development throughput is far much than our QA members to test , our test team found them self in situation, where every two days there a new closed feature and they need to do functional, regression, exploratory and other tests, this loop consume a lot of time, because every change or commit in source code, force them to repeat every thing. They now waiting the developer at middle and before end of sprint to run their tests. is there any best practice to testing in Scrum.

04:46 pm November 13, 2017

I suppose you might be able to speed things up with a better use of automation. But isn’t this kind of delay and wastage exactly what you’d expect from having separate test and development teams, with their associated skill silos?

09:35 pm November 13, 2017

Agile will highlight where your issues and/or bottlenecks are in flowing quality work product to your customers.   It seems in your situation that manual testing is the bottleneck.

It is extremely difficult to practice Scrum without automation.  As soon as possible, you should begin looking into ways to automate your testing.   It certainly won't happen overnight, but you need to begin the effort, and the sooner the better.

One of my favorite Agile quotes is from Ilan Goldstein, a Scrum trainer and author:

"Scrum without automation is like driving a sports car on a dirt track – you won’t experience the full potential, you will get frustrated, and you will probably end up blaming the car..."