Bug review - reducing WAD bugs and Sharing with team what the best bugs are like?

As the key output of test teams, we have to monitor our bug quality, reducing WAD bugs, invalid bugs (raised dur to invalid set up, incorrect understanding to requirements, etc). Moreover, bug severity is very important for us and product team, we should monitor bug severity, incorrect severity level will mislead team, eventually have side impacts on project progress.

For example, if one defect didn't lost functionality of one feature, just have some impacts on end users, you shouldn't raise the defect as a major bug. In other hand, if the defect lead to lose the major functionalities of the feature, that should be a major issue, SW team should respond it within 24 hour, and keep the fixing progress once a day.

So if you are a test leader, test manager, a big responsiblity is that you have to coach your team to raise approprate bugs, and that is our topic today. We always drive another series of activities - Best CRs competetition. That is a good thing for test team, through each activity, your team will know what kind of issues you or SW/Product team really care, and what kind of defects really improve our product quality. We provided a little gife - movie tickets or cake coupons to thos guys who won the competetition.

BTW, not all WAD CRs are bad, some of them are very good to product, just SW team follow up requirements or their technique design, so they reject to fix them. By this case, we have to look for help from SW management team or QA team, maybe the defect can't be fixed on this product for schedule reason, but that can be considered on next product if they really bring major benefits to our consumers.

In summary, that is a routine task, you have to put our energy, passion and effors to make them well done.

Good luck, guys.