Skip to main content

We are aiming for an incremental return to campus in accordance with guidelines provided by NSW Health and the Australian Government. Until this time, learning activities and assessments will be planned and scheduled for online delivery where possible, and unit-specific details about face-to-face teaching will be provided on Canvas as the opportunities for face-to-face learning become clear.

Unit of study_

COMP9412: Agile Software Development Practices

This unit builds students skills to follow defined processes in software development, in particular, working in small teams in an agile approach. Content covers the underlying concepts and principles of software processes, their analysis, measurement and improvement. Students will practice with a variety of professional-strength tool support for the practices that ensure quality outcomes. The unit requires students to enter already skilled in individual programming; instead this unit focuses on the complexities in a team setting.

Details

Academic unit Computer Science
Unit code COMP9412
Unit name Agile Software Development Practices
Session, year
? 
Semester 2, 2020
Attendance mode Normal day
Location Camperdown/Darlington, Sydney
Credit points 6

Enrolment rules

Prohibitions
? 
SOFT2412
Prerequisites
? 
None
Corequisites
? 
None
Available to study abroad and exchange students

Yes

Teaching staff and contact details

Coordinator Basem Fathi Suleiman, basem.suleiman@sydney.edu.au
Type Description Weight Due Length
Final exam (Open book) Type C final exam hurdle task Exam
Final exam.
50% Formal exam period 2 hours
Outcomes assessed: LO1 LO2 LO3 LO4 LO5 LO6 LO7 LO8
Assignment group assignment Group Project
Integrating agile development tools
15% Week 06 multiple weeks
Outcomes assessed: LO2 LO3 LO4 LO5 LO7
Small continuous assessment Agile development tools
Quiz 1: Agile development tools.
5% Week 06 In-tutorial quiz
Outcomes assessed: LO2 LO3 LO4 LO5 LO6 LO8
Assignment Scrum software development
Software development using Scrum and agile tools
25% Week 11 multiple weeks
Outcomes assessed: LO1 LO7 LO6 LO5 LO4 LO3 LO2
Small continuous assessment Scrum software development
Quiz 2: Scrum software development
5% Week 11 In-tutorial quiz.
Outcomes assessed: LO1 LO2 LO3 LO4 LO5 LO6 LO7
hurdle task = hurdle task ?
group assignment = group assignment ?
Type C final exam = Type C final exam ?
  • Group project (Tools for agile development): group of students will collaboratively work to apply software development tools and use recommended development practices in agile project environment. The project involves using technical agile tools and practices that aid in software development and reporting the outcomes of project and its rationale. 
  • Group Project (Scrum software development): group of students will collaboratively work on a small software development project in agile environment using Scrum approach. The project involves applying Scrum in agile development environment and agile development tools, reporting the outcomes and its rationale. 
  • Quiz 1: individual in-tutorial quiz assessing student’s contribution to agile devlopment tools project and topics covered in weeks 1-5.     
  • Quiz 2: individual in-tutorial quiz assessing student’s contribution to Scrum softare dvelopment project and topics covered in weeks 6-10. 
  • Exam: online exam during exam period. 

*** In order to pass the unit, you must obtain at least 40% on exam, and at least 50% overall!

Detailed information for each assessment will be communicated and udpated during the semester.

Assessment criteria

The University awards common result grades, set out in the Coursework Policy 2014 (Schedule 1).

As a general guide, a high distinction indicates work of an exceptional standard, a distinction a very high standard, a credit a good standard, and a pass an acceptable standard.

Result name

Mark range

Description

High distinction

85 - 100

 

Distinction

75 - 84

 

Credit

65 - 74

 

Pass

50 - 64

 

Fail

0 - 49

When you don’t meet the learning outcomes of the unit to a satisfactory standard.

*** In order to pass the unit, you must obtain at least 40% on exam, and at least 50% overall!

For more information see sydney.edu.au/students/guide-to-grades.

Late submission

In accordance with University policy, these penalties apply when written work is submitted after 11:59pm on the due date:

  • Deduction of 5% of the maximum mark for each calendar day after the due date.
  • After ten calendar days late, a mark of zero will be awarded.

This unit has an exception to the standard University policy or supplementary information has been provided by the unit coordinator. This information is displayed below:

As per the faculty/school policies

Special consideration

If you experience short-term circumstances beyond your control, such as illness, injury or misadventure or if you have essential commitments which impact your preparation or performance in an assessment, you may be eligible for special consideration or special arrangements.

Academic integrity

The Current Student website provides information on academic honesty, academic dishonesty, and the resources available to all students.

The University expects students and staff to act ethically and honestly and will treat all allegations of academic dishonesty or plagiarism seriously.

We use similarity detection software to detect potential instances of plagiarism or other forms of academic dishonesty. If such matches indicate evidence of plagiarism or other forms of dishonesty, your teacher is required to report your work for further investigation.

WK Topic Learning activity Learning outcomes
Week 01 1. Introduction to software development processes; 2. Introduction to Git Lecture and tutorial (4 hr)  
Week 02 Version control: Git team collaboration Lecture and tutorial (4 hr)  
Week 03 Build automation: software build and configuration Lecture and tutorial (4 hr)  
Week 04 Software quality assurance: software testing Lecture and tutorial (3 hr)  
Week 05 1. Continuous integration (CI); 2. Continuous delivery/deployment (CD) Lecture and tutorial (4 hr)  
Week 06 1. Group dynamics: tools and technologies for teamwork; 2. Issue tracking Lecture and tutorial (4 hr)  
Week 07 Agile software development: Scrum method and agile team structure Lecture and tutorial (4 hr)  
Week 08 Scrum method: expressing requirements Lecture and tutorial (4 hr)  
Week 09 Scrum method: planning and estimation Lecture and tutorial (4 hr)  
Week 10 Ethics, intellectual property, copyright, licensing, patents, and open source Lecture and tutorial (4 hr)  
Week 11 1. Reflection: project experiences and lessons learned 2. Industry speakers Lecture and tutorial (4 hr)  
Week 12 Review, Exam Structure Lecture and tutorial (4 hr)  

Study commitment

Typically, there is a minimum expectation of 1.5-2 hours of student effort per week per credit point for units of study offered over a full semester. For a 6 credit point unit, this equates to roughly 120-150 hours of student effort in total.

Learning outcomes are what students know, understand and are able to do on completion of a unit of study. They are aligned with the University’s graduate qualities and are assessed as part of the curriculum.

At the completion of this unit, you should be able to:

  • LO1. demonstrate proficiency in agile and Scrum method in software development
  • LO2. use tools for collaborative processes (version control, issue tracking, collaborative editing of documents, project planning and progress tracking)
  • LO3. identify issues and challenges in estimating project effort, examine the characteristics of software projects that make them a challenge to partition and examine roles and responsibilities in a software team, and management issues of teams
  • LO4. understand good coding practices, including documentation, contracts, regression tests and daily builds
  • LO5. understand various quality assurance techniques, including unit testing, functional testing, and automated analysis tools
  • LO6. demonstrate a basic understanding of legal aspects of software
  • LO7. elicit requirements from a client and specify them
  • LO8. describe the phases of software development and life-cycle of software and compare alternative software process standards and presses (e.g. waterfall, incremental, spiral, prototyping, empirical and agile methods).

Graduate qualities

The graduate qualities are the qualities and skills that all University of Sydney graduates must demonstrate on successful completion of an award course. As a future Sydney graduate, the set of qualities have been designed to equip you for the contemporary world.

GQ1 Depth of disciplinary expertise

Deep disciplinary expertise is the ability to integrate and rigorously apply knowledge, understanding and skills of a recognised discipline defined by scholarly activity, as well as familiarity with evolving practice of the discipline.

GQ2 Critical thinking and problem solving

Critical thinking and problem solving are the questioning of ideas, evidence and assumptions in order to propose and evaluate hypotheses or alternative arguments before formulating a conclusion or a solution to an identified problem.

GQ3 Oral and written communication

Effective communication, in both oral and written form, is the clear exchange of meaning in a manner that is appropriate to audience and context.

GQ4 Information and digital literacy

Information and digital literacy is the ability to locate, interpret, evaluate, manage, adapt, integrate, create and convey information using appropriate resources, tools and strategies.

GQ5 Inventiveness

Generating novel ideas and solutions.

GQ6 Cultural competence

Cultural Competence is the ability to actively, ethically, respectfully, and successfully engage across and between cultures. In the Australian context, this includes and celebrates Aboriginal and Torres Strait Islander cultures, knowledge systems, and a mature understanding of contemporary issues.

GQ7 Interdisciplinary effectiveness

Interdisciplinary effectiveness is the integration and synthesis of multiple viewpoints and practices, working effectively across disciplinary boundaries.

GQ8 Integrated professional, ethical, and personal identity

An integrated professional, ethical and personal identity is understanding the interaction between one’s personal and professional selves in an ethical context.

GQ9 Influence

Engaging others in a process, idea or vision.

Outcome map

Learning outcomes Graduate qualities
GQ1 GQ2 GQ3 GQ4 GQ5 GQ6 GQ7 GQ8 GQ9
Evaluation of individual contributions to group group project Evaluation of student's understanding and ability to explain own and group work in the context of lectures and tutorial materials Online assessments and demos.

Disclaimer

The University reserves the right to amend units of study or no longer offer certain units, including where there are low enrolment numbers.

To help you understand common terms that we use at the University, we offer an online glossary.