Software Testing in Scrum
Do testers find it hard to adopt Scrum?
9 November 2015
Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.
Software testing can be defined as a process for running a program or application to find software defects. According to Philip Crosby's definition of quality, testing is conformance to requirements (1979, 16). So software testing is an important activity, especially in mission-critical software. End users expect 100 percent error-free software.
Testing is done during the later phases of the traditional software life cycle. Testing is frequently considered the final activity before the delivery. At the same time, testers' knowledge of the requirements and client's expectations are sometimes low when we look at today's Scrum teams.
Is it difficult for testers to adapt to Scrum? I don't think so. But it can be a little uncomfortable for some testers to transition to Scrum. Traditional testers are used to sitting in a cubicle, with little human interaction, focusing only on their testing activities. They don't feel responsible, overall, for what they have tested. But it's necessary for testers in Scrum teams to become accustomed to more frequent and meaningful conversations with teammates, and sometimes even with product owners or clients. One of the biggest challenges is learning how to work iteratively. In the first few sprints, testers have to learn the real expectation of the client and how the test suite should be worked.
Increasing test automation becomes the hallmark of Scrum teams, especially during the regression pace in the final sprints. Likewise, knowledgeable automation testers always give an extra advantage to Scrum teams. So one can clearly see that testers who transition to Scrum are making a smart move. Testers in Agile teams have more influence in the development process, and they have overall responsibility for the end product.
Current rating: 3.6 (5 ratings)
The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.