One of the biggest mistakes in software development projects is to adopt Quality Police Policy for testing activities. In this post, I will explain what Quality Police Policy is and how it affects software testing and software quality.
A simple explanation of Quality Police Policy is to keep testers away and not involving them till late stages of software development. In other words, testers are ignored and their role is limited. The only thing testers might have is the initial customer requirements which most probably are subject to modifications. The testers then wait for next software release. They are not involved during requirements clarification meetings, design meetings or other project-related meetings. Whether this is done intentionally or unintentionally, there are always high expectations by management that the testers will (and must) find all the issues in the software. (more…)