CST438 - Week 7

CST438: Software Engineering – Week 7

Agile vs Waterfall

In week 7, we are exploring the differences between Agile and Waterfall methods in software development. When we talk about Agile, most requirements come from user stories and their continuous feedback during each iteration. In contrast, Waterfall relies heavily on documentation created early on to outline software specifications and requirements. The requirements gathering process involves formal documentation of use case scenarios, user interviews, and reviews of similar platforms when applicable. Making changes later in the development cycle can be difficult with Waterfall, so change management is controlled by CAB stakeholders who must follow strict procedures to approve or deny changes. Unlike Waterfall, Agile allows changes during the iterative process to accommodate mandatory design prerequisites or simple customer requests.

Waterfall methods include cost estimation as part of the initial requirements phase, resulting in a planned design that strictly follows those requirements. It’s important to note that Waterfall follows a linear progression through phases like requirements gathering, design, implementation, testing, and maintenance. The advantages of following a documented design with a scheduled plan include better project predictability, easier progress tracking, clear milestones, and improved control over scope and budget. Agile flexible approach to changes, however, can delay projects and drive up software development costs. Ultimately, the choice between Agile and Waterfall depends on the needs and priorities of stakeholders, developers, and the project context.