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

 

Professionalism rubric

Evaluating Professionalism in a team setting is complex, but encompasses values (see linked article) such as integrity and tranparency, and how you act. As such, it is intrinsically difficult to evaluate levels of Professionalism via a rubric. Here are some things to be considered.

Teamwork

  • Time management (punctuality, meeting is not go too long/too short)
  • Being an active listener (as opposed to passive)
    • Paying attention to speakers rather than working on code/emails/social media.
    • Camera on during online meetings
  • Respectful and professional etiquette used throughout the meeting, versus name calling, shaming and other bullying, which is not tolerated
  • The meeting should 'flow':
    • It is good idea to have an agenda
    • Being sidetracked on one topic too long etc. reflects poor time management etc.
    • Contributions should be on topic
  • Treating everyone fairly, and acting honestly and transparently.

Leadership and Followership

  • Does the team leader direct discussion (without micromanaging it)?
  • Do team members contribute actively and productively?
  • Is the leader able to get the discussion back on track if the conversation has sidetracked?
  • Do Team members mentor other Team members? (This is not the same as doing their work.)
  • Do Team members, especially the Team Manager, ensure that voices are heard, and decisions are made.

Marking Rubric

0 ≤ N < 1
Largely did not engage with the Project and the Team by responding to emails, participating in Team meetings, etc.
1 < N < 3
More than one of:
  • Missed meetings without apology, or more than one or two meetings with apology (excepting Special Consideration), or attended online, but with camera off, or repeatedly came late or left early
  • Egregious padding of Booked Hours
  • Failed to complete assigned tasks, but also failed to inform Team/Team Manager in good time
  • Took on Team Manager roll, but failed to properly prepare for, and lead, Team meetings.
3 ≤ N < 5
One of:
  • Missed meetings without apology, or more than one or two meetings with apology (excepting Special Consideration), or attended online, but with camera off, or repeatedly came late or left early
  • Egregious padding of Booked Hours
  • Failed to complete assigned tasks, but also failed to inform Team/Team Manager in good time.
  • Took on Team Manager roll, but failed to properly prepare for, and lead, Team meetings.
5
Attended all meetings (with camera on, if online), but did not contribute anything unless specifically asked. However, was able to respond meaningfully. At most one of the weekly deliverables were not sent on-time to the current Team Manager.
5 < N ≤ 7
Attended all meetings (with camera on, if online), contributed to discussions, occasionally leading the discussion. Evidence of preparation for meetings. If assigned tasks not completed, has let the Team/Team Manager know in good time, and sought help. All weekly deliverables were on-time (without having to be chased).
7 < N < 10
Apart from preparing for and contributing significantly to meetings, and generally getting the job done in a professional manner (see above), evidence of mentoring.
10
Outstanding leadership that inspires the Team; outstanding follower - ship, supporting the Team leaders (use this mark sparingly).


Department of Computer Science & Software Engineering
The University of Western Australia
Last modified: 14 December 2022
Modified By: Michael Wise

UWA