ICT2622
Assignment 3
Exceptional Answers
Due 5 August 2025
, ICT2622
Assignment 3
Due Date: 5 August 2025
Critical Analysis and Integrated Solutions for Iterative and Agile Development
Question 1 (Total: 08 Marks)
1.1 The Primary Objective of Each Iteration (3 marks)
In iterative development, the main objective of each iteration is to deliver a functional,
tested, and usable increment of the final system. This iterative cycle allows developers
to refine and improve the product through continuous feedback and evaluation. Each
iteration goes through phases of planning, analysis, design, coding, and testing,
ensuring that the system evolves systematically towards its final form. The goal is not
just partial completion but progressive value delivery and stakeholder validation
(Sommerville, 2016). Thus, every iteration should result in working software that brings
the project closer to completion.
This objective assumes that each increment adds user value and aligns with project
goals. However, there is a possible tension between fast delivery and deep architectural
design. If iterations focus only on visible functionality without strong design, technical
debt can grow, risking long-term system health. This reflects an agile philosophy, which
values adaptability over strict upfront planning. In the long term, this approach changes
project culture towards collaboration and flexibility, requiring teams to focus on
continuous user validation rather than fixed plans.
Assignment 3
Exceptional Answers
Due 5 August 2025
, ICT2622
Assignment 3
Due Date: 5 August 2025
Critical Analysis and Integrated Solutions for Iterative and Agile Development
Question 1 (Total: 08 Marks)
1.1 The Primary Objective of Each Iteration (3 marks)
In iterative development, the main objective of each iteration is to deliver a functional,
tested, and usable increment of the final system. This iterative cycle allows developers
to refine and improve the product through continuous feedback and evaluation. Each
iteration goes through phases of planning, analysis, design, coding, and testing,
ensuring that the system evolves systematically towards its final form. The goal is not
just partial completion but progressive value delivery and stakeholder validation
(Sommerville, 2016). Thus, every iteration should result in working software that brings
the project closer to completion.
This objective assumes that each increment adds user value and aligns with project
goals. However, there is a possible tension between fast delivery and deep architectural
design. If iterations focus only on visible functionality without strong design, technical
debt can grow, risking long-term system health. This reflects an agile philosophy, which
values adaptability over strict upfront planning. In the long term, this approach changes
project culture towards collaboration and flexibility, requiring teams to focus on
continuous user validation rather than fixed plans.
