) Software Engineering handouts 3 collaboration (2) Building hamburgers

Http://www.cnblogs.com/xinz/archive/2011/08/22/2148776.html

A good article. For more information, see the original article.

Many students are eager to deal with various people in a large software team to promote project progress, but they often lack the skills and experience of one-to-one cooperation. Have you ever practiced cooperation at from elementary school to high school?

Class? No. I often hear that-please do not speak with your deskmate!

Exam? Which of the following tests can be completed by two people? It seems no.

What we often hear when the two quarrel is-I want to tell the teacher!

During the process of student growth, most of the relationships are between upper and lower-level teachers and students, and between parent and child... The authoritative party generally promotes the progress of the event through "command/guidance + inspection/evaluation. However, in society, many jobs are competing with people, cooperating, bargaining, and providing feedback... Completed. In a word, it means dealing with people! I often hear the following expressions:

I just want to go deep into technology and become a technical expert. I don't want to be in charge of anyone, but I 'd better not be in charge of others.

In an organization, there is inevitably a parent-subordinate relationship, but more often it is that the two sides of the cooperation do not have a clear parent-subordinate relationship, nor do they have clear leadership and obedience roles. This is more common in software projects. In this case, do you want to actively ask others to do things, or do you want others to arrange things passively? If the project progress is not as expected, how do you remind your companions? If there is a dispute between the two, will you say-I want to tell the teacher! I want to tell the leaders !? In team cooperation, equal team members must influence their peers through "influence + feedback.

Influence)

You can try the following methods.

Table 11-2

Method

Example

Logic/sentiment

Push/pull

Annotation

Assertions

(Assertion)

That's it. Listen to me. That's right!

Feelings

Push --

Actively promote peer to do something

Strong feelings apply to companions with full trust. Speech, intonation, and body language can help deliver strong information.

Bridge

(BRIDGE)

Could you tell me your reason ......

Logic

Pull --

Attract the other party and build consensus

Give both parties sufficient conditions for mutual understanding

Persuasion

(Persuasion)

If we do this, based on my analysis, we will have such advantages: a, B, c ......

Logic

Push --

Let the other party think

Organized and based on logical analysis. Even if you cannot persuade them all, the other party may accept some comments.

Attracting

(Attraction)

Do you want to live a comfortable life? Do you want to make a fortune at home? Join our pyramid sales team. In a few months, we will be able to earn tens of thousands of yuan in revenue ......

Feelings

Pull --

Describe the ideal status to attract the other party

Information can be effectively transmitted, but the accuracy of the information must be noted. Exaggerated rendering will reduce your credibility

In the software engineering class, the most popular way for students is "Persuasion". Maybe it is because of science and engineering. In fact, other methods are also very useful. Imagine-in the middle of the night, the dormitory caught fire and everyone was running out. Your roommate was hesitant about the clothes to wear. Which method will you choose? Bridge? Persuasion? Attracting? Or assertion?

Feedback (feedback)

"No one says before, no one says behind it"-post-human ratings are a fine tradition of our people. This can be regarded as a "concise feedback", because these feedback will eventually be filled with vinegar and transferred to my ears.

But have we made one-on-one feedback to our teachers, parents, and classmates? Very few. There are many lovers, but because the hormones are too high in love, the human brain is in a irrational state, so it is not discussed.

Feedback is to tell the other party what you think of him. Shrek said that people are like onions and there are many layers. What level of feedback do you need?

Outermost layer: behavior and consequences

Intermediate Layer: habits and motivations

Innermost layer: nature and basic attributes

For example, the jelly in wangwu village invited the girl in the neighboring village to listen to the concert, and the girl lychee waited right at the entrance of the concert hall. The jelly arrived 5 minutes after the concert began. At this time, lychee can give feedback on three levels of jelly.

Outermost layer: behavior and consequences

Jelly, you are late, so I am in a hurry. We cannot enter the venue now. We can only wait for the first scene to end. We missed the wonderful performances!

// Note: When the feedback is about behaviors and consequences, the behavior can be corrected, the consequences can be compensated, and the other party still has the opportunity to recover the situation.

Intermediate Layer: habits and motivations

Jelly, why did you put my pigeons again? When some of my girlfriends went in, I was hanging out, and you were playing with me on purpose! Shame on me!

// Note: when the attack goes up to habits and motivations, it is difficult for the attacked party to confess and clarify the motives.

Innermost layer: nature and basic attributes

Jelly, you are too selfish, all thinking about yourself and your broken software project! You guys in wangwu village don't have any good stuff! Selfish!

// Note: When an attack reaches the core, the attacked party cannot respond because the target [Wang Wu village man] cannot be changed. Or [Selfish].

No one is perfect and there is room for improvement. In software engineering cooperation, partners also have a lot of opinions to tell their peers that there are both technical and cooperative approaches, and there are also ways for people to live, there may be emotional issues. Let's take the simplest code specification as an example. Assuming that jelly accidentally uses the tab indent style, his companion Xiaofei is uncomfortable, because Xiaofei advocates four spaces. How can Xiao Fei give his opinion?

Outermost layer: behavior and consequences

Jelly, I noticed that you use tab indentation when writing a program. We had to say it was four spaces when we set the team specifications. If you use different styles, you will be reading them later and there will be a lot of inconvenience in modifying the code. at the same time, if such a simple specification cannot be implemented, it will make everyone feel bad and affect other work in the future.

// Note: When the feedback is about behaviors and consequences, the behavior can be corrected, the consequences can be compensated, and the other party still has the opportunity to recover the situation.

Intermediate Layer: habits and motivations

Jelly, how do you indent tab again? The number of times? We had a consensus last time. Why are you still doing this? Are you dissatisfied with the previous resolution? That cannot be hacked!

// Note: when the attack goes up to habits and motivations, it is difficult for the attacked party to confess and clarify the motives.

Innermost layer: nature and basic attributes

Jelly, you are too selfish, all thinking about your own style and convenience, where is your team spirit! How are you selfish students from the mountain software college!

// Note: When an attack goes deep into the core, the attacked party cannot respond because the target [Student of the mountain Software Institute] cannot be changed. Or [Selfish]. We can imagine that the conflict that touched the depths of the soul would have a violent ending.

In addition, when giving feedback to others, what we want to accept most is, of course, the most nutritious [meat]. However, if there is meat, it is hard for others to take or eat. You cannot force others to swallow. We want to learn from the masters who make hamburgers and sandwiches-making feedback into hamburgers:

Let's begin with a piece of bread and lay a solid foundation. For example, we can start with the common vision of both parties and the shared vision of the team, so that the other party can feel in a safe environment.

Put the meat on, then you can fry the constructive comments (constructive feedback), add lettuce, condiments, and so on.

How to prepare this piece of meat is also exquisite:

We often say [Feedback], but when providing feedback, we should not completely indulge in the past, old-year, rotten sesame seeds, give comments to others, and draw conclusions. This will lead to a feeling of [you are not doing well, I hate you.

We can adjust [Feedback] to [feedforward], emphasizing that [you did not do enough in the past, but we can do better in the future]

In the technical team, our feedback should focus on the [behavior and consequence] layer, and do not rush to [habits and motivations], [essence]. unless the situation is very serious, it is necessary to touch the depth of others' hearts and let others fight.

Then a piece of bread is covered. At this time, we can echo the beginning and encourage the other party to do a good job.

Well, a nutritious and delicious hamburger is ready: