Software Engineering › Key terms › Y12 SE Project › Agile approach
Agile approach
Term Key terms bank Y12 SE Project
Also listed as: Agile
Definition
An iterative approach that builds the software in short cycles (sprints), delivering working versions often and adapting to feedback; method tailoring is allowed. Suits changing requirements and small to medium projects.
Example: Release a working feature every two weeks.
Found in: past SDD papers.
Iterative approach with short sprints and continuous feedback.
Where it is used in the test
Syllabus area: Y12 SE Project.
Question types it can appear in
- Multiple choice: 2025 Q2 dropdown
- Short answer: Define, outline or explain it and tie it to the scenario.
- Extended response: Use it as a supporting point linked to the stimulus.
Where it has appeared in the paper
The Software Engineering Project (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q2 (1 mark): Software development approaches The Software Engineering Project (Part A) · 1 mark
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Other questions that mention it
- 2021 Software Design and Development Q25 Secure Software Architecture (Part D) · 11 marks · old syllabus
- 2022 Software Design and Development Q25 The Software Engineering Project (Part D) · 11 marks · old syllabus
Study links
- Flashcard: Agile approach in The Software Engineering Project (Year 12) · study that set
- Memorise: Waterfall
- Key terms bank entry: Agile
- Master answer: sdd2021-q25 (11 marks, extended) (Master model answers: Secure Software Architecture)
- Master answer: sdd2022-q25 (11 marks, extended) (Master model answers: The Software Engineering Project (written answers))
How to use it in an answer
A model sentence
“An iterative approach that builds the software in short cycles (sprints), delivering working versions often and adapting to feedback; method tailoring is allowed.” Then apply it: Release a working feature every two weeks.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Identify: Recognise and name. (2025 HSC Q2 (1 mark): Software development approaches)
Technique for the question types
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Extended response: Plan with the command word, give a judgement or explanation supported by named details from the stimulus, use course terms and cover both sides when asked.
Common mistakes
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: Waterfall approach · WAgile · Iteration workflow