Self and Mutual Evaluation

Version: August 29, 2001

The specific results will be kept in strict confidence. Please be frank and complete in your responses. When completed, this form should be handed in hardcopy on the specified due dates.

Please answer each question for each person in your group, including yourself. Except for the "Descriptive and Qualitative Questions" section, each question should be answered with a single sentence for each person indicating their rating. Note that each question indicates the extreme ends of a scale -- you should freely rank students as lying somewhere in between (you can choose how to best express this) as appropriate.

For each person in your group, including yourself:

1. How familiar are you with each team member's contribution?
   [Use a scale from
        VERY familiar / observed directly -- to --
         NO real idea / rarely worked together.]
     
2. Attitude toward team and teammates:
   [Use a scale from
        BEST: enthusiastic, cooperative -- to --
        WORST: negative, uncooperative]
     
3. Attitude toward project and achieving a good result
   [Use a scale from
        BEST: determined to produce an excellent result -- to --
        WORST: only what must be done for the grade]
     
4. Quality of work contributed by each team member:
   [Use a scale from
        BEST: consistently high quality -- to --
        WORST: seldom meets expectations]
     
5. Attendance at meetings:
   [Use a scale from
        BEST: always attends and comes on time -- to --
        WORST: never shows up or too late to be useful]
     
6. Communication during meetings and team discussions:
   [Use a scale from
        BEST: productive, positive communicator -- to --
        NEUTRAL: little or no contribution -- to --
        WORST: mostly a negative effect]
     
7. Communication via email:
   [Use a scale from
        BEST: productive, positive communicator -- to --
        NEUTRAL: little or no contribution -- to --
        WORST: mostly a negative effect]
     
8. Efforts to share work and contribute as "part of the team":
   [Use a scale from
        BEST: Strove to work well with others -- to --
        WORST: Tended to work in isolation]
     
9. Ability to meet deadlines:
   [Use a scale from
        BEST: always met or beat deadlines -- to --
        WORST: never met deadlines]
     
10. How well did each person meet the team's expectations:
    [Use a scale from
         BEST: did everything we expected or more -- to --
         WORST: did nearly nothing of what we expected]
      
11. Suppose you have 100 units of something desireable to distribute across your team in proportion to their overall contribution and effort on this project. How would you distribute it?
    [The sum over all of the team members will be 100%.]
      
12. DESCRIPTIVE and QUALITATIVE comments on each member's part in the team work (including your own!!). For each member, mention:
    
    • what they have done on the project
    • how well they did their job / the quality of their work
    • their attitude toward their work on the team and the end product
    • any strengths, weaknesses, or mitigating factors.
        
13. Additional Comments (if any):

Change Log

• August 28, 2000. Original version (adapted from evaluation authored by Vicki L. Almstrum).

Students have experienced many problems in the past using word processors for creating their documents (e.g. MS Word) and then having these applications generate "html" format. As a result, create your documents directly in "html". Please use the style defaults, and do not include any frames, forms, javascript or other dynamic features (unless you first clear this with me). You should only need to use a few basic tags; the following set should suffice:

title, html, body, head, ol, ul, li, p, br, hr, table, tr, td, a 
(anchor), h1-5 (section level), em, strong, samp, var, dl, dt, dd

Overall guidelines

• Strive for consistency of style across the documents produced by your team.
• Use the section numbering given in the document outlines that you are utilizing when possible.
• Font choice and size should allow for easy readability of the final document. The default font size is generally the best choice for the body of text in a document.
• Tables can be very helpful in organizing information.
• Utilize the "real estate" of your document as effectively as possible. Be judicious in the use of mechanisms such as border frames (whose primary purpose is to add color).
• In general, each document should be self-contained, i.e., not split across several html pages. Images should generally be inline rather than hyperlinked.
• Use only black text against a white background.

Use of HTML tags

• Section and subsection headers should use heading styles to help them stand out.
• Each section, subsection, and sub-subsection heading should have an appropriately named anchor, which will be linked to from the Table of Contents for the document. You can also use these anchors from other documents that refer to these sections.
• Use horizontal rules <hr> to aid the usability of your document.

Opening banner

• Appears in every project document.
• Introduces the document with all identifying information.
• For all documents:
  • The opening banner is the first information to appear
  • The fonts should be of an appropriate size. Use a pleasant mix of the largest headings (<h1>, <h2>, <h3>).
  • It is good to vary font size for the various parts of the opening banner.
  • The following information must appear in the opening banner:
    • Document title
    • Version number/name for this document (date should be used as the default)
    • Date of the document (if not used as version number)
    • Product name
    • Team title
    • A list of the authors (i.e. the team members)

Table of Contents

• Included in every project document.
• Provides an overview of the document.
• Follows immediately after the opening banner.
• For all documents:
  • Include all section and sub-section titles (including the numbering)
  • Use indentation to show the structure of the levels
  • Include anchor links to allow a reader to jump directly to each section

Example Layout

Here is an example index.html from a student project group, modified (by me) to meet updates to my formatting requirements.

Change Log

As documents evolve, the version number changes to reflect these differences. A change log informs the reader of the differences between versions. Documents receive new version numbers each time a different version is turned in or added to the team's web site.

There should be an entry in the change log for every version of the document. This should include:

• the version number
• the date it was issued
• a sentence or two describing the reason for the new version
• the person who made the change

The change log should be located at the end of the entire document. Note that for these documentation standards, the version number is the same as the date of issuance.

Change Log

• November 16, 2001. Changed to create "html" file directly w/list of tags. Also, provided a sample index.html file.
• November 1, 2001. Added sample index.html file.
• October 30, 2001. Added add'l constraint for single name file names and also black text against white background.
• August 29, 2001. Added comments on forward vs. back slash for directory names in hyperlink references.
• April 9, 2001. Added comments on case-sensitivity and handin via softcopy.
• March 1, 2001. Edited version of original.
• Original version by Vicki Almstrum, University of Texas