这个问题, 我想是大多数公司或是QA manager的梦靥. 一方面找不到好人才, 一方面人才也不易留住. 很容易地, QA不是离职就是换跑道到RD去. 让我们来看看Microsoft资深的QA manager如何看待这个问题.
在某一场合, 作者被问到一个问题: 你如何保持在QA这条路上, 而不会想转换到RD去呢?
他说他已经听过很多次这样的问题. 许多人把QA视为是RD的一个跳板, 一个先期训练中心. 他说如果是这样也不错, 因为那将会有许多RD知道QA在做什么, 会比较注重质量, 也会比较容易和QA沟通.
作者也认为并不是因为RD要写code, 所以QA想过去. 其实QA自己也是需要写code, 去做automation或是帮助
测试更方面. 他认为QA会想离开是因为太多QA manager无法求新, 只考虑shipment和 schedule, 缺乏有求新求变的环境和心态.
而至于愿意留下来的QA, 则是因为在team里面, 他们有机会去做invent, investigate and discover, 使得他们有成就感.
所以如何让你的QA愿意留下来呢? 让他们有机会去创新. 如果他们都只是focus 在
test cases execution和ship schedule, 那大家都会想跑的
以下是一些读者的响应
===============================
calkelpdiver said:
(1) lack of credibility & respect, lack of pay, lack of support, insane work schedules, finger pointing
(2) getting the opportunity to do new and innovate things in this line of work doesn't come often for the average tester in the average company (Microsoft, and other large shops may be different).
(3) Want to earn more money (RD's pay is higher)
===============================
swn1 said:
他提出一个可能的改善方法: rotation
Assign testers to development teams, assign developers to test rotations.
Developers became very conscious of the need for documentable designs, meaningful messages, and such. And customers were shocked to have the phone answered by someone who understood and could actually fix their problem. Good for everyone.
===============================
ru_altom said:
他认为rotation不太可行, 原因如下
(1) 你需要假设RD是一个好的QA, QA 也是一个好的RD
(2) RD 和QA的mindset不同, A tester will write code to break someone else's code, while a developer will aim to write unbreakable code.
所以他赞同JW的作法:
Innovation is the best way to keep your testers (and developers as well) content and at their best. Give them a chance to invent, to find new ways, to try their ideas - and they won't leave, not for another department and not for another company.