Eight rules of software quality management

Quality ManagementIt is a very important part in software engineering. No matter how subtle an algorithm you have, how advanced technology you use, or how many strong designs you have, in the face of quality control or quality management, none of these are possible. Here, there are some quality management rules that can benefit software users. If you say "Quality Management" in a word: In the face of a software that requires long-term improvement, when users or managers say they have a complete and basic trust in the standards provided by an organization.

　　Eight rules of software quality management

The following describes eight quality management rules:

1. Always from the user's perspective: "whenever and wherever we are, we need to understand the current or future needs of the user, and be able to meet the user's needs, or even exceed the user's expectations ."

This is the top priority of the entire software project. In a sense, quality management is to manage the quality of user needs. This requires the relationship between quality management and users, as well as the user needs and the entire team (Development Team,TestGroup, product group, project team, etc.

2. Leadership: "leaders need to build a united and clear team. This team can create and maintain a good internal atmosphere that enables everyone to participate and achieve the goal of the entire team ."

In this regard, we need a forward-looking lead to create a mutually trusted environment for the entire team. Advocate honesty and actively guide team members. This can motivate everyone and create a strategy (such as a reward and punishment mechanism) to achieve these goals.

3. Active participation of team members: "team members always have different division of labor and different responsibilities. If only all team members are involved, the entire project or all parts of the software, all aspects can be used perfectly."

This gives Team members a sense of ownership and makes them feel like they areWorkOr the task owner is the key to whether all members can participate actively. Here, we also need to make every participant focus on the user, help and support team members, and create a satisfactory working environment for them.

4. Process Method: "We need a very efficient process or method to integrate all resources and daily work activities to form a production line model"

In this regard, define a proper process (note that a proper process is here, and a good process is not necessarily appropriate ). This process requires you to determine the input, output, and functions of the entire daily production activity. Risk management, assigning responsibilities, and managing external and internal users.

5. System Method management: "determine, understand, and manage a system-related process so that the entire team can improve themselves effectively and quickly ."

This defines the organizational structure of a system, which is efficient and effective. Here we need to understand the requirements of the Team (hardware, software, personnel, etc.) and some possible restrictions. In this way, we can effectively manage the entire team system.

6. Continuous Improvement: "continuous improvement is a permanent goal that a team needs to set for itself"

In this regard, the improvement of work efficiency is the top priority of the whole improvement. In terms of work efficiency, it depends to a large extent on the improvement of the work process. Therefore, process improvement is very important and requires long-term efforts to improve the work efficiency. To achieve this goal, we can generally use a loop like plan-execute-check-summary.

7. Talking about facts in decision-making: "We can make effective decisions and actions only after analyzing actual data and information"

In this regard, we need to pay attention to the collection of daily data and information, and we need to measure the accuracy of the collected data and information. In this way, we can make decisions and actions based on the correct data.

8. Mutual Benefit: "Although each department or sub-team in a team is functionally independent, A mutually beneficial situation can enhance the overall capabilities of the entire team or company and create greater value."

In this regard, we need a healthy relationship between teams. Good communication can only benefit the team for a while. It is only a long term to establish a long-term mutually beneficial relationship or situation.

Eight rules of software quality management