Bug Bash is referring to an event that everyone focuses on finding and fixing bugs, but nothing else. It is an indication of the software having a severe quality issue and cannot be taken care by the normal process.
Having a bug bash may mean that QA needs helps as they did not uncover bugs while they should. However, in another angle, it may mean that during the normal process, QA was not given enough resource or time to run the test. The defects of products may be accumulated over time. The problem is that the investment on QA may not be linear comparing to the growth of development. When we count the scenarios to be covered, when the software is getting complex, it will grow very fast while the development resources including maintenance does not need to grow as fast.
Slowing down and giving QA more authority as a gate keeper may be sometime more important than having a bug bash.
No comments:
Post a Comment