How to evaluate the performance of an individual in a software team

This is a very important issue,Yan XinThe teacher also wrote a blog to discuss this problem http://www.cnblogs.com/xinz/archive/2011/05/01/2033927.html

 

First of all, we certainly cannot share the same score as in the big pot era. This will not inspire everyone's enthusiasm. Secondly, it cannot be calculated by PM alone, although PM knows the team's situation best.

What we need is a scientific method. According to this question, our Group members had a heated discussion. The following describes the results of our discussion.

 

We can look at the contribution of a member from three perspectives: mutual score within the team, score of other members and teachers outside the team, and user score and feedback.

 

1. Mutual score within the team

This should account for the largest proportion, because the team is more aware of the contributions of each member.

When the team members work together to complete a project, they will certainly have a lot of contact and understanding. Everyone knows who is doing a lot and who is doing well, therefore, members in the team have the most say.

We think this part of the score should account for 50% of the total score.

2. rating of other students and teachers outside the team

It is also necessary to present our final work to other students and teachers so that they can evaluate the quality of their work.

Many things are the fans of the board, and outsiders need to make a public remark. This method is more objective and credible.

Why other students and teachers? Because they understand technology and software development, they can evaluate it from a professional perspective.

We think this part of the score should account for 20% of the total score.

3. User rating and feedback

Users are always very important. The software we make will eventually be used to benefit users. Therefore, user feedback and evaluation have great value.

For example, if the user reports that book search is difficult to use, the person responsible for book search should assume certain responsibilities.

User feedback and comments are based on the pain points and requirements of users, and are complementary to the second point.

We think this part of the score should account for 30% of the total score.

Of course, each of these three evaluation methods involves many subdivided evaluation points. For example, mutual evaluation within the team can include the number and quality of completed tasks, attitudes and inputs to projects,CodeQuality and maintainability. Of course, we also need to consider the different backgrounds of different students, and the basic differences are quite different. "We know that we have different priorities and specialized skills." We cannot have the same requirements for everyone. Otherwise, problems may also occur.

 

In short, "how to evaluate the performance of an individual in a software team" is a very complicated issue. We are new to software development and are constantly exploring to enhance our understanding. We believe that through team project, we will have a better understanding.