Week 9 [Mon, Oct 14th] - Admin

  1. Submit weekly quiz before the next lecture
  2. Submit midterm peer evaluations on TEAMMATES Fri, Oct 18th 2359

1 Submit weekly quiz before the next lecture

  • Weekly quiz: Read weekly topics allocated for this week and submit the weekly quiz before the quiz deadline.

2 Submit midterm peer evaluations on TEAMMATES Fri, Oct 18th 2359

  • Midterm Peer Evaluation will open on TEAMMATES. You will receive the submission link by Sat, Oct 5th 10:00.
    If you did not receive the submission link, you can get TEAMMATES to resend the link by going to TEAMMATES link recovery page and entering your NUSNET email address (try the e______@u.nus.edu before trying the 'friendly' email address). Remember to check your spam folder as well.

Admin Peer Evaluations → Session: Midterm Peer Evaluation

Session: Midterm Peer Evaluation

  • Held about two weeks into the tP coding phase
Important questions included in the evaluation:

Some of these questions (e.g., contribution to DG) are omitted from the midterm peer evaluation but are in the final peer evaluation (they are given here for your reference)

Q The team members' contribution to the User Guide is,

Uses the Equal Share +/- N% scale for the answer

Q The team members' contribution to the Developer Guide is,

Uses the Equal Share +/- N% scale for the answer

Q The team members' contribution to the team-based tasks is,

Uses the Equal Share +/- N% scale for the answer

Q The team members' contribution to the product implementation (excluding UG, DG, and team-based tasks) is,

Uses the Equal Share +/- N% scale for the answer

Q The team members' conduct in the project and during tutorials,

  • Evaluated based on the following criteria, on a scale Poor/Below Average/Average/Good/Excellent:

Peer Evaluation Criteria: Professional Conduct

  • Professional Communication :
    • Communicates sufficiently and professionally. e.g. Does not use offensive language or excessive slang in project communications.
    • Responds to communication from team members in a timely manner (e.g. within 24 hours).
  • Punctuality: Does not cause others to waste time or slow down project progress by frequent tardiness.
  • Dependability: Promises what can be done, and delivers what was promised.
  • Effort: Puts in sufficient effort to, and tries their best to keep up with the course/project pace. Seeks help from others when necessary.
  • Quality: Does not deliver work products that seem to be below the student's competence level i.e. tries their best to make the work product as high quality as possible within her competency level.
  • Meticulousness:
    • Rarely overlooks submission requirements.
    • Rarely misses compulsory course activities such as pre-course survey.
  • Teamwork: How willing are you to act as part of a team, contribute to team-level tasks, adhere to team decisions, etc. Honors all collectively agreed-upon commitments e.g., weekly project meetings.

Q The competency of the team member demonstrated in the project and during the tutorials,

  • Considered only for bonus marks, A+ grades, and tutor recruitment
  • Evaluated based on the following criteria, on a scale Poor/Below Average/Average/Good/Excellent:

Peer Evaluation Criteria: Competency

  • Technical Competency: Able to gain competency in all the required tools and techniques.
  • Mentoring skills: Helps others when possible. Able to mentor others well.
  • Communication skills: Able to communicate (written and spoken) well. Takes initiative in discussions.

Q [Optional] Any ANONYMOUS feedback you want to give the classmates you reviewed above?

Q [Optional] Any CONFIDENTIAL comments about any team members?