COMP4050 applies an agile method to the engineering of features in a non-trivial software project. Students work as a team on a project. They are able and encouraged to use technology with which they are already familiar or that has a relatively short learning curve. The assessment is focused on the software processes and tools that a team uses, as well as individual contributions to the team effort. The items will be assessed continuously with feedback being provided frequently by the unit convenor to teams as well as to each student. Peer feedback will be used to inform the assessment by the convenor.

The deliverables for the basis of the reflection include group presentation, peer group reviews, personal logs, and a personal reflection. Based on the supplied evidence and the convenor's observations, these assessment items will be assessed according to the following standards:

• Distinction/High Distinction: An extremely valuable team member who makes many key contributions to many different aspects of the software that is developed by the team.
• Credit: A team member who makes useful contributions to multiple aspects of the team's software.
• Pass: A team member who makes a small number of contributions to the team's software or focuses on a single area of contribution. 

The team contribution assessment item captures contributions to the functioning of the team rather than a specific contribution to the development of the software artefact (which is captured by the other three assessment items). E.g., a high team contribution mark might be earned by a student who often comes up with useful suggestions in planning discussions for features proposed by other team members or who volunteers to present some useful technology to the team so everyone can learn about it. Students are encouraged to think of ways in which they would like to contribute but the unit convenor will also suggest opportunities. Students should plan to attend all classes since they are vital meetings of the software team.

Participation will be assessed according to the following standards:

• Distinction/High Distinction: An extremely valuable team member who contributes strongly in many, varied ways to the smooth and efficient functioning of the team.
• Credit: A team member who makes multiple varied contributions to the team's operations, not just in a single particular way.
• Pass: A team member who makes a small number of contributions to the way the team operates or whose contributions have a single focus.

The focus of the unit is on development periods of a few weeks duration - so-called sprints - where milestones such as new features, bug fixes and the like are proposed, planned, delivered and reviewed. Students should not develop code by themselves or in pairs or focus narrowly on one or two aspects. Instead, we expect students to participate in each aspect of the project rather than focus on one or two aspects in isolation. In particular, students will be asked to review each other's code and participate in reviews of each software milestone.

Tools such as distributed version control and milestone planning software will be used throughout to coordinate activities.

Each week there is a three-hour class during which the teams will meet to discuss expectations, plans and progress. Usually, the first hour or so will be devoted to general topics of interest to the whole class, while the second and third hours will be used by teams to work together on their activities. Students are expected to attend all classes since they are vital meetings of the software team.

This year, the course will be delivered on campus, in a face-to-face mode. We expect students to be present on campus for the weekly sessions.