Does QA should be independent of the project group?
At the weekend, I saw Qilo. Point Break, starring Levis. The plots in the film are still unwakenly sleeves. It is a policeman who has just graduated from the police school to help investigate a serial bank robbery. The gang will make a crime, the trail is secret, can only be inferred from the blurred banking camera. It is possible to surf your lovers. In response to the case, strengthening the Southern Casa Beach, I met the beautiful surf coach Taylor, and more than Taylor's forebear boyfo in order to live and die. However, as the case is gradually exposed, it is found that the original emparts is the head of robbery group, facing friendship, love and law, strong sorry is difficult to choose ...
After reading it, I suddenly passed a trace of thought from my mind. The QA should be independent of the project group? To a certain extent, QA also acts as part of the process police role (based on the three rights discrete between SEPG, SEG and QA). So, can QA can also learn from the working model of strengthening? The answer is yes. On the one hand, surfing, skydiving, feet ... to understand their language, thinking, and behavior, more real, more deeper, and deepen their deviation between their decentralizes, and gradually guides them to the right track. On the other hand, in the functions / administrative independent of the supervisor (project group) to ensure the objectivity of its own independence and evaluation (that is, the gains between affection, reason, and law).
At present, many software companies in China are exploring the implementation model of QA, and there are many peers to present or suspect "Qa is the product of Western culture, not suitable for China." From my own understanding, they often go to two extremes: do not qa completely independently of the project group, do not fully integrate into the project group. For a fresh example, I am very familiar with a company (more than 200 people, most items in 100 people, more than 2,000 months), in 2002, the work product of all project groups will be completed (Such as project planning, progress report, demand, design, code, review record, test documentation, etc.) submitted to Quality Management, reviewed by the personnel of the Quality Management Department. The examiner and the project team are completely detached, and the examiners do not have technical research and development experience, and the issues that are reviewed are almost all the things of chicken fry. What is even more, the deputy general regulation The goal of the Quality Management Department is 300 errors per month, and it will not be deducted. On the other hand, developers have been issued and they must be deducted. As a result, it is often seen that the developer runs to the Quality Management Department to quarrel, and argue for a small format problem ... later, that is, in August 2003, the quality supervisor changed, came to a thorough change, QA is all put it The development departments, the result is that jumps, and the postgraduate postgraduate, there is one of the rest. It later, that is, recently, the previous department secretary turned over when it was QA, even more interesting, the secretarial of the front desk also came to QA ... Just like this, the job of QA turned into the department's contact (Similar secretarial), For example, to help the payment of the payment, before the external audience remedy, the document is completed, the Quality Management Department will meet no one to participate in the time ... QA "Q" ......
From the above description, we can understand that it is not advisable whether it is completely independent of the project group or full integration into the project group. QA should be independent of the project group independently of the functional and administrative level, integrating into the project group in the business and work level. Just like streptology, he is a policeman (FBI) in its functions, but in the work of the criminal gang. At the operating level, this independent and integrated dual role of QA is a very difficult-balanced thing that requires the mechanisms of organizations and QA's personal qualities to protect.
Learn this, let you take less in the QA mode exploration.
