In the implementation of the software development, SQA is a separate role, and the SQA report is also a focus of its work. How to grasp the objectivity of the SQA report and the appropriateness of the SQA report is a fairly important issue.
In SQA work, SQA reports can easily lose a potency; I believe that similar problems have been met in organizations that have implemented SQA work, especially in the enterprise that is now implemented; Next, SQA's work often reduces the data of statistical defects, reviewing some irrelevant issues, and debates some irrelevant issues. In the case of SQA organizations relatively conservative. Even will not dare to agree to the release and delivery of any product. When the project summarizes the meeting or a higher level meeting, Luo lists a surprising defect. Then, developers have to make a lot of time to modify this. The result, but most of these defects or Finding is a defect that does not affect the quality or delivery of the software, spelling errors, statements are not available. When these so-called defects are repaired, they can be delivered.
So how to grasp the SQA report a simple principle, it should not be controlled by the software technical manager or project manager. In the process of project progression, especially for contractual projects, the progress is always very nervous, and technical manager usually does not want to support incomplete, document is not comprehensive, and there are some developers itself The report of SQA, etc. SQA should be in this case, there is a channel that is capable of reporting to a higher level management. And clear the priority of the problem, and strive for problems. And determine the resources and time required to get a repair key issue in the process of negotiation.
During the SQA report, the elevation of the report level is required to consider and weigh. In the process of project throughout the project, the report grade is low, which is conducive to the close relationship to the development and other collaborative working groups. And there is a problem, but it will reduce the extent of the report. Different organizations should define relevant mechanisms and channels according to the cultural and self-projecting of their own organization. --SQA cannot report to the project manager - SQA should not leap over the local organization - the maximum management level between SQA and local enterprises can only have a management level - SQA and the company's advanced quality manager should keep it at any time One connection - SQA is in the implementation, and it is possible to capture the on-site person in charge or executive person who is very concerned about quality. And report to them in time.
The time of SQA's work in China is not long, and there are also some misunderstandings of SQA. The obstacles in progress progress, the lack of creativity of work itself will make SQA easy to lose level. Thus SQA may become a statistical official. It is difficult to adhere to the idea of implementing the abstraction. Sign in feasibility and rationality during the execution process.
