Software System Design May 20

Student’s Name: Venkatanaresh Tadoju

Institutional Affiliation: Monroe College, King Graduate School

Course Name: 23SP-CS620-151HY - Software System Design

Instructor’s Name: Syed Farid

Date: May 22nd, 2023

Agile and Waterfall project management methodologies are well-known. Software engineers

use these methods to design, build, and test their software. Both are widely used in software

development, though each is better suited to a specific type of project. After discussing the

differences between waterfall and agile development methodologies, I believe Agile would be

more appropriate for the project. Agile's iterative and flexible nature allows for better

adaptation to changing requirements and promotes effective collaboration within the context

of a group project. One example of the benefits of Agile comes from a previous group project

in which I was involved.

Our project began with a rather hazy set of requirements. As the development process began,

it became clear that the requirements needed to be refined and clarified. We accepted these

changes and incorporated able to accept these changes and incorporate them into our iterative

development cycles thanks to Agile. We held regular meetings with stakeholders and end-

users to collect feedback, which was critical in determining the project's direction. We

ensured that the end product met the evolving needs of our stakeholders by continuously

adapting and adjusting our approach.

Agile processes can be modified. Sprints are short bursts of work that emphasize agility. Even

after the project is completed, the technique allows for multiple paths to be taken. In contrast

to Agile, waterfall requires each step to be completed before moving on to the next. This

management style is beneficial to teams because it provides a clear path from beginning to

end. Even in the final stages of a project, agile allows for change and experimentation. As a

result, budgets are more flexible. Waterfall projects frequently have predetermined costs. The

budget cannot be changed midway through the project because it is fixed from start to finish.

The strategy is better suited to initiatives whose conclusions will be determined by further

research or testing.

Waterfall, on the other hand, may not be as effective in this scenario. The progression of a

waterfall is linear and sequential, with each stage dependent on the completion of the

previous one. It necessitates a well-defined set of requirements from the start, which may

conflict with the dynamic nature of group projects. If the project's requirements change

significantly during the development process, Waterfall can cause delays and difficulties in

accommodating these changes.

Agile, in my opinion, is a better fit for the project due to its ability to handle change in

requirements, promote collaboration, and embrace feedback. By using an iterative and

adaptive approach, your team will be able to navigate the project's uncertainties more

effectively, increasing the likelihood of success.