I have been buried my head, suddenly Ignore this important issue - Who is my customer?
We usually understand that customers refer to the outside customers, we must give our work results to him / her, of course, work results are also called delivery results, need to make customers satisfaction, otherwise, customers will not buy. According to the results of the work, in order to make anyone who satisfied, the customer has a broader meaning.
Individuals in the organization have their own customers, and there is no one. For individuals within the organization, the biggest customer in the heart is his / her superior leaders, maybe someone is myself.
For a project person in charge, in addition to superior leaders, customers have external customers, external customers will affect the satisfaction of superior leaders, sometimes who is the biggest customer in my heart, I am afraid that I will not be clear. . However, your degree of satisfaction with customers will definitely affect the quality of your work.
Software development projects are composed of one process and process, demand analysis -> design -> encoding-> test, the quality of the results of the results of the result of submitting to external customers, not to say which process is determined. If the subject of each process looks like your own customers, it is very impressive to the satisfaction of your own results, then we can improve overall quality.
However, I see the phenomenon (although a small number, it is enough to cause a big impact) is not the case. The design book written, the implementation personnel have no way to implement; the completed code is not debugged, and it is not allowed to give the testers, and even the basic function is not working.
I have said that "SQA is for project service" in front of everyone, and the purpose of SQA is to ensure the success of the project. " At that time, I value more about the project team's understanding of SQA work. But later, gradually, a tiny change occurred, but the consequences of this change were severe (at least in my opinion). It turned out that SQA was a project service. Later, it was understood to be "SQA as project team service". I invited the project manager to give advice on SQA work, resulting in "SQA is the project manager service". God, I actually make such a thing, SQA is serving the project manager! ? Obviously, SQA (Software Quality Assurance) is to ensure that end customers' confidence in the project should be to work at the perspective of external customers. If it is a service manager service, then a little track is SQA, you should change a job name, such as the "Project Manager Assistant", so as not to tarnish the name of SQA.
The external customers facing the project manager have been XX. For the submission of the results, it is always careful when testing the XX company test, it is afrained. This is not the case when developing a regeneration to the Beijing internal test group. Before submission, the development movement is as fast as possible, no matter if there is any problem, first done in time, there is a problem, etc., there is a problem to solve it when the test phase is. The view to the test group is: I will definitely have a fault for your program. You have gave me, didn't find it, and I submitted to XX Company's question is your fault. Test staff can say that it is a responsibility. It is not a good or bad of the right to say the procedure, the measurement is good, develop the table, and finally develop, if you miss a few bugs, let XX The company tested, then it is not, the quality of the project is not good, "why others can measure, you can't measure", there is a little neglected, really cause bugs, not testing, but Development, of course, this is not a test.
Then there is developmental start to guide the test, how to do it, test becoming the subordinates of development. The test began to develop, developed into a real customer in the test heart, the tester feels that these bugs are their own mistakes, there is no sense of finding bug, the only feeling is to find a bug, the chance of developing is less A bit. However, when the ear is born, or when the defense line has collapsed, even the last thorns have not, and some are just opposite and tired, and there is no more and more bugs that are not found. Since everyone who has developed will definitely have a bug, why can't you understand the test, there is inevitable BUG. In other words, if the test cannot miss a bug, you can also ask for a bug that can be required to develop. Development can be said that the code quality is not a day that can be basically no bug, then the BUG that is not lost is also a day. Therefore, the development does not have to accuse the test, and the test does not have to blame the development, because everyone is half a catty.
We should give the test rights to judge the quality of the development and submission. If there is no standard, there is a right to return processing, reach the requirements, then start testing, the test submitting the software quality situation, this report should be used as an organization to develop. Important reference. Perhaps this can make the development of testing as a customer, not a subordinate. The status of the tester will also increase, when the test department (or the quality management department) will not be willing to go, or it is treated.
2005-6-23 in Beijing
