In a Scrum team, there are three roles: Product Owner, Development Team and Scrum Master. There is no explicit mention of software testers and some could question if testing specialists are really necessary in Scrum teams. After working on several projects, Eric Delahaye has found that they are and shares with us four reasons why they should be included as soon as the first Sprint Planning. Author: Eric Delahaye, Hexacta, https://www.hexacta.com/ While it is true that in theory The Scrum Guide points out that “Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis”, those of us who work in this Agile world know that Scrum itself, in an organic way, know that involving all roles that make a development possible is the key to success. Scrum recognizes the importance of each member (not only developers) as part of the team. So, what actually happens to software testers if Scrum suggests that an Agile team is fully capable of performing different tasks while being responsible for quality? Are they really necessary? Thanks to the results we have achieved in several projects, I have no doubt that THEY ARE, and they are absolutely necessary from day 1 from the first Sprint Planning! There are many ways to face testing in an Agile team that works with Scrum, especially when there are one or many testers. After years of working with this methodology, we have implemented a practice that [...]
↧