-
Team Leader
- The team leader
- prepares agendas for team meetings
- acts as moderator during team meetings
- insures that meetings stay on track and on time
- determines
assignments for individual team members necessary to
complete the project
The agenda will be a list of topics to be covered and a
time limit assigned to each topic. The meeting should be
conducted in a "time box" manner: Do whatever can be done
on a particular item within its allocated time. What cannot
be done and remains necessary becomes an item for the next
meeting and/or a between meeting assignment for a team member or
subteam.
Assignments should be mutually agreeable among all members
of the team, but the team leader makes the final determination
when the team lacks consensus.
-
Team Recorder
- The team recorder prepares summaries of each team meeting
in the form of annotated agendas.
An
annotated agenda
is an outline of what transpired at a meeting in which the
items on the meeting agenda are the main headings. A summary
of the relevant decisions and the team's reasons for the
decisions appears under each heading. In addition to the
agenda headings, the meeting summary will contain one
additional heading, "Action Items", which are questions
to be resolved between meetings, each of which is associated
with a team member responsible for the item.
-
Team Librarian
- The team librarian
- collects the necessary program components
- prepares listings of program components
- prepares a
session transcript for the project
Program components are modules defined, files created,
and the like that team members developed to complete
project requirements.
Files created by other team members
and stored under their userIDs will be
accessible to the librarian because of the way
the team members have set the file access permissions.
(See
Group Access to Files.)
-
Team Collector
- The team collector collects session transcript and program
component listings from the team librarian and the meeting
summaries from the team recorder, packages them
appropriately, and submits the resulting package
to the instructor.
-
Team Members
- All team members participate in solving the software
development problems that arise in the course of
completing projects. The team should strive to
arrange individual assignments so that all contribute
both to the intellectual effort required and to
other necessary activities, such as
document preparation,
preparation of data for testing individual functions,
and the use of such data sets for software testing.
-
Peer Evaluations
- Each team member will award a total of 100 points to
fellow team members. For example, in a five-member
team, member A could award 25 points to member B,
25 to member C, 25 to D, and 25 to E, or member A
might award 10 to B, 40 to C, 30 to D, and 20 to E.
The only restrictions are that the points awarded
must be non-negative, integral numbers {0, 1, 2, ...}
and the points awarded to fellow team members
by a particular member must total exactly 100. Do not
award points to yourself.
Peer evaluations must be submitted by email to the
instructor within 24 hours after the project submission
deadline. A team member who fails to submit peer
evaluations will be docked 25% on the project grade
and the other team members will receive ratings as if
the team member in default had awarded each of them
the same number of points.
The email message must list the team members in
alphabetical order by last name, one name per line,
with the numeric evaluation written to the right
of the name of the team member it applies to.
Peer evaluation messages in other formats will
be treated as missing evaluations.