New project Bonus Distribution Scheme

In accordance with the spirit of the company's new bonus distribution system, in our project team, I proposed the following Bonus Distribution Scheme.

Principles

1. Calculate the bonus distribution ratio based on the workload, but the contribution to the project based on the task difficulty. (This is already used in the May bonus distribution plan)

2. The branch of each task is: basic score * Complexity * reconstruction coefficient + (days-1) * 0.3

Basic score: used to reflect the task completion. value range: (0.1-1)

For basic scores, see the following rules:

1. The task has test feedback and the basic score is 0.9,

2. The task test feedback exceeds 3 times, and the base score is 0.7.

3. The task test feedback exceeds 5 times, and the base score is 0.4.

4. The task test feedback exceeds 10 times, and the base score is 0.1.

5. introduce new technologies with a base score of 1

6. Introduce a new idea with a base score of 1

Complexity coefficient is used to reflect the complexity of a task. value range: 0.2-no upper limit)

For details about how to obtain the complexity coefficient, refer to the following rules:

1. General System Improvement Suggestions 0.1

2. Outstanding System Improvement Suggestions 0.5

3. General Document Sorting 0.2

4. business logic document summary 0.5

5. Changes and availabilityAlgorithm/System architecture/Business Process/new module related, but the number of changes is very small: 1

6. changes are related to availability algorithms, system architecture, business processes, and new modules, but the changes are 1.5 larger.

7. changes are related to availability algorithms, system architecture, business processes, and new modules, but the number of changes is greater than 2.

8. introduce new technologies, generally 1

9. introduce new technologies with high technical content, involving more than 1.5 of the underlying framework of the system.

10. Introduce new ideas, generally 1

11. Introduce new ideas and improve system quality, stability, or workflow by more than 1.5.

For, the customer feedback shall prevail.

I will record the scores of 7 and 9 first, and discuss them with you before counting the bonus table at the end of the month.

For the range in 2, 3, 4, we can further discuss and supplement

3. Reconstruction coefficient:CodeCode reconstruction in modifications (1-2)

4. Number of days: the number of days for the task to be completed. The number of days is calculated as one day.

5. Test

Test tasks are not scored, and the first reward for self-testing bugs is canceled. However, for bugs found in test tasks or in self-test, each score is 0.1 points. If the value of a bug is high, the score is 0.2 points;