Do we need testers on agile teams? It’s the same argument again and again. One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”. The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And the debate goes on and on
To address this common question, we caught up with Janet Gregory, co-author of ‘More Agile Testing: Learning Journeys for the Whole Team’. Here’s what Janet had to say…
Janet Gregory (DragonFire Inc. Canada)
An agile testing coach and practitioner, Janet Gregory (@janetgregoryca) is the co-author of Agile Testing: A Practical Guide for Testers and Agile Teams and a contributor to 97 Things Every Programmer Should Know. Janet specializes in showing agile teams how testers can add value in areas beyond critiquing the product; for example, guiding development with business-facing tests. For the past thirteen years, Janet has been working with teams to transition to agile development, and teaches agile testing courses and tutorials worldwide. Janet contributes articles to publications such as Better Software, Software Test & Performance Magazine and Agile Journal, and enjoys sharing her experiences at conferences and user group meetings around the world.
For more about Janet’s work, visit www.janetgregory.ca where you can also view her blog.