Software Engineering I

Team Minutes/Notes

Instructions

Minutes are to be posted in your deliverables website, using the template (.doc) (.html).

Each week you must post your minutes on the web. Failure to post minutes will result in 5 points off the deliverable. All minutes are kept from the beginning of the project until the end of the project.

Good minutes are critical for team members who missed a meeting, and as protection against miscommunications and memory lapses of team members who did attend the meetings. They are also very useful in project management and software process improvement, as trace of the history of the project. By reading back through the minutes one may see a pattern that indicates a problem, or suggests a better way of operating in the future.

Minutes should include a record of every management decision made by the team, including assignments of work or action items to team members. You may also give credit by name to team members who contribute specific ideas, or who are recognized by the team for special accomplishments that week.

Most recent minutes are kept at the top of the file. If there are any problems noted in the minutes, a problem report must be e-mailed to the instructor and team members.

Grading Criteria

  1. Timeliness:
    1. 1 day late 20 points
    2. 2 days late 40 points
    3. 3 days late 80 points
    4. After 3 days late a zero grade is recorded
  2. Correctness (80 points total):
    1. No minutes
    2. Minutes incomplete or incorrect
      1. Missing date
      2. Missing purpose
    3. Minutes not authorized by all team members
  3. Format (20 points total):
    1. Not written in required table format as provided
    2. Misspelled words - 0.5 point for each occurrence
    3. Not in correct order
Adapted by T.P. Baker from original by Dr. Sara Stoecklin. ($Revision: 1.1 $ by $Author: baker $ on $Date: 2010/08/22 15:45:52 $)