| Team Score Component | 50 | |
|---|---|---|
| Area | Criteria | Value |
| version control | work products under version control | 2 |
| versioned files w/history | 2 | |
| useful commit comments | 1 | schedule | reasonableness of schedule | 2 |
| how well it was followed | 3 | review | agenda and flow | 4 |
| issue discussions | 4 | |
| issue dispositions | 4 | |
| adherence to protocol | 4 | |
| value/quality of the process | 4 | |
| report | completeness | 2 |
| accuracy | 2 | |
| detailed status of each issue | 2 | |
| summary | 2 | |
| clarity | 2 | |
| postmortem | developing review package | 2 |
| process of reviewing module/test plan | 2 | |
| the review itself | 2 | |
| schedule (reasonableness & tracking) | 2 | |
| pedagogical value of project | 2 | |
| Individual Score Component | 50 | |
|---|---|---|
| Area | Criteria | Value |
| version control | work products under version control | 2 |
| versioned files w/history | 2 | |
| useful commit comments | 1 | |
| review package | Table of Contents | 2 |
| Background | 4 | |
| Design to be reviewed | 4 | |
| Test Plan to be reviewed | 4 | |
| Suggested Study/Review order | 2 | |
| Problems, Issues, Standards | 2 | |
| Overall Package Quality | 2 | review comments | completed well before review | 4 | design review - thoroughness | 4 |
| test plan review - thoroughness | 4 | |
| throughtfullness and clarity | 4 | |
| Organized for discussion | 2 | |
| Overall package quality | 2 | schedule | reasonableness of schedule | 2 |
| how well it was followed | 3 | |
NOTE: