"Software industry, people-oriented". The common psychological performance of all kinds of personnel participating in the software development process have a great impact on the entire development process. As a project manager, it is necessary to analyze it one by one, find a heart knot, then the disease, increase communication, and improve development efficiency.
Symnary 1: User, due to the difference in concept, domestic users more inclined to see a real "thing". The review and signature of the traditional development method, the left is often the classic joke: "Yes, this is what I ask, but I don't want." And because the customer can't see a formation Things, let him sign the report on the confirmation report is also a more headache, let alone customer needs may change at any time. However, at the beginning, it is necessary to give the user a "satisfactory result", such a scene actually does not exist, and it is impossible.
Symopoly two, system analysts: System analysts believe that things that should have often feel unnecessary. Customers feel that there should be something that should not understand. The most annoyed thing for system analysts is that customers keep in changing demand (especially the situation in which they are in place). System analysts consider the most convenient implementation when designing systems, not system extension and update. System analysts are always "hard-tolerant" things, often doing so good to be a lot of "hypothesis" for customers. In fact, these "hypothesis" often deviate from the actual situation of our customers. And the largest "fatal injury" of system analysts is: System analysts often ignore some details, but these details are often the key to system success or failure.
Symomidism: Programmer: China's software companies are generally in the "workshop era". There are still many programmers, "digital heroism" in the head, like unique. They prefer to have a project immediately code. Then tell you: His code is excellent. They will regard detailed design instructions as a "桎梏" for them. They think procedures should be an art, and they are "master of art". Therefore, "old daily footsteps" in the program can be seen everywhere. They like Tiama to make a way of working, and they tend to ignore the existence of others' value.
Symomidism, test engineer: Test engineer often thoughts "I have been carefully reviewed and tested, and there will be no more wrong." Software does not exist when there is no error when running. Because the cause of the wrong cause is more likely to come from an external factor. Test engineers tend to more inclined to test the software itself and ignore the operating environment. Once the delivery is delivered, the complaints that customers have generated tend to say "this is the incomplete cause of the designer, and I don't cohere with me." Therefore, you are very difficult to determine their "sin".
How to solve these psychosis. "The first is communication, the second is communication, the third or communication." Customer cooperation is the premise of system implementation. From the beginning to the end, the user's participation is essential. You must let customers see: You are actually doing things for them. This allows you to get our customers from psychological recognition. After eliminating the original concerns, it will be more smooth. Secondary system analysts, in the design phase, put all possible problems in the desktop, participate in discussions with customers (the conditions, characteristics, effects, consequences, etc.), solve, and analyze the analysis and design as little as possible Error Bring the next step development phase. The programmer is not annoying to tell them the importance of program rules. In terms of psychological, we have to use active way to eat "tonic", more than two praises will often bring a good effect, after all, the programmer is a group of young people, it is not "hit" of. It is essential to cultivate their team spirit. In terms of test engineers, we must respect them (many of the status of many domestic companies test engineers), let them realize the importance of their work. It is also necessary to continuously cultivate their patience, sense of responsibility and careful style (in this regard, female test engineers are more advantageous). Seriously listen to their suggestions and understand their psychological feelings. After solving the psychosic symptoms of the above personnel, you will find significant improvements in the development efficiency of the entire project. I personally feel a good software project manager, first of all, I should be an expert in management psychology. People are the foundation of software companies. Understand the psychological activities of participating in the project developers, for project managers, you can leverage poor people, improve the team's cohesiveness and workability, thereby increasing development efficiency.
About the Author
Zhang Hua, Bachelor, System Analyst, Software Engineering Expert Network expert group member. With rich software project development and management experience, skilled use of Playcase, Power Designer, Visio, Smart Draw, etc., project analysis and design. For Java, C , Delphi, VB, compilation and other development languages have many years of development experience, familiar with Japanese software companies development management model. Contact email: charmhard@long.com (End)
