IT Employment

Ask something
Discussion Locked

Uniting Developers and Testers

0 helpful
5 replies

by jashburn

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The company I work for has separate departments for software developers (Development) and testers (VV&T). Development and VV&T are in the same location, but are housed in separate buildings. Only completed development projects are sent to VV&T for testing.

What I've noticed here is a very prevalent "us vs. them" attitude between these two departments, each perceiving the other as the inferior half. May I know how your company tackles this problem. I'm particularly interested on how collaboration between these two departments can be improved, and such ill-feeling can be minimised. Your views, advice, and even links to papers/articles that discuss this issue are much appreciated. Thanks.

5 replies

by realgem

The we/they thing can be reduced in several ways.

First of all, the geographic separation should be minimized. Eating in the same cafeteria will help each group recognize the others as human.

Encourage (or require) movement between the groups- this will blur the edges. It will also force people to put their money where there mouth is. There's nothing like wearing another man's shoes to appreciate their path. You can encourage the movement by making it a prerequisite for advancement, applying a financial incentive for the transfer (e.g. an additional 3% on their next increase, say). This should apply to management too, since I'll bet they promote this attitude whether they mean to or not.

You can also consider setting joint performance goals. Measure the development group by the number of defects found in testing in addition to their other objectives. Software should be designed with defect correction in mind, too - complex software is difficult to debug and fix.

There will always be some room for improvement, but perhaps this will reduce that room somewhat.

by jashburn

I like the idea of horizontal movement. Permanent movement would be a bit "difficult" as this involves management acceptance from the two departments, but temporary 3- or 6-month movements would probably help.

Also, setting joint performance goals for the relevant teams across the two departments is a good idea. It would promote "product ownership" in the teams, and they will have to work together in order maintain/enhance their reputation.

by istal

To be the FIRST or the SECOND, that's not a question.

They all eat and they all drink the same water. Without the first or the second part - there something fails, but if there are all of them the system works.
That is all the Philosophy about your question.

All best.

This discussion is closed to new replies.