Guest Blog: The Need for Dedicated Testers in an Agile Environment
The following is a guest post to Zephyr from Venkatesh Krishnamurthy. You can read more of his writing at his blog http://agileworld.blogspot.com/.
Scrum recommends 3 roles, the Product Owner, Scrum Master and the team. There is no dedicated role as a tester (or QA) if you are following pure Scrum.
Agile also recommends that the team members are expected to be cross functional with T-shaped skills popularly known as “Generalized Specialists”.
However, the challenge I have seen in many projects is how “generalized” one could be while performing the role. Most of the projects are, so budget and time constrained that everyone is part of the rat race. They just want to get things done, and there is hardly any time for the team members to learn from each other and building generalized skills.
Building cross-functional and T-shaped skills is not easy. It needs a dedicated attention, time, effort and $ is involved from the organization to enable this. One cannot ask a developer to sit with a tester for a few days and learn testing. Personally I believe that testers mindset is something that comes with passion. In addition, mindsets of developers and testers are different.
There is one more reason behind having dedicated testers, and this is due to “IKEA effect”. The Harvard article concludes that,
“When people use their labor to construct a particular product, they value it more than if they didn't put any effort into its creation, even if it is done poorly.”
In the context of this article, when developers create the code, they value their creation more than the testers. The developer doesn’t like someone finding fault with their creation. This is one of the reasons why one gets to hear all sorts of excuses from the developers.
This is where sometimes I get skeptical about building generalized skills between testers and developers. It is easier to learn testing tools and few skills, however, inculcating “testers mindset” is a challenging task.
I am not saying that developers shouldn’t take the quality responsibility. However, it should not be left only on the “creators”. Contrary to the popular beliefs, testers have a much important and key role in Agile environments.
There are some on and off threads on the internet, and rumors around Facebook don’t have testers. Sometimes it is hard to believe that a large organization which supports millions of users, robust, scalable platform has no testers!!
As I conclude this article, let me ask you this, have you come across projects with no dedicated testers? How effective were you in building “generalized skills” between developers/testers?
About Venkatesh Krishnamurthy - Venkatesh Krishnamurthy is a delivery coach in a large insurance company in Melbourne, Australia. After completing his bachelors degree in Computer Science and Engineering, Mr.Krishnamurthy has spent the last 15 years working for major industries such as telecom, finance, healthcare and automative. Mr.Krishnamurthy's innate interests in Cognitive science lead him to easily gain mastery in the Agile methods and processes such as Scrum, XP, lean and Six Sigma.