Quality Hunting

Delivering software with the right quality at the right moment is only possible if there is a clear view of what quality level is needed to get the pursued business value (which is elaborated
in the requirements). Also, the people involved need a clear view of what the actual quality level currently is. Static testing and dynamic testing, by people in IT delivery teams, contribute to the
understanding of the current quality level. However, part of the image of quality depends on the impression the stakeholders have from their personal experience. To support building such
personal experience, you can organize a collaborative activity with a gamification approach, so-called quality hunting (note: this is not the same as bug hunting).

What is Quality Hunting?

Quality hunting is a gamified event where quality hunting teams (typically half the size of an Agile team, so about 4 people) compete to give the most valuable assessment of the quality level of their test object in a limited timeframe.

The main goal of quality hunting is to get a shared view of the quality level of the test object. By having multiple quality hunting
teams, consisting of stakeholders and members of IT delivery teams, competing to get the best understanding of the current quality level, these teams are challenged to come up with fresh and innovative ways to assess the quality and to give a good insight into one or more aspects of the quality level.