9 of software engineering psychology-how does Party B face Party A 2

(This article is synchronously published on javaeye.com. Repeat the source for reprinting)

In http://www.cnblogs.com/jackyrong/archive/2006/11/08/554694.html,

I briefly talked about how to deal with Party A's leadership. This is about how to deal with Party A's information project owner. This is also a very important part.
How to deal with the relationship with Party A's Information Project Leader directly affects the smooth and efficient operation of the subsequent project. Party B deals with Party A most often, that is, Party A's information project owner. For the convenience of discussion, the owner of Party A's Information Project is referred to below as the owner of Party.

First, the general identity and composition of Party A's owner must be summarized. Generally, the common owner of Party A has the following types:
Classification

1) academic. There are many such types of projects as PhD, master's degree or above, academic school, and rich theories, but not many practical projects.
2) skilled. In enterprises, this type usually includes teams with a large number of personnel to complete tasks.
A large enterprise has a large number of development teams, but some of them need to be outsourced. Skilled Party A's leader is hands-on
Type, strong practical experience.
3) Academic + skill. High degree of education, high project ability.
4) general skills. This type of Party A owner has a small number of teams in the enterprise, and needs to be developed at ordinary times,
5) single management type. For this type of enterprise, Party A generally understands some technologies, but not many, but prefers information management,
Many theories.
6) I don't know the type. Many of these types, especially in small and medium-sized enterprises, may have been engaged in maintenance or development,
It may also be the responsibility of the temporary boss.

it is roughly the same as above. Next we will analyze them from a psychological perspective and briefly list some methods for everyone to discuss and reference.
1) Academic Party A's manager. This type of course has a high degree of education and a high theoretical level. Some are even teachers and professors in colleges and universities. Because of their special identities, they think they are very high (ah, they think that their educational qualifications are higher than others), and their self-esteem is quite strong, especially some teachers and professors, maybe it's a cool man in academia. For such people, we must end the project from the beginning to the end, and maintain a respectful attitude towards them and regard them as their own teachers. Of course, what we encounter sometimes may be actually less theoretical and practical experience. In this case, we can still endure it and don't compare it with them. In some cases, we once had the boss of Party B, who was unhappy with some of Party A's people. They thought that they would only blow theory and would not actually do it. Therefore, in some occasions and problems, I want to press the momentum of Party A to make it easier. In fact, this is quite wrong, because many people of this type are indeed mixed in academic circles. They should also know that they are not your party B software company, they may not be as good as you in actual technical projects, but they think that their only advantage is their theory, education, status, and opinions. They often need to be appreciated by others, especially by Party B, in this way,
they are quite comfortable.

Therefore, the following are some of the best things that can be said and done with them in common interactions, such.
A "Haha, Zhang XXX, I have read what you published in xxxx magazineArticle(Thesis) Oh, oh, we really don't get a lot of money. I will give it back.
My team went to study (or a technical question that I had never been able to figure out before. I have read your article and I am very inspired ).

B "Well, Zhang XXX, I heard that your school has a teaching practice base. Our company also has a talent training demand in this aspect. We
Can you communicate and cooperate in this area"
Resolution; if you are not the boss and the boss of Party B, you can also say that you have some relationships with them through some contacts.
If you have no intention to intercept Liu and turn it into Yin, the atmosphere will be very good and it will be very beneficial to Party B's future work.

C. At each meeting, you should listen respectfully to them and do not interrupt them. Even if their views are not correct, do not immediately target them.
You can say it out in a way that is too straightforward. If it is not too urgent, you can even go back and study it clearly. If there is sufficient evidence, email or
Other forms of writing can be expressed in this way, so as to avoid the problem of poor facial expression and their dislike.

D. Remember that if you want to encounter a problem that persists, if you feel that you are justified, your team should fully demonstrate and be sure of it,
Otherwise, if it is true that the people are correct, your mistakes, and a confrontation, people will look down on you more. In case they finally find that they are not feasible or wrong,
After they know it, they generally do not want to talk about it again. You should move the topic as soon as possible, and do not get stuck.

E. Some people may be very academic, self-disciplined, not very polite, and not very fond of PR.
Do not try to go to public relations. Do not think that people of this type like Public Relations very much. Otherwise, it is counterproductive.

D. When Party A's owner encounters such problems, he may cite theories in project documents and PPT documents to make them feel that your project is fully theoretical.

 

2) skilled people.
This type of owner is very technical and has many people. People like this most. It can be called Zhiyin. But pay attention to the following points.

After all, Enterprise A is not a software company. What the company wants is that after the system project is put on the horse, it will produce the fastest benefits. Therefore, the pressure from Party A's leadership is under pressure on such people. They often have their own internal projects and other projects, because some of them need to be outsourced to you. Therefore, first, you should better communicate with them beforehand to find out where their difficulties are. That is to say, for example, whether they are in this project
Why? For example, will party a complain about Party A's handling methods? Will Party A's leadership demands be unclear, and the capital investment is not in place, but it is in a hurry? All these things should be PR at the beginning of the project. Because psychologically, if they are under pressure, their technical background is the easiest way to talk to you. Therefore, public relations should focus on this.

B. Don't underestimate them. Their companies often come from technical experts because their tasks are not urgent. You should be aware of the technical talents before you meet, and be more cautious with your team. In some previous cases, some party B had to deal with Party A's manager for a long time, and finally found that the other party was a technical cool. This was really bad for future work. At the beginning of the project, you need to chat, search, third-party inquiry, and other methods to truthfully talk about the strength of the other party, find out the other party's posts, blogs, and so on. You need to know your opponent well.
If you find that the other party is a cool man, you should praise the other party in multiple ways. In this case, because the other party is a cool person, you can consider discussing with the other party, or even discussing project-related and other technical issues on some issues during the project. Because of their technical skills, if you can make them feel that the discussion is conducive to his level improvement, they often have a good academic atmosphere, and they are psychologically fond of it, because they like to have a friend. Sometimes, even if you know the problem, you need to pretend that you do not know much about it. Instead, let the other party tell you and let the other party attend classes with you,
Let these cool people feel that they are better than you, and they are teachers, so they should be OK.

C. Of course, this type of person is very serious about technology. Therefore, you have to consider dealing with the other person in the matching team, at least to make the other person feel
You have some strength.

D. If you encounter your own mistakes, you must remedy them as soon as possible. Sometimes you can even say to them that we have fixed any bugs, and there is no need to fix them.
Cover up, because if they are honest with them, they think that you are very technical and they like it.

3) Academic + skill. This type is quite cool, with rich theories, strong practical skills, and a high degree of education. Their Solutions combine the above two points for consideration.
Yes.

4. General skills. This type of Party A owner has a small number of teams in the enterprise. at ordinary times, it also requires some development, but it is not very in-depth. Often
They are all tasks to be completed by superiors, and they are rarely exposed to new technologies. For this type of person, consider:

A makes them feel that the project achievements developed by your team can help them to work in the future and relieve their burden.
At the early stage of the project, I thought you were very good and trustworthy.

B: some of them are technical staff who have completed task-based tasks. They do not like new things very much, but they have nothing to do. In this way, you should not show off new technologies in your project. You are always promoting new things of your company team. They only need to complete the task steadily. You need to do more work in project development to reassure them, and use stable technologies and equipment, do not sell things to others as soon as you are or if you want to sell more expensive things. Otherwise, people will be counterproductive. Another type of technical personnel may want to improve their technical capabilities in the enterprise, but suffer from their own capabilities. Therefore, they want to learn more new knowledge and technologies, sometimes, because they want to learn and use technology, they ask you to use it. Haha, if you meet such people, you can sell them crazy and make them feel that they have bought or used your new products and technologies, the level of their owner will also be good.

5) single management type. For this type of enterprise, Party A generally understands some technologies, but not many, but prefers information management. They basically do not involve
Technical level, because there are also grassroots operators below them. For such people, be sure:
A should discuss with him about the design and demand phases. If he cannot grasp the technical skills, he should suggest that the other party should have more technical personnel at the grassroots level.
Contact you. Well, many of these types are solution-oriented, and they may need to do other chores in the enterprise.

B must know more specific information about grassroots technical personnel at the beginning of the project to contact such personnel; otherwise, it will be troublesome to contact him when something happens.
Such people should focus on discussing their business with them, rather than sticking to them with specific technical principles. But these people are also selling new products to them,
New technologies are easy to use, because they are not skilled and have herd mentality. Therefore, we recommend that you,
Find more time to introduce new technologies and new products of your company, and let the other party know that they have bought your technology. The other party will not need to manage the technology in the future,
He can make his leader more comfortable, and the rest will be done by his hand. Because the psychology of such people is to make solutions and avoid getting bored.
Technology, but it is not necessary to contact them. Therefore, you can properly clarify the general principles with them, and there is no need to let them know things that are too meticulous.

 

6. I don't know what the model is. This type is actually the biggest headache and the most troublesome. If they do not engage in technology, they may be representatives of business departments. Handle
Their method is really difficult to express in detail, but I feel that I should at least grasp the following points.

A. They don't engage in technology, so you can give new products and technologies to them, but pay attention to "degree". Don't be counterproductive.
They are fooled by you and use your fancy stuff. As a result, the improvement of the main business process is not satisfactory to them.

B is best suited to business demand analysts to communicate with them, and even mostly work on the site of the other party. Every time you visit them, let them think of you in detail
It is a very serious development team, not to fool them, it does help them improve productivity. Therefore, more teams are required for important meetings.
The importance of people should be symmetric at least, not for a meeting. Only when the leaders of other people arrive Will you send an analyst to make them think that you are a high level.
Important.

C. Before the project starts, he repeatedly stressed the importance of the demand with them. To make them feel that they need to handle the issue internally as much as possible before submitting the request. Otherwise
If you don't think about it, it will lead to multiple rework, and the final loss is to them. It is best to give them more examples of failure. Many times,
It will make them pay attention to it psychologically. Remember it multiple times.

D. When PR personnel talk about their business, they should use informal channels to set up some of their content that they dare not say on formal occasions.
I know what it means.

E. Let them feel that your team's projects are very fast and high-quality. For example, if you use XP for quick release, let them
When they see something very functional, they don't engage in technology, and they like to see it like this, they have a mental illusion that this is probably something to do.
Of course, the detailed requirements and software engineering are not detailed here.