|
How do you improve the relationship between developers and testers?
|
|
|
|
Q: How do you improve the relationship between developers and testers?
A:
In the SDLC, there is a potential conflict of interest between developers and testers.
Developers can experience feelings of frustration, anger, and bitterness whenever they have to face the testers and their bug reports.
When there is a debate, as to fix or not fix a bug, the debate between developers and testers can get nasty.
If the level of understanding between the testers and developers is insufficient, the developers may start thinking the testers are troublemakers,
and vice versa.
In defense of developers, when you develop a product, it will have bugs. In defense of quality, the bugs are there to fix.
And in defense of testers, finding bugs and breaking the product is the job of testers because, from a business perspective,
the cost is significantly less and customers are much happier, if the product is bug-free before it's shipped out the door.
In defense of management, the battle between the two groups is a necessity, because it creates a balance in the team,
and because it generates the required momentum to move ahead faster, and because it produces a better product.
Solution #1: When you're a developer, remind yourself that the ultimate goal is to maximize the value of the software.
Remind yourself that it's the mission of both developers and testers to ensure that there are no bugs in the software.
Remind yourself that it's up to management that the bugs are handled correctly and given the right priority.
Solution #2: When you're a manager, do allow the testers to advise the developers by pinpointing areas where the software is error-prone.
Allow the two groups to have meetings to discuss the software design process. Allow the two groups to work together in finding defects beforehand.
This way the developers become more aware of the different issues and concerns, which will translate to fewer bugs and better cooperation
between testers and developers.
Solution #3: When you're a tester, and when you're writing a bug report, do share with developers the test tactic you have employed.
Sharing your test tactic will help the developers to re-create the issue, to better understand the issue, and to test better before delivering
the product to you.
Solution #4: When you're a manager, remind your team that product development is teamwork,
and teamwork is based on the right attitude and cooperation of all team members. The relationship between testers and developer will be friendlier,
if you call for teamwork and cooperation. Product quality will improve, if you remind your team that the ultimate goal is to develop a better product.
Link to this article!
Link to this article from a forum!
|
______________________________________________________
|