本博客详细记录了五个不同团队在指定时间段内的项目质量和完成频率，通过量化评分来对比各团队的表现，未考虑结对编程日志和项目评价的影响。分析结果显示，团队3在整体表现上领先。
| 5.27-6.6 Frequency | 5.27-6.6 Quality | 6.7-6.13 Frequency | 6.7-6.13 Quality | 6.14-6.20 Frequency | 6.14-6.20 Quality | 6.21-6.26 Frequency | 6.21-6.26 Quality | Sum | Score | |
| Team1 | 10 | 8 | 4 | 6 | 0 | 0 | 5 | 9 | 42 | 8 |
| Team2 | 5 | 5 | 3 | 1 | 3 | 9 | 4 | 6 | 36 | 4 |
| Team3 | 10 | 15 | 10 | 9 | 2 | 6 | 5 | 8 | 65 | 9 |
| Team4 | 5 | 6 | 3 | 5 | 2 | 9 | 4 | 8 | 42 | 8 |
| Team5 | 10 | 8 | 10 | 15 | 10 | 15 | 10 | 15 | 93 | 15 |
| Team6 | 10 | 9 | 10 | 8 | 0 | 0 | 2 | 2 | 41 | 6 |
| Team7 | 0 | 0 | 3 | 3 | 2 | 6 | 4 | 6 | 24 | 3 |
| Team8 | 3 | 2 | 5 | 8 | 0 | 0 | 3 | 2 | 23 | 2 |
| Team9 | 4 | 3 | 3 | 3 | 0 | 0 | 4 | 4 | 21 | 1 |
| Team10 | 5 | 5 | 4 | 5 | 3 | 9 | 4 | 4 | 39 | 5 |
说明：1.评分标准和上次一样。
2.项目评价和结对编程的日志不计入此次检查成绩。
扫一扫
277
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
