Assessment of agile teams

Below are some mistakes I have seen in performing agile team assessments

1. People who read some agile materials think that the levels of all people in the agile team should be the same.

 

What is agile most important? I think everyone will have no doubt that the answer is "person". It's good. It's just a person.

First of all, there is a difference between people. The Chinese people like to divide people into three categories: People, people, and below. This shows that there are differences between people.

This difference reflects many aspects, such as work experience, understanding of problems, and problem solving capabilities. Setting everyone's level as the same will definitely lead to a big pot of food, that is, the better people are getting worse and worse, and the worse people are getting worse and worse. This Chinese person should be the most experienced.

Second, setting everyone's level to the same, it is difficult to distinguish personal expertise, so there is no targeted project, it is difficult to put the right people into the right project. Whether the responsibility is greater than the capability, or the capability is greater than the responsibility.

2. Evaluate the work results of each person

This is a fatal mistake, because it is especially not applicable to Chinese teams. You should evaluate me. Well, what you can see is that I did very well. If you don't think of it, I don't care, there is not a saying: "I can't think of it, I can't do it! I know what to assess.

 

So how can we solve the above problems?

In the first case, we must acknowledge that each person's level is different. How can we determine this level? There are reviewers, that is, the "interviewers" who enter the team, based on experience and ability. Some may worry about the inaccuracy of this level. In fact, this worry is redundant, because agile teams must trust people first. The entry into the group may not correspond to the level in the future. This problem should be attributed to the question of assessment.

So how can an agile team assess it?

First of all, the agile team does not assess individuals. If you have already talked about this issue, you cannot say that you do not assess the team. If you do not assess the team, the agile team should assess the entire team, assess the completion status of the entire team based on the goal.

Secondly, because the team is composed of individuals and is related to the individual, we have given different levels to each team, first, we believe that everyone in the team can achieve their own capabilities. At the same time, we also believe that every member of the team is proactive. But believe it, but what if someone doesn't take the initiative? Isn't someone capable enough? What is the solution? Here is an example: for example, if we get in the queue, but some people do not queue at this time, what should we do for others? For example, if someone has already got on the bus, but he is not doing anything in the car. I think first, someone must come up and say that they must be in the queue, and everyone else accepts this idea. Second, let's squeeze this person out.

Therefore, the agile team's assessment is to assess the entire team and realize that the assessment must be carried out during the project process, because it is a little late after the project is over. The most important thing is to train a team with a "squeeze out" culture. If you want to queue up with a single person, other people will not say anything, and it will often not work.