Analysis of Common Psychology of various personnel during software development

　 " Software Industry, people-oriented ". The common psychological performance of various personnel involved in the software development process has a significant impact on the entire development process. As a project Management It is very necessary to analyze them one by one, find out the knot, then remedy the problem, increase Communication to improve development efficiency.

Knot 1: users, due to their different ideas, domestic users prefer to see a real "thing ". The review and signature of each stage of the traditional development method often leaves a classic joke: "Yes, this is what I want, but it is not what I want ." In addition, because the customer does not see a molding "thing", it is a headache to sign the confirmation report. What's more, the customer's requirements may change at any time. However, in the beginning, we must give users a "satisfactory result". Such scenes do not actually exist and are impossible.

System Analyst: what the system analyst thinks is often unnecessary for customers. What the customer thinks is not understandable to the system analyst. The most annoying thing for system analysts is that customers are constantly changing their needs (especially in the case of in-situ conversion ). System analysts are most concerned with implementation convenience when designing a system, rather than system expansion and updates. System analysts are always doing "thankless" and often make many "assumptions" for customers in good faith ". In fact, these "assumptions" often deviate from the customer's actual situation. And the biggest "fatal injury" to system analysts is: Psychology But these details are often the key to system success or failure.

Conclusion 3: programmers : Software enterprises in China are still in the "workshop age ". So far there are many programmers who are full of "digital heroism" and love to be unique. They prefer to code the project as soon as they get it. Then I will tell you how good his code is. They will regard the detailed design specification as a "Shackle" to them ". They think that the program should be an art, and they are "masters of art ". Therefore, the "old daily footprint" they left in the program can be seen everywhere. They like it. Work To ignore the existence of others' values.

Conclusion 4: test engineers often think that "I have carefully reviewed and tested it, and there will be no more errors ". In fact, software with no errors does not exist during running. The reason for running errors may be due to external factors. Test Engineer It is often more inclined to test the software itself and ignore the running environment. Once delivered and used, complaints from customers often say "this is not entirely caused by the designers and is irrelevant to me ". Therefore, it is difficult for you to determine their sins ".

How to solve these cases. "The first is communication, the second is communication, and the third is communication ". Customer cooperation is a prerequisite for system implementation. From project start to end, user participation is essential. You must let the customer see that you are actually working for them. In this way, you can be psychologically recognized by the customer. After the original concerns are eliminated, the process will be much smoother. In terms of system analysts, during the design phase, all possible Problem On the desktop, participate in the discussion with the customer (conditions, characteristics, effects, and consequences of the problem), solve the problem together, and bring as few errors as possible during analysis and design into the next development stage. Programmers should not bother to explain to them Programming The importance of rules. From the psychological aspect, we should adopt a positive guidance approach to give programmers more "supplements". Two more comments will often bring very good results. After all, programmers are groups of young people, it cannot be cracked. In addition Team Spirit is also essential. For test engineers, we need to respect them (many domestic Company Testing engineers are relatively low) to make them aware of the importance of their work. They also need to constantly cultivate their patience, sense of responsibility and careful style (in this regard, female test engineers are more advantageous ). Listen carefully to their suggestions and understand their psychological feelings. After solving the mental symptoms of the above personnel, you will find that the development efficiency of the entire project has been significantly improved.

I personally think that a good software project manager should first be a manager Psychology Experts. People are the foundation of software companies. To understand the psychological activities of the project developers, the project managers can take advantage of the benefits, eliminate undesirable human factors, improve the team cohesion and work ability, and thus improve the development efficiency.

　Author Profile

Zhang Hua, Bachelor of Science, system analyst, Software Engineering Experts Network Expert Group member. Rich software project development and management experience, skillful use of play Case, Power Designer, Visio, smart draw and other design tools for project analysis and design. He has many years of development experience in Java, C ++, Delphi, VB, assembly, and other development languages and is familiar with Japanese software enterprise development and management models. Contact Email: charmhard@elong.com

Note: The above content comes from the Internet and I am not liable for any joint liability.

Article transferred from: http://pm.csai.cn/hr/200801282157071950.htm