| Type | Basis | Description | Value |
|---|---|---|---|
| team | work product | Index of Work Products | 1 |
| team | work product | Review Report | 10 | team | work product | Response to Raised Issues | 15 |
| team | work product | Updated Design | 5 |
| team | work product | Updated Test Plan | 5 |
| team | work product | Post Mortem Analysis | 8 |
| team | methodology | Use of Version Control | 1 |
| team | work product | Plan for phase activities | 2 |
| team | methodology | Planning and Management | 2 |
| individual | work product | Prepared Review Notes | 10 |
For this project you will:
NOTE: all members of each team must prepare, and check in,
notes on the module to be reviewed.
The team that designed that product will be present to
observe and to answer questions, but will have no other
formal role in the process.
WARNING
Each phase of this project will receive a team grade.
Individual grades (for contribution, quality, and schedule management)
will be based on the combined deliverables for all of the phases.
This project requires the same general project index, plans,
subversion use, and post-mortems that are part of every project
in this class.
An overall project plan will have been created in the first
phase, but (if it has not yet already been prepared) you will
also need to prepare a detailed plan for how the sub-tasks of
this phase will be done, by whom, and on what dates.
The team will be graded, as a whole, on its ability to
Individuals will be graded on the extent to which they
were able to perform their work according to (a) the
original plan or (b) the plan of record.
The project specific grade-ables for this project are:
The review meeting is not a place where reviewers will
study a proposal. Rather it is a meeting where reviewers
will discuss issues they have discovered in their
(already completed) study of that proposal.
Each member of the team (including the facilitator and
scribe) will completely review the submitted project
package, prepare, and check-in to svn, detailed comments.
These will be graded on:
The meeting scribe will write up a formal report of your
review session. This report is, most specifically, not a
set of meeting minutes. Rather, it is a distillation of
key issues and decisions. It will be graded on:
This is a final report and should be carefully written, and
well distilled.
This is a summary of the issues to which you had to respond,
and the manner in which you responded to each. The details
of the responses will be found in the updated specification
and design documents. This document is an overview
of the response, that should enable a reader (who is familiar)
with the project to understand (in general terms) how each
issue has been responded to, and should direct them to
the portions of the updated and specs and designs
where the details can be found.
This overview will be graded on
After you have figured out how to respond to the issues raised
in the review, there may be changes to some of the component
specifications or designs. If there are, you wil be graded on:
After you have figured out how to respond to the issues raised
in the review, there may be changes to some of the component
Test Plans. If there are, you wil be graded on:
Reflect and review the way you organized and conducted the
design effort:
The standard guidelines for work product formats apply.
3. Assignment
There are critical interdependencies
between the team whose product is being reviewed and
the team that is conducting the review.
You cannot use late days to defer deliverables owed to
another team:
You must make all of these deliveries on time. Missing
any of these deliveries may result in your receiving a
ZERO for a large portion of this project.
4. Grading
4.1 General Criteria
We will determine when work was done by looking
at the dates of the final subversion check-ins.
Monitoring plans should be included in your
project plan. Problems that come up should be
discussed in your post-mortem.
Detected problems and responses should be discussed
in your post-mortem, and reflected in revisions to
the plan.
4.2 Project Specific Grade-ables
4.3 Work Product Formats