Couple of months back I wrote an article on “How to keep good testers in testing position“. There I mentioned one point as to appreciate the testers for their good work.
“Reward testers for finding good quality bugs. Keep some weekly or monthly competitions such as ‘Bug of the week’ to reward them. This will help to build a successful QA team”.
The same concept is used by Eric Jacobson - a software tester, to keep motivation alive in his testing team. Eric found interesting idea to reward good testers. The idea of holding a bug contest. And decided to award the ‘Mercury’ cap to the tester who could log the most bugs in a given week. See the winner of his contest.
A small tweak I would rather suggest to make this technique more effective is to award the testers who will find the quality bug, may be called as “Bug of the week”. This way quality bugs will be the main focus of software testers rather than running behind the quantity. Obviously you should not ignore those small UI bugs also 
I am really fan of awarding testers for their good work. It may be any kind of appreciation. May be a small gift or just few kind words of appreciation from the lead or manager. This will keep the spirit alive in testers to find new and quality bugs.
If you are a team leader, manager or even a team member, what do you think is the best way to keep motivation alive in software testers?
19 comments ↓
Hello,
This wil really form a good Tester’s team. This wil really help team leads.
One of the best ways to keep motivation alive in software testers is just appreciating them for their achiements. And also a lead or manager should support him in all ways, from motivating him for his good work or to being the solace when he is in trouble. And also we need to understand the thing that nobody is perfect in anything.. We do mistakes and it should be excused..
I am glad, I have a TL who is the real mentor in my professional life as a tester. His way of communication and the support given at various times is truly obliging..
Thanks to Vijay or this good article..
According to Bug’s Critical type we can give points to Testsers .
And for every 50 points one gift, for 100 points one gift for every 500 points bonus gift …
i think like this type of situation make testing environment more alive and active
After testing different applications for 3 + years i feel testing is the same old cock and bull fight now as i feel my team is also facing the same thing. i have one more idea i would like to share, buy a trophy or sheld with bold letter written ” TESTER OF THE WEEK” keep a compitition for the team. the most critical bug or most number of quality bug found will be rewarded this prize. each week there is a compitition within the team and the performance increases. this really works.
Hi,
Some how it is right.. I hope it is for the people who works on the same project. But if in a team different people are handling different projects or products it may differ. Because all the products may not have more bugs. Please reply me in this case how to consider..
Thanks
RUP (Rational Uni process) Development Cycle?
if any one know about this, please let me know guyz.
i am in need of it.
The testers have been classified in different terms like..
1.Who finds more critical bugs for the given project..
2.It does not mean that only the more critical bugs it should happen in all the processes..
3.It does not mean that when the Team Awards the member only they do well ,if they have spirit they will,Actually it should be within ….
Hi All,
According to me the tester should be appreciated in appropriate way. Or what we can do is organize a team party to get away from day today schedule. Or we can go to picnic where every one forget everything, can show there real.
Regards,
Pradeep Kumar Sharma
Great idea !!!
no matter how sever it is.
In fact I know couple of companies where the testers name flashes on the display board on weekly basis based on the number of bugs he/she finds.
Given a chance I would reward the tester who finds a LOGICALLY INTELLIGENT bug
@ Kishore
In this case I would keep the reward for each project and not each team.
Regards,
Suhas M.
@ Suhas - The idea to display names of testers on display board seems interesting
Its not about awards or rewards but a small word of appreciation will do and motivates him to come up with much better output.
A token of respect always does matter- And QA is always plays a role of Devil’s (Client
) advocate. And collection of such kind of logical/intelligent bug could go in Lesson Learnt meeting after the project.
I want good placement in Software Testing in City
Different people are motivated by different factors. However, I think that software testers working in a team or independently are motivated by the following factors.
Challenging work (but not too challenging - that could have the reverse effect)
1) (As mentioned by Vijay) appreciation for good work
2) (As mentioned by others) freedom to experiment and make a few mistakes in the process
3) Clarity of work assignments
4) Availability of at least a few senior testers in the organization (to consult in case of problems and get general technical direction)
5) Smooth working environment
6) Opportunity of training and self-learning
7) Opportunity to work with at least a few automation tools
9) Opportunity to work in a popular domain e.g. finance, banking, healthcare
10) Supportive and approachable team lead or manager who provides regular direction and feedback
11) Good relations with other employees
12) Continuity of work
13) No large fluctuations in the amount of work
14) Being consulted on important matters e.g. estimates for testing work, high priority bugs etc.
15) Resolution of any immediate problem being faced by the team member (whether personal or official)
Hi friends,
I had a very good Project Manager who lead the team in a bizarre way. For every quarter of the year, the best tester was awarded with a memento, certificates and rewards based on his/her testing performance. We really miss him.
According to me Software tester feels rewarded once his each and every bug and suggestions are considered without any compromises, which will increases his energy level to find more bugs to increase or maintain his performance.
He/She can be awarded as star of the week or any kind of appreciation will work and motivated the tester
With regards,
Jaishri K S
hi
i want to know How can we breaking down the project among team members in software testing and what is the path for test director,where the test cases are stored.
Please do reply me.
@Stevie
U can break project into different modules and assign them to ur team.
U can upload the test cases using export option in XL.
In TD test cases get saved under “TEST PLAN” tab and test cases can be executed under “TEST LAB” tab.
Hi ,
Anyone give information
1). What is Protocal Testing ?
2). What is the Purpose of doing that Testing?
3). Can I do Protocal Testing in Web Application Project?
4). If do means can u give complete detail about this?
Can u Please reply for this .
Thanks
Vinoth
Leave a Comment