Developers, testers, and the communication between them

You know something that developers are really good at? Blaming other developers. Another thing? Fighting with quality assurance people.

Joking aside, I think is human nature to be defensive when somebody else holds a title that allows them to review and approve your work. (I personally struggled with that idea for a long time, but finally made peace with it.)

Having a QA person dedicated to make sure your work goes out the door flawlessly is a blessing. These are people that dedicate every hour of their working days to give you all the information you need to correct your own mistakes. We should be eternally grateful about that. Every single day.

Here is the catch: if you want the good stuff that comes from having a QA team dedicated to you, you need to make certain adjustments and learn to work with them.

More than anything else, I'm thinking about communication: a good team fusions developers and testers in one, not separate silos that can't talk to each other (or can, but it's extremely cumbersome and inefficient.)

When organizing a team, this is a good place to look at: How to maximize the information that's shared between these people? How to make sure knowledge is promptly disseminated and acted on by both sides? How can you get everyone to communicate efficiently and effectively?

(This is one area where I think remote work helps a lot. Being able to talk directly to people is a double-sided sword when discussing tasks to be implemented. Although you are maximizing efficiency in the short term, you are putting a lot of pressure in everyone's memory three days from now when trying to remember that same conversation. Working remotely forces everyone to over communicate in writing.)

I'm not sure I'll ever get every single developer that works with me to love our QA team, but I'll try. For now, I'm happy seeing how much progress they are making communicating with each other.

P.S. If you are a developer, and you happen to work with a person that regularly tests your code, stand up from your desk and tell him/her how much you appreciate it (an email will also work.)

Have something to say about this post? Get in touch!

Want to read more? Visit the archive.