Quality Management Miscellaneous

There is a legend in the Quality Management field and is hailed as cobaini in the quality management field. That's right. He's clushby. Clushby has an important idea: zero defect. The core idea of zero defect is "prevention ". What is prevention? Many people know that the first time they do the right thing. This sentence is simple and difficult to do. How can we achieve this? How can we establish such a culture in the team based on actual conditions?

First, it is pointed out that software testing is not the same as quality management. It is part of quality management. Many people will say this. I know. Do you still need to say it? Do you really know it? Software testing has a well-known concept: TDD, test-driven development, and test first. What does it mean? To put it simply, I will give you a test model before development, and you will develop it according to my model.CodeEnter it in. After the development is completed, you do not need to test the result. It is correct. This is prevention.

If we know in advance what we do is right and what we do will go wrong, we will build the right approach into a model, a framework, a system, and all the work will be done here, the final result is zero defect. To put it bluntly, it is to prevent errors in advance. A problem arises here. How do I know that the model is correct? Or in another way, how can I build a correct model?

First of all, it is actually a philosophical question,10 thousand million people read Shakespeare and there are 10 thousand hamplets. There is no perfect method, but there is indeed a practice that can guide us in this direction. For example, what is the significance of Defect Prevention, fault backtracking, and so on? It is the hope to find out the previous wrong practices and then correspond to the correct practices. These correct practices are the benchmark for future work. By combining many correct practices, you can create a prototype of correct model. Therefore, we will make continuous improvement. This is the purpose of continuous improvement and its core value.

So what should we do after we have a prototype? How can scattered points be summarized together? Learn from previous experiences. What we mentioned above can be regarded as a practical lesson of blood and tears in our actual work. Practice alone is not enough. We need to combine theory with practice. We need to refer to and thoroughly study the summaries of our predecessors. I will not describe the works of masters here. In short, we should not do things on the road and study more, read a good book. Of course, it is better to believe in books than to have no books. Do not trust the authority.

Test management, project management, fault management, and daily requirement management. To put it bluntly, build models one by one. Speaking of this, two problems may arise.

First, is the model a process, system, or framework? Yes or no. At the beginning, this may be the case, but the final goal is not. The ultimate goal should be to form a culture and a management product. For example, we often say that the spirit of a team is different from that of another team. Working with one team is smoother than the other. We can't see it, but we can feel it.

Second, is the model heavyweight? Will it imprison people's ideas without innovation? Similarly, no. The concept of software factory has been around for a long time. Just like my blog name, software practitioners are essentially migrant workers. Don't tell me anything about the Golden Collar. It sounds disgusting. But at the same time, creation comes from life, and innovation comes from the simplest daily work. Can you come up with a reliable idea with your head? It is not just a certain system that binds people's thoughts, but more people themselves. There are countless facts in history that prove this point. For example, in a certain institutional age, will China have no masters?

I was excited by the recent failure management and daily demand management system, but I was confused about my ideas and expressed like a statement.