Home > Undergraduate > Professional Computing 3200 > Project   


Project Home Page


Project Deliverables (Team related assessment)

Deliverable Description Marking
Sprint 1 (5%)
Sprint 2 (10%)
Sprint 3 (15%)

Individual Project Related Assessment

An mentioned in the introduction on the home page for the unit, in accordance with the University policy on assessment, group-based marks can account for a maximum of 30% of the final mark. In the case of CITS3200, this means the outputs of the three Sprints. (University policy also stipulates that all team members must be awarded the same mark.)

For the 50% of the final mark related to the project (i.e. excluding an individual Professional Development Portfolio):

  • Sprint Reflections (15%)
    Fifteen percent of the final mark is made up of structured reflections for the 3 Sprints, i.e. 5% each. Each Sprint has its own reflection document, linked to the Sprint page above.
  • Professionalism (10%)
    There will be mark for Professionalism, as judged by the Project Auditor and Unit Coordinator based on observations across the project timeline, but particularly on team meetings that the auditor will attend. Professionalism has many aspects, making it hard to set out a check list, but includes punctuality for meetings and level of preparation evident. Has the team member thought through the tasks in hand and come with good questions, and contributed constructively to Team meetings and other interactions. If you were a Team Leader for a period, the assessment will include a judgement about the quality of of leadership shown; otherwise, your qualities as a team member. See also the guidelines used by project team Auditors. Any late submissions of weekly deliverables will detract from this mark, as will missing Team meetings (unless due to illness or other circumstances where Special Consideration would be applicable). It is expected that will have had at least two roles in the Team, so if you had just one, the maximum mark will be 8.
  • Contribution (10%)
    There is a mark, worth 10% of the overall assessment, for contribution. That is, the mark reflects the total effort you have put into the project, as recorded in the Booked Hours and supported by submissions to GitHub. The mark will simply be the number of hours divided by 10 (rounded to 1 decimal place). More ambitious projects will therefore, in general, result in higher marks for this component as the projects require more work, but please realise that the couple of extra marks are not worth jeopardizing your other units.
    The total Booked Hours should include formal team meetings (i.e. minuted meetings), and may include time required to pick up new skills or learn about the project background. However, the time for learning new skills or gaining background knowledge will be limited to no more than 20% of the total hours that have been claimed.
  • Peer Assessment (15%)
    Contribution will also be peer-assessed at the end of each Sprint by members of your team using SPARKPLUS. Each assessment is worth 5% of the final mark (so 15% in total). Details of how to get started with SPARKPLUS, and how to use it at the end of each Sprint, can be found here.

Weekly Deliverables

In many industries is it standard that teams have minuted meetings on a regular basis, and that time working on particular projects is charged to project clients. We wil be doing somethign similar in this unit. Specifically, it is expected that:
  • Teams will have at least one formal meeting per week, i.e. those meetings will be documented via minutes. (Of course, this does not preclude many informal interactions.) Certain of the Team meetings, on weeks, denoted by a green ball on the timetable, will also include the Team Auditor.
  • There will be 4 additional Team meetings, in weeks indicated on the timetable, with Team Mentors from industry.
  • Team members will each record the time they personally spend on project activities, including Team meetings including Mentor meetings
  • While there is generally considerable flexibility about when meetings are organised, all Team meetings are compulsory, particularly those involving project Mentors or Auditors.
  • As denoted on the timetable, Teams are expected to provide each week, on Friday (but certainly no later than Sunday evening), the following documents:
    • A set of Minutes for each Team meeting held that week (PDF or MS-Word doc),
    • A time-sheet summarising the work that has gone on that week (Spreadsheet) based on Booked_hours spreadsheets from Team members, and
    • A tar or zip file containing the Booked_hours spreadsheet submitted by EACH Team member.
    (Minutes, TimeSheets and the Booked Hours will be discussed in the Introduction lecture. Also see note on the Project Timetable page. The Project page has templates for the Timesheets, Minutes and Booked Hours.)

    The three items are to be emailed to the Project Auditors directly and deposited in the directory allocated for the Team in the Microsoft Teams space for this unit. Please observe the file naming convention mentioned on the Project page.

  • Finally, while School and University policy governs the major deliverables (and in particular late penalties), the following will apply to the weekly deliverables.
    • If a group's Minutes (both weekly meetings and Mentor meetings), Booked-hours spreadsheets file or Timesheets are later than Sunday evening, the Professionalism mark for the responsible Team Manager will be penalised.
    • By the same token, it is not up to the Team Manager to chase Booked Hours spreadsheets from Team members, so if these are late, then the Team Manager is within his/her rights to submit that week's data without the missing person's hours, and that person's Professionalism mark will be penalised.
    • The weeks when there will be meetings with mentors are known well in advance. Therefore, there is no excuse other than illness or misadventure, or the unavailability of the mentor, for you not to attend a mentor meeting, so there will be penalty against the Professionalism mark for each Mentor meeting missed.

Department of Computer Science & Software Engineering
The University of Western Australia
Last modified: 3 August 2020
Modified By: Michael J Wise