Home > Undergraduate > Professional Computing 3200 > Project > Sprint 3  

Home
Lectures
Project
Timetable
Resources
 
Help3200
Lecture Times
Unit Outline

Definition of Sprint 3

The heart of the deliverables for this Sprint is the final system, which is to be delivered, both as source code and as an installed sytems on the client's platform of choice. The principal difference with the other Sprints is that this Sprint will be asseessed by both the Client, and your Team's Auditor (with the marks being averaged). Note that previous years' requirement for Client and Team retrospectives has been removed.

 Group Submission: Each Team must submit:

  • Any Project documents (as required by the Client) for Sprint 3 need to be submitted to the Client. At the very least, beyond the system itself, the Team should supply an installation guide and a user guide (which can be in the same document).
  • A copy of the GitHub commit logs for the project deposited on your Team's MS Teams directory.
  • Given the size of some projects (due to being components of larger systems), or IP issues, it may not be practical or ethical to submit the code and accompanying documents via your Teams MS-Teams directory. However, in general, it is important that your Team submit the final version of the code via MS-Teams if possible, firstly to act as a timestamp and secondly to act as a backup source, particularly post the end of the semester.

 Individual Submission: 

  • As in Sprint 2, in addition to your participation in the team submission, you must also submit a reflection on your experiences in the unit thus far. To guide you in this task, a form can be found here. Complete the form (MS-Word or PDF only, please) and submit the completed form via LMS.

    Please also remember to log into your SPARK+ account and complete the group assessment survey for this Sprint.


Department of Computer Science & Software Engineering
The University of Western Australia
Last modified: 14 October 2023
Created by: Michael Wise 		UWA