Why sharing information with other people can make you a more agile tester
Posted by Matt Archer on January 23, 2013
|This post is part of the tips for manual testers working in an agile environment series. A series of posts inspired by the topics covered in the Techniques for Agile Manual Testers course that is currently available to take in London (via the Ministry of Testing) and in Copenhagen (via PrettyGoodTesting).
When testers work in isolation it is easy to forget that some of the information that we gather and store for future use is the same, or very similar, to the information that other team members document.
In agile development teams, testers typically work much closer with other team members which helps highlight this kind of repetition. That said, even when the overlap becomes obvious, the practice of “my documentation” is one of the hardest habits to break.
I attribute much of this resistance to the practice of using documents to represent key milestones and the rate of document production as an indicator of progress. Based on this mentality, reusing another team member’s documentation can feel like you are not providing measurable value. In reality, this type of reuse will give you more time to focus on the things that make you valuable, like finding bugs.
This emphasis on documents is something that agile teams replace with a focus on working, business impacting, software. Testers can help support this ethos by looking for opportunities to reuse existing documents that have already been produced and either updating or amending them directly, or referencing them from their tests or new (typically much shorter) test-centric documentation that only contains information that cannot be found elsewhere.
If you have a comment or question about this particular tip, please do not hesitate to Leave a Reply. A complete list of tips is listed below.