Assessments for Professionalism

This deliverable assesses learning outcomes 2: critically analyse requirements and resources for IT projects and 5: perform effectively as part of a multidisciplinary and multicultural team.

An important aspect of iterative development methods is reflection: "At regular intervals, the group reflects on how to become more effective, then tunes and adjusts its behaviour accordingly" [agilemanifesto.org/principles.html]. Each of the main project deliverables for CITS5206 includes a component for professionalism comprising two types of reflection: P1 is a team-based self-assessment and peer grading with timesheets and P2 is an individual professional reflection.

You will likely make mistakes with the team performance contract and time management. Don't worry - this is an expected part of the learning for this unit. There are 3 submissions for professionalism and an important goal is to improve your team work and time management skills during the project.

The project team will grade each member of the team using the rubric your team has agreed for team performance. This rating of each member is to be done through a whole-of-team discussion, which should also include respectful formative feedback. If there are any problems with this, you may wish invite the unit coordinator to attend the team rating meeting. Each team performance rating should cover contributions to the project only during the weeks of each deliverable (i.e. weeks 1-5 for deliverable 1, weeks 6-8 for deliverable 2 and weeks 9-12 for deliverable 3).

This submission must also include a timesheet for the group showing the contributions of each individual during the deliverable. You should be able to generate a suitable report automatically from Clockify and Trello.

Each student should maintain a timesheet that shows the hours worked by yourself on the the project. You may include activities undertaken in the weekly skills workshops, contributing to group meetings, client meetings, time required to learn project background and new skills, as well as time spent writing, reviewing and testing code and documentation. It is recommended that you use a tool such as Clockify integrated with Trello and GitHub to manage your timesheets.

The goal of keeping timesheets is so you can demonstrate and be seen to contribute your fair share for completing the project. Students will not gain extra marks for spending much more than 10 hours per week on the project, but students who spend much less than this will receive a low contribution mark in the Peer Grading rubric. The aim is, therefore, not to record maximimum hours, but rather to make effective use of the limited hours you have to complete this project (around 10 hours per week).

The completed document with the Peer Grading submission and Team Timesheet should signed by every member of the team. Failure to participate in this exercise, or failure to submit a timesheet, will result in a "0" mark for any missing students.

Submission (one per group) Each group should submit their P1 deliverable (completed Peer Grading and Team Timesheet) to cssubmit. Check you use the correct submission area and submit a single PDF document (no other formats please) with your group number and the student number of the person submitting for the group included in the file name, e.g., Deliverable-1-P1-group7-22233301.pdf.

Marking Rubric for Deliverable P1 The Team Rubric developed by your team in Weeks 1 to 3, that you have practised using and agreed with the unit coordinator.

For this submission, each student should write or record a short professional reflection on the group process so far: what went well, what could be improved and how to improve it. See the Resources Page for advice on writing a good professional reflection.

The format of your reflection may be either

• One page written document (apx 500 words) submitted as a PDF document (no other formats please) OR
• Two minute video Speak to video as if you were giving an answer to a job interview panel about your work and learnings from this capstone project submitted in MP4 format (no other formats please)

Submission Each student should submit an individual reflection in cssubmit (Deliverable 1/2/3 Individual Reflection). Your submission file name should include your student number in the file name, e.g., Reflection1-22233301.pdf or Reflection1-22233301.mp4.

Marking Rubric for Deliverable P2 CITS5206-Individual-Reflection-Marking-Rubric.xlsx