Bug Hunt的替代品？

Question

Recently, our QA department has been running bug hunts. Once a sprint all the teams do 10 min demos then they spend the whole day submitting bugs for a feature getting ready for release. They've been fairly successful. We find lots of bugs before they hit production, it makes the higher ups really happy to see results, and the winning QA members get lunch.

However, I've noticed a very hostile tone encroaching from the teams themselves. We have 4 scrum teams and the bug hunts have been pitting the QA from each team against each other. This starting to cause a headache for myself and the other QA leads. Testers trying to game the system, complaints about other teams cheating, and generally less than happy office chatter about the hunts. Everyone seems to really enjoy the hunts, but everyone has a reason as to why the other teams found issues shouldn't qualify or they just have general paranoia about what the other team is doing.

Has anyone else had to deal with conflicts arising from bug hunts before and if so, how have you gotten around them?

TL;DR Our scrum teams hunt each others features for bugs. Originally this went well, now QA spends as much time, if not more bickering over validity of found issues. Anyone have an alternative approach?

Answer 1

From my point of view, it seems that the very same question was better answered on another website (ie Software Quality Assurance and Testing - Stack Exchange )

The answer link is below:

https://sqa.stackexchange.com/questions/2726/bug-hunts-and-possible-alternatives

Answer 2

Buy everyone lunch - don't make 'losing' a punishing experience. You should all be striving, as a whole team, to maximise the quality of the end product.

As a matter of setting a personal example, especially if you can't change management's position overnight, is to take the team that find the most bugs in your area out for lunch/dinner/drinks/whatever. Thank them for finding stuff before the customer. Don't begrudge them a good job.