| project | content |
|---|---|
| Spring 2020 School of Computer Software Engineering (Roger Renjian) | Blog Garden Class Blog |
| Work requirements | Team contribution distribution rules |
| Our goal in this course is | Exercise yourself in teamwork |
| In what specific areas does this assignment help us achieve our goals | Clear assessment rules for team contributions |
Team contribution points distribution method
After everyone's meeting and discussion, we finally reached an agreement: the distribution rule of the team's contribution points is composed of three parts, which are task completion status, status mutual evaluation and daily report. The sum constitutes everyone's team contribution points.
1. Task completion
For each issue published on GitHub, different size values are comprehensively assigned according to the amount of tasks and difficulty, and the value range is 1 ~ 5. The sum of the size of the tasks completed by each team member is the task score for this team member.
-
The size is 5: the task volume is large (it takes 6 ~ 8h)
-
The size is 4: the task volume is large (it takes 5 ~ 6h)
-
The size is 3: the task volume is average (time consuming 3 ~ 5h)
-
The size is 2: the task volume is small (it takes 1 ~ 3h)
-
The size is 1: the task is small (less than 1h)
This item accounts for 40% of the total score
Second, the state mutual assessment
After the end of the Alpha phase, the group conducted a mutual evaluation, and the evaluation content was the state performance of each team member during this period. It includes the following aspects:
- Task completion quality: whether they are actively completing their own tasks, what is the quality of the code, and whether there are situations that hinder the team's progress
- Participation: whether you actively participate in group discussions, daily meetings, and whether you have a sense of team participation and responsibility
- Overall score: Synthesize the feelings of cooperation at the Alpha stage and give an overall evaluation
This item accounts for 40% of the total score
3. Daily report
- If you have a code submission record or comment record on GitHub in one day, you can get a full score of 3 points.
- There is no submission record or comment record on GitHub, but if you participate in the daily regular meeting or participate in the discussion in the group, you can get 2 points.
- Without any participation, you get 0 points.
- Because PM publishes blogs every day and counts the scores of members, the default score is full.
This item accounts for 20% of the total score
Score calculation
Scoring is just a quantitative indicator to measure the performance of team members, the purpose is to inspire everyone to do their own job for the team project, and try their best to make the best results. It is our common goal and pursuit for everyone to work together to get professional skills and teamwork cooperation in cooperation.