Note: This unit is an archived version! See Overview tab for delivered versions.
SOFT2412: Agile Software Development Practices (2018 - Semester 2)
| Unit: | SOFT2412: Agile Software Development Practices (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Intermediate |
| Faculty/School: | School of Computer Science |
| Unit Coordinator/s: |
Dr. Suleiman, Basem
|
| Session options: | Semester 2 |
| Versions for this Unit: |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | INFO1113 OR INFO1103 OR INFO1105 OR INFO1905. |
| Prohibitions: | COMP9412. |
| Brief Handbook Description: | 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. |
| Assumed Knowledge: | None. |
| Lecturer/s: |
Dr. Suleiman, Basem
|
||||||||||||||||||||
| Timetable: | SOFT2412 Timetable | ||||||||||||||||||||
| Time Commitment: |
|
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
| Attribute Development Method | Attribute Developed |
| Able to use typical tools of a professional software developer, including version control, issue tracking, debugger, automated test framework, automated deployment framework. | Engineering/IT Specialisation (Level 2) |
| Able to produce conceptual models of overall systems, based on interactions with stakeholders | Information Seeking (Level 2) |
| Working in project teams with clearly differentiated roles and responsibilities. Awareness of planning issues and methods. Ability to work with project planning methods and documents. Ability to work in teams with people from different professions, and different cultural backgrounds; Able to work with stakeholders to extract requirements and document them. | Communication (Level 3) |
| Develop or acquire software (information) systems that satisfy the requirements of users and customers | Professional Conduct (Level 3) |
| Able to follow an agile process for software development, adjusting to changed requirements; Working in a small team through multiple time-boxed iterations; Understanding of all phases of the lifecycle of an information: requirement analysis (systems analysis) and specification, design, construction, testing, and operation and maintenance;Knowledge of methodologies and processes for developing systems; Able to design thorough test plans for software, or individual components . | Project and Team Skills (Level 3) |
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table 2018.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.
Project and Team Skills (Level 3)| Assessment Methods: |
|
||||||||||||||||||||||||
| Assessment Description: |
Project work involves small (4 student) group working in Scrum approach on software project. Group members will be rotated regularly. Online quizzes will cover the lecture/tutorial of the previous week |
| Recommended Reference/s: |
Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
|
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
| Week | Description |
| Week 1 | Introduction and Overview; SDLC methods; Agile vs planning-heavy |
| Week 2 | Version Control: Git Basics |
| Week 3 | Version Control: Git Team Collaboration |
| Week 4 | Project Automation; Software Configuration, Deployment Process |
| Week 5 | Continous Integration (CI) |
| Week 6 | Software Quality Assurance; Software Testing |
| Week 7 | Group Dynamics; Tools and Technologies for Teamwork: Planning and Issue Tracking |
| Week 8 | Scrum Method; Expressing Requirements |
| Week 9 | Scrum Method; Team Structures |
| Week 10 | Scrum Method; Estimation and Planning |
| Week 11 | Ethics, Intellectual Property, Copyright, Patents, Licensing, and Open Source Software |
| Week 12 | Project Reflection (Lessons learned and discussion of experiences from the Scrum projects) |
| Week 13 | Review |
| Exam Period | Assessment Due: Exam |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
| Attribute | Practiced | Assessed |
| Project and Team Skills (Level 3) | Yes | 42% |
| Professional Conduct (Level 3) | Yes | 39% |
| Communication (Level 3) | Yes | 6% |
| Information Seeking (Level 2) | Yes | 0% |
| Engineering/IT Specialisation (Level 2) | Yes | 13% |
These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.
