Project-[Quality Management] Quality Supervision

The phone rang on the desk, and I was impatient to pick it up because I knew that the customer called me. In the past few days, customers have complained about the same content: There are many System bugs after the launch.

 

Many familiar terms about bugs, although we all know that there is no software without any bugs. Let's take a look at all the patches at Microsoft. However, if your bug reaches the level that affects the normal functions of the system, it will be troublesome.

 

Now I have such troubles.

 

The current software company is equipped with the quality department (there are also cut corners without quality department), our company is no exception, also known as the quality department. This is because it is no different from the Bodhisattva in the temple.

With the quality department, the company never counts as a tester when assigning project team members, because the company thinks there is a quality department and you can develop it.

 

This is a good thing, but the problem lies in the quality department.

 

Let's talk about our colleagues in the quality department. There are not many people in total, and it seems enough to deal with this project. Don't worry, we have 80 developers in our company, and there are about 20 projects at the same time. For example, one person tests five projects on average.

 

Obviously, the manpower is tight, but the problem is not complete. As the cost center of the quality department, the boss's abacus is very refined. I have invested RMB in the quality department. I have made reports (paper and printers or companies), and even ke Ledu has won. What else can I do.

 

Under the boss's low-salary policy, our company's quality department can only recruit interns, and the number of students is limited to three plus an experienced manager. This experience is still in the manufacturing industry. Actually, the number is not large, not to mention the poor quality.

 

In order to better carry out quality management, the boss's perspective is to better use the money invested in the quality department, in addition to testing, the Quality Department is also responsible for contract documents, project reports, and internal audits of CMI (our company has passed cmmi3 without a project management process), network management, and database management. This time the number of low-quality candles is still two points.

 

Colleagues in the Quality Department "Work hard" based on the principle of how much one person can do with one hand. They work hard because they have set a record of zero overtime work in the history of our company. (When they worked overtime, all the programmers in the company were saying, "Do you know? The quality department has worked overtime ")

 

Now the situation is clear that this quality department cannot complete the project test, at least it is impossible to meet the customer's requirements.

 

Since we can't rely on them, we can only rely on ourselves.

 

I can do things on my own and never bother others-two people turn to actors, Xiao Shenyang

 

In fact, solving bugs is not difficult. What is difficult is how to reduce the appearance of bugs. Because I will not estimate bugs by throwing a shoe or throwing a dice. I can only use tests, but I can only use my people to do this job. I really envy the gods, they will become soldiers.

 

Two challenges can be tested.

First, programmers do not like testing.

I can understand this. Just like playing "xianjian" in the past, will I play it again for a certain item I didn't get? I believe someone will do this, but most people won't, at least I won't. So I believe that most programmers will not repeat the code they have developed.

 

We are not in the era of planned economy. We pay attention to "one line of work and one line of Love". The current slogan is "one line can be done with one line of love ". Therefore, you are not willing to do things you don't like. Since it is not good, why?

 

The second problem is that testing requires manpower and time.

You must exchange resources for quality. Resources are always scarce. In my project, resources are scarce like water in Kuwait. This is not enough water to drink. Now we need to take a bath.

 

If there is any difficulty, you need to do it without difficulty in manufacturing.

 

Based on the existing form, I will change the current project's time frame.

 

My team was fully engaged in production, on the grounds that the first milestone had to be completed within two months.

 

My team is like a gunshots of doping. They rushed to the hill. Although there were no medical soldiers behind them, they were still brave.

 

Now, I want to change the overall attack type to both defense and defense, which will reduce the development speed, but will solve the quality problem. After all, customers will not pay for products full of bugs.

 

Qi gefei (a tough child) put half of the time on the test, and as a project manager, I put 70% of the time on the test. Others must perform a two-hour test every day. And cross-test. Cross-testing aims to solve the problem that programmers do not want to test their own code. But on the surface, they do not want to test their own code, but do not want to test others' code.

 

The painful test (really painful) was conducted for two weeks, with remarkable results. Nearly 120 bugs were fixed and the system stability was greatly improved. The cost is that the development speed is reduced to half of the original, and the whole group of people sacrificed two Saturday breaks (no overtime), and I spent 300 yuan (invite her to dinner) to coax my girlfriend ).

 

After the patch is sent to the customer, the customer is satisfied with the modification result because we sent the bug list to the customer along with the patch. The customer saw the 120-line list, I think we have done a lot of work. It's hard to get credit.

 

However, such satisfaction will not last long, because the customer's satisfaction ultimately depends on the quality of the product.