Unit Outline

The capstone project units provides an opportunity for students to consolidate the knowledge and skills they have acquired in their course and apply them to a substantial ICT project. This unit extends the students development of the professional, technical, communication and teamwork skills required by ICT professionals in practice. Students will extend their knowledge and skills in the areas of project management and software development through completing professional project documentation and managing the development of the team project. Students will work together in a team of approximately 6 students and continue to work on the project they started in KIT301.

Intended Learning Outcomes

As per the Assessment and Results Policy 1.3, your results will reflect your achievement against specified learning outcomes.

On completion of this unit, you will be able to:


1	Design and develop a technical system that supports the needs of a client and adheres to professional standards.
2	Apply a user centred approach to system design and development while collaborating and communicating with stakeholders.
3	Convey capacity to self-learn, work as a contributing team member, and adhere to codes of professional conduct throughout the software development process.

Requisites


REQUISITE TYPE	REQUISITES
Pre-requisite	KIT301

Alterations as a result of student feedback

The assessments for both KIT301 and KIT302 have placed greater emphasis on implementation and student engagement. This adjustment aims to address the issue of imbalanced individual contributions, which was a significant concern raised in student feedback in 2022.

Teaching arrangements


ATTENDANCE MODE	TEACHING TYPE	LEARNING ACTIVITY	CONTACT HOURS	FREQUENCY
On Campus	Lecture (Online)	A real-time (i.e. synchronous) interactive activity involving the whole class whose primary purpose is the presentation and structuring of information/ideas/skills to facilitate student learning. All students are expected to attend.	1	Study Period 2 times
On Campus	Tutorial	A structured real-time (i.e. synchronous) activity in a small-group setting where the primary purpose is the clarification, exploration or reinforcement of subject content presented or accessed at another time or place (e.g. lecture, preparatory work). It is reliant on student-teacher and student-student interaction and dialogue for achievement of its learning outcomes. The students enrolled in the tutorial are expected to attend.	0.50	Study Period 4 times
Online	Workshop (On Campus)	A structured real-time (i.e. synchronous) activity that involves a mix of presentation of new information/ideas/skills and guided activities related to that information/ideas/skills. All students are expected to attend.	4	Study Period 1 time

Attendance/Engagement Expectations

It is expected that you will attend all on-campus and onsite learning activities. This is to support your own learning and the development of a learning community within the unit.

If you miss a learning activity for a legitimate reason (e.g., illness, family commitments) teaching staff will attempt to provide alternative activities (e.g., make up readings) where it is possible.

If you are unable to attend regularly, please discuss the situation with your course coordinator and/or our UConnect support team.

How will I be Assessed?

Assessment schedule


ASSESSMENT TASK #	ASSESSMENT TASK NAME	DATE DUE	WEIGHT	LINKS TO INTENDED LEARNING OUTCOMES
ASSESSMENT TASK 1:	Agile Cycle 2 Reports	Week 7	20 %	LO1, LO2, LO3
ASSESSMENT TASK 2:	Agile Cycle 3 Reports	Week 12	30 %	LO1, LO2, LO3
ASSESSMENT TASK 3:	Team Presentation	Week 13	20 %	LO1, LO2
ASSESSMENT TASK 4:	Performance	Refer to Assessment Description	30 %	LO1, LO2, LO3

Assessment details

Assessment Task 1: Agile Cycle 2 Reports

TASK DESCRIPTION:

PART A: AGILE REPORT: Your team will develop a professional-style business report (including all relevant structural elements) that describes your team’s activities and progress towards completing the project described in your Initiation report, specifically as it relates to Agile Cycle 2 in your Planning Report schedule.

PART B: SELF REVIEW
Each member of the team will complete a self-assessment activity template.

PART C: PEER REVIEW
Each member of the team will complete a confidential peer assessment template, including a detailed assessment of the contributions of your teammates to the Agile Report (PART A).

TASK LENGTH:

As appropriate for the student project

DUE DATE:

Week 7

WEIGHT:

20 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Report the progress towards the technical development of the system in regard to system users’ requirements.	LO1
2	Describe and justify the methodology and outcomes to evaluate the system and its compliance with best practice.	LO1
3	Report the methodology and outcomes to elicit client feedback on the system and plans for the next phase of development.	LO2
4	Reflect and report on your own contributions and conduct towards the project and your personal learning strategy	LO2, LO3
5	Provide a detailed and useful review of your peers' contributions to the project, identifying any opportunities for improvement.	LO2

Assessment Task 2: Agile Cycle 3 Reports

TASK DESCRIPTION:

PART A: AGILE REPORT: Your team will develop a professional-style business report (including all relevant structural elements) that describes your team’s activities and progress towards completing the project described in your Initiation report, specifically as it relates to Agile Cycle 2 in your Planning Report schedule.

PART B: MANUALS Your team will produce both a User Manual and a Reference Manual related to your project.

PART C: SELF REVIEW Each member of the team will complete a self-assessment activity template.

PART D: PEER REVIEW Each member of the team will complete a confidential peer assessment template, including a detailed assessment of the contributions of your teammates to the Agile Report (PART A).

TASK LENGTH:

As appropriate for the student project

DUE DATE:

Week 12

WEIGHT:

30 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Report on how the Initiation and Planning requirements and expectations have been achieved by the final software system	LO1
2	Review and assess your peers' contributions and conduct towards the project and identify any opportunities for improvement	LO2
3	Reflect and report on your own contributions and conduct towards the project and your personal learning strategy	LO2, LO3
4	Describe and justify the methodology and outcomes to evaluate the final software system and its compliance with best practice.	LO1
5	Report the methodology and outcomes to elicit client feedback on the system and plans for future development.	LO2

Assessment Task 3: Team Presentation

TASK DESCRIPTION:

Your team will conduct a 20-minute presentation, supported by slides, to ICT staff, students, and project clients, encompassing the process and outcomes of your work across the units KIT301 and KIT302.

TASK LENGTH:

20 minutes

DUE DATE:

Week 13

WEIGHT:

20 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Present the team's process for developing the ICT system.	LO1
2	Describe how the system meets the needs of the client and users and applies best practice.	LO1, LO2

Assessment Task 4: Performance

TASK DESCRIPTION:

Your professionalism during this unit will be determined via a series of measures including demonstrations, client feedback, and participation in unit activities.

TASK LENGTH:

Templates

DUE DATE:

Refer to Assessment Description

WEIGHT:

30 %

CRITERION #

CRITERION

MEASURES INTENDED LEARNING OUTCOME


1	Describe your contributions and your ideas through active participation in scheduled Management Meetings.	LO3
2	Participate actively and make useful contributions in client-oriented activities throughout the project.	LO2
3	Describe your contributions to the development of a technical system through active participation in the scheduled team demonstrations of your system.	LO1, LO2

How your final result is determined

To pass this unit, you need to demonstrate your attainment of each of the Intended Learning Outcomes, achieve a final unit grade of 50% or greater, and pass any hurdle tasks.

Submission of assignments

Where practicable, assignments should be submitted to an assignment submission folder in MYLO. You must submit assignments by the due date or receive a penalty (unless an extension of time has been approved by the Unit Coordinator). Students submitting any assignment in hard copy, or because of a practicum finalisation, must attach a student cover sheet and signed declaration for the submission to be accepted for marking.

Requests for extensions

If you are unable to submit an assessment task by the due date, you should apply for an extension.

A request for an extension should first be discussed with your Unit Coordinator or teaching support team where possible. A request for an extension must be submitted by the assessment due date, except where you can provide evidence it was not possible to do so. Typically, an application for an extension will be supported by documentary evidence: however, where it is not possible for you to provide evidence please contact your Unit Coordinator.

The Unit Coordinator must notify you of the outcome of an extension request within 3 working days of receiving the request.

Late Penalties

Assignments submitted after the deadline will receive a late penalty of 5% of the original available mark for each calendar day (or part day) that the assignment is late. Late submissions will not be accepted more than 10 calendar days after the due date, or after assignments have been returned to other students on a scheduled date, whichever occurs first. Further information on Late Penalties can be found on the Assessments and Results Procedure.

Review of results and appeals

You are entitled to ask for a review of the marking and grading of your assessment task if there is an irregularity in the marking standards or an error in the process for determining the outcome of an assessment. Details on how to request a review of a mark for an assignment are outlined in the Review and Appeal of Academic Decisions Procedure.