How can project managers improve software quality?

Physical Quality refers to the quantity of substances. No matter the position, state, or shape changes, the quality of an object will not change. It is the physical property of the matter.

The degree to which the inherent characteristics of quality in life meet requirements. Obviously, I think the software quality we often say should belong to the second type.

When we are working on software, a requirement on the project manager is to ensure the quality of the software, but the quality is easy to say, but it is not easy to implement. The reason is very simple, this quality is a bit illusory. When I want to buy clothes, I think the quality is not good, but I can't tell how bad it is, the seller also said that the price quality is already the best. In fact, everyone does not know what quality is, but it is just an interface for bargaining.

We often hear from our leaders that, especially to project managers, we must ensure the quality of our products. However, no one can come up with standards for quality.

I have been a project manager for several years and have heard the most about quality and efficiency.

I have the following feelings about quality:

1. Low software bugs do not mean high quality.

2. Testers cannot guarantee the quality of the software.

3. Quality is a compromise between the two parties at a certain price (this is just like buying and selling clothes ).

4. Good Quality is continuously repaired (or reconstructed.Some of us think it is impossible to produce or define high-quality software from the very beginning, just as we plant crops, we plant crops in the ground, and we still need to weed out. If the weather is dry, we need irrigation, but if the wind adjusts the rain, irrigation is a waste. Because we cannot predict whether a year is going to suffer, how can we define what we do at the beginning to ensure quality.

The best way to ensure quality,It is to constantly interact with customers, let customers provide feedback, and make appropriate corrections (note that we only get information from customers, not requirements )..

Speaking of this, it seems that it has little to do with the project manager. In fact, the most important job here is that the project manager should complete the following key points:

1. find a balance between the customer's requirements and the quotation of the project to define the features and details of the product. This often requires negotiation with the customer, we are often disturbed by developers.

2. grasp the "degree" of the Project. Do not let the developer over-development lead to too long time, performance, XX thoughts, do the customer care about, but do not be too far away from the customer.

3. Think about how to promote products to services.

In short,The quality of software is to improve customer satisfaction.. It doesn't matter if there are any bugs or if the system is fast or not. Some customer requirements are to quickly occupy the market and occupy users. Our developers all know that Firefox is easy to use, but its market share is still inferior to that of IE, which is the best communication software, in China, it is hard to compete with QQ. If the system does not have a bug, the system will also walk gently, just as it gently comes.