Home > Undergraduate > Professional Computing 3200 > Project > Project Auditors Marking Guide  

 

Project Auditors: A marking guide

Assessing Teamwork and Leadership is a classic "I can't describe it, but I know it when I see it" scenario. However, these questions/ideas that you can ask yourself when watching team discussions will help frame your assessment of the students, and provide justification for their marks.

Teamwork

  • Time management (punctuality, meeting does not go too long/too short)
  • Students are active listeners (as opposed to passive)
    • Students pay attention to speakers rather than working on code/emails/social media
  • Respectful and professional etiquette is used throughout the meeting
    • Name calling, shaming and other bullying is not tolerated
  • The meeting should 'flow':
    • Being sidetracked on one topic too long etc. reflects poor time management etc.
    • Contributions should be on topic

Leadership

  • Active vs passive listening
  • Does the team leader direct discussion (without micromanaging it)?
    • Is the leader able to get the discussion back on track if conversation is sidetracked?
  • Does the leader motivate the team, or are they overtly negative/patronising/sabotage specific individuals ideas?
  • Are they assertive/do they make decisions when necessary, or do they vacillate/attempt to please all parties?
  • Do they lead without asserting authority?
    • "Leader" not a "dictator"

Mechanism

At each meeting attended by the Auditor, the Auditor will award each Team member a score in the range -3 to 3, where 0 implies no contribution, 3 implies solid leadership or considerable sensible and useful contributions, while -1 implies did not attend the meeting (unless there was a Special Consideration reason for not attending) and -3 implies disruptive behaviour, bullying, etc. (In the latter case, the Unit Coordinatior would need to be informed.) It is not intended that the mark for Professionalism simply be the sum of the meeting marks, but rather that the meeting scores be used to inform the Professional mark.

Department of Computer Science & Software Engineering
The University of Western Australia
Last modified: 5 June 2019
Modified By: Michael Wise

UWA