One of the benefits of Agile is being able to test each piece of functionality as it’s developed. Part of the testing should include testing how all the functionality works together. But what do you do when SQA teams are focused on only their piece?
That’s where Tech Pubs comes in. As part of our writing process, our group installs the latest build. That’s not an uncommon practice. Since we deliberately push the system in ways SQA doesn’t, sometimes we can spot issues that SQA isn’t testing for.
In this release we have two pieces of functionality that should be complimentary. One is intrinsic to the direction the software is heading; the other is an add-on. The two development teams worked together in areas that overlapped. However, SQA didn’t. Each SQA team concentrated on its own area and didn’t create test scripts to include the other functionality.
When I installed and activated the add-on module, I discovered that the intrinsic functionality was disabled. I brought this to my team’s attention, who didn’t believe me at first. (Of course it worked; SQA didn’t have any issues.) So, I reinstalled. It happened again. I noted my steps and exactly where the issue appeared. I complained. I discussed it with the writer on the other team. We both complained. And we complained some more.
If I installed the extra module, I couldn’t do my job. If I didn’t install the extra module, the other writer couldn’t do her job. We were stuck. Yes, we could have installed two instances, but the amount of “real” data we put in made that time consuming and wasteful.
Finally, someone listened. The Associate Director put both teams in a room and told the developers to figure it out, and for SQA to add test data that included the other functionality. It was fixed.
I’d like to say it worked out just fine from there on. However, two sprints later, I was in the same boat. This time, the teams listened much quicker. The issue was resolved within days.
I am in a unique position as a technical writer. Not only am I able to speak for our customers during development, but I am able to bridge teams. Along with my fellow writers, I am the first person who uses the software was it was meant to be used. If we find any issues, we save the company time and money—and, if the issues slipped by OQ, its reputation.
