What’s a Tester without a QA Team?

of community, they want to share their testing experiences with testers from other project teams. This creates shared common knowledge across the teams. If one team finds a tool they think can help another team, they share their innovations to save time and energy. This kind of respective knowledge sharing is good for the organization. Testers get the support they need and plenty of help solving the toughest testing issues.

Once a tester no longer thinks of herself as isolated, or a victim of process, but instead as someone as with power to help the team, she can start to take charge of her own development. As part of a learning organization, she will be encouraged to read articles and professional blogs, write articles of her own, present successful team initiatives to other teams, participate in larger community organizations such as local quality or agile groups, attend conferences or maybe even present at one. Participating in a testing community within the organization, as well as larger testing and development communities on local, national and international levels, helps us and our development teams continually find ways to work better.

Expanding Your Horizons
As you can see, testers need never be alone, even if they don’t belong to a separate QA team. They have a giant support group ready to help them if they reach out and find it. Even more importantly, testers bring their expertise to a development team where everyone, not only testers, is passionate about quality. It takes courage to get out of your comfort zone and team up with developers for the first time. You may need to learn new skills to help customers specify their quality criteria for each new piece of functionality.

Open your mind to the new possibilities. Team up with developers to solve testing problems in new ways. Maintain a strong connection to your tester community to exchange experiences and good practices. Take advantage of all the resources on the internet, in publications, in local and online user groups, and keep learning. You may find you enjoy your job even more than when you were part of a QA team.

Tags: 

About the author

Lisa Crispin's picture
Lisa Crispin

Lisa Crispin is the co-author, with Janet Gregory, of Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009), co-author with Tip House of Extreme Testing (Addison-Wesley, 2002) and a contributor to Beautiful Testing (O’Reilly, 2009) and Experiences of Test Automation by Dorothy Graham and Mark Fewster (Addison-Wesley, 2011). She has worked as a tester on agile teamssince 2000, and enjoys sharing her experiences via writing, presenting, teaching and participating in agile testing communities around the world. Lisa was named one of the 13 Women of Influence in testing by Software Test & Performance magazine in 2009. For more about Lisa’s work, visit www.lisacrispin.com.

About the author

Janet Gregory's picture
Janet Gregory

An agile testing coach and practitioner, Janet Gregory is the co-author of Agile Testing: A Practical Guide for Agile Testers and 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, by guiding development with business-facing tests. For the past ten years, She has been working with teams to transition to agile development, and teaches agile testing courses and tutorials worldwide. Janet enjoys sharing her experiences at conferences and user group meetings around the world. Janet was named one of the 13 Women of Influence in testing by Software Test & Performance magazine.

For more about Janet's work, visit www.janetgregory.ca/ or visit her blog at janetgregory.blogspot.com.