Development organization participation

11.5 Development organization participation

The development organizations that will be monitored by software quality practitioners must have some say in the criteria and methods to be used. Acceptance of the SQS by the rest of the organization is the critical factor is the success or failure of the SQS.

Openness by software quality practitioners in the beginning of the system will enhance openness by the developers later on. No one likes to feel as though someone is constantly looking over his or her shoulder. Yet that is exactly the impression that software quality practitioners can give if they have not requested and welcomed participation and involvement by the development groups in the preparation of the SQS. When the developers have been a part of the overall planning and development the system, there will be less resistance to the requests by software quality practitioners for information about progress and status, let alone data on defects being found.

Participation by the developers can also help create more meaningful measures of progress, trends, and areas in need of additional attention from the SQS. Most people know their skills and limitations. If they have the attitude that someone else is going to discover and tattle on their weaker capabilities, there is resistance to exposing those areas. On the other hand, if given the opportunity, most people will point out those areas in which they feel they can use assistance. If that assistance is provided, there is a growing trust built, and fear and suspicion are reduced. By maintaining close contact with and participation by the developers during the planning and implementation of the SQS, the software quality group can build a feeling of SQS ownership on the part of the developers.