Each team is given wide latitude in how to structure and manage their team project.  However, the following constraints are required of all teams.  If you want to modify any of them you must obtain the instructor's approval.  

Required deliverables:

Each team member must adopt one of the roles specified in Job Descriptions.

The team maintains all project documents on a team website hosted on the team unix account.  Only the webmaster is allowed to use this account; other team members are allocated individual unix accounts.

The team must locate a person not enrolled in the class (preferably a non-computer major) who is willing to play the role of customer for the product being developed.  The customer's obligations will be defined in class.

The team must perform at least one and preferably two formal reviews or structured walkthroughs.

The team will hold a weekly progress meeting with the instructor during lab time.

The team product must meet the nonfunctional requirements developed during class.

Every student must keep a Time Log.  Submitted every week (Suggested Due: Monday 8:00 a.m.). Submitted to quality assurance (see productivity metrics, below) and to the team manager. (Electronic submission is fine).  The manager uses this data to update the Project Visibility on the team home page.

Suggested Reports

Individual Status Reports

• The status report is where each person documents their accomplishments for the week.
  
• Follow the Status Report Template.
• Alternatively, formal weekly status reporting may be replaced with informal daily reporting via a team bulletin board.
  

• Produced weekly, by project manager, submitted electronically to instructor by 5pm on Monday.
• Follow the Progress Report Template.
• In a separate message, forward all the individual status reports (including your own).
• Alternatively, written progress reports may be dispensed with if weekly team progress meetings seem adequate.
  

• The purpose of the journal is to document the process the team went through in creating their product. It is a record of all team activities. It can be maintained by the manager or by a designated recorder.
• The journal contains the complete minutes from every status meeting (see format above).  Be sure to record all action items assigned and their priority.
• The journal is also the place to document significant management and technical decisions made during the meeting.
• Use a bound "composition book" for the journal.  You can purchase one at the bookstore, they have a black and white speckled cover and a black binding.  Do not use a three ring binder or spiral binder.