Why Testers and Developers Don’t Have to Be on the Same Page
We so often assume that conflict or a differing opinion is a bad thing. Because testing and development teams work together more than ever before—thanks to agile requiring greater collaboration between the two teams—we assume there has to be some sort of consensus on how things should be done at each and every step.
Fortunately, that’s just not the case. Since software development is highly subjective in nature, different thought processes and assumptions between development and testing teams can positively impact applications and lead to a more successful, well-rounded product.
It might not seem like it at the time, but there’s value to dissonance. Different members of the team can bring unique ideas to the table, bounce them off of each other, and come to a compromise/solution that could only come through some disagreement.
TJ Usiyan, a software developer and instructor with Atlanta-based company Iron Yard, recently spoke with StickyMinds about the subjective nature of software development and how disagreeing early on is healthy.
“Having a conversation early on with as many people with as many views as you can, can help you understand where you've fallen in relation to certain decisions that you can make, and you know whether or not you have to be on the same page,” he explained.
For example, you might exclusively use your banking app to keep track of what’s in your checking account and manage the amount that goes into savings. If that aspect of the app you’re developing is solid, you’d feel great as you approach launch. But if someone else on your team values the check deposit feature the most, and the app you’re developing struggles to recognize signatures and dollar amounts, then you need to take that experience into account to improve the product.
Software development shouldn’t be a constant battle between developers, testers, and everybody in-between. However, don’t shy away from conflict when it’s there. Deal with it early and often, and make sure that everyone agrees on the direction of the application before it ships.
“I'm not advocating that you actually have to consider every single person all of the time in all scenarios, but you have to know that you have made a decision not to support this user in this way,” Usiyan continues. “You don't actually have to be on the same page in the beginning, but I do think that by the end of your process, you should be on the same page.”
