Software performance Scoring

I think an effective evaluation method should achieve the following objectives:

1, to the team: let the whole team into a happy and efficient working state

2, to "master": Reward work more work good people

3, to "low hand": from the system to eliminate the phenomenon of skiving

4, to "Middle hand": to provide work seriously but the level to be improved member survival and growth space

Because everyone's level is different, so the grading standard is not quite the same, finally after discussion, our team decided to use the following methods to judge individual performance, mainly divided into the group score and the score outside the group.

1. In-group score (70%)

Within the group, 5 audit points were used to

1) Task completion (20%)

Task completion is judged by the number of tasks completed by a person, as long as all tasks are completed on time, you can get full marks, if not completed, for any reason, can not obtain full marks.

2) Task completion quality (50%)

Task completion quality is a person's task to complete the quality evaluation, some people to deal with, some people strive for excellence, the result is certainly not the same. The same is read database, someone only need 0.1 seconds, some people want 10 seconds, this effect on product quality is self-evident, so this piece in the score occupies the largest proportion.

3) Code specification level (15%)

The level of code specification is used to constrain the readability of each and every one of us to write code, enhancing maintainability. If the naming is not canonical or the entire comment-free, unformatted, this will make the final composition of the person very painful.

4) Working attitude (15%)

Work attitude is very important, it is afraid that the final result is not very good, as long as the attitude has been serious, we all can be seen, this piece is able to get full marks. On the contrary, if the task is completed, but the attitude is very casual, this part will not get full marks.

5) degree of enthusiasm (5%)

The degree of enthusiasm for the additional points, for a team, everyone will make their own contributions to the team of enthusiastic people, we can see, this part is the work of the attitude of the complementary embodiment.

2, group external ratings (30%)

At the end of the project phase, a unified report will be organized within our group to present the work that we have done during this phase of development. We will ask some of our foreign team members or professionals to listen to our report and rate each of us according to what we have shown in our report. This part does not have a unified audit point, but mainly is the quality of the assessment work and individual evaluation of their work.

The above is the evaluation scheme adopted by our group, we hope that we can make better suggestions.

Software performance Scoring