CST 438 Week 7

Task Tides

Throughout CST438, we examined two major approaches to managing software development projects: Waterfall and Agile. Waterfall follows a structured, linear process with distinct phases such as requirements gathering, design, implementation, testing, and deployment. In this model, each phase is completed before the next begins, and documentation is emphasized heavily upfront.

Agile, on the other hand, takes a more flexible, iterative path. Development happens in short cycles called sprints, with cross-functional teams delivering small, functional parts of the software regularly. Agile promotes collaboration, welcomes changes throughout the project, and focuses on working software over exhaustive documentation.

Both methodologies have their advantages and challenges. Waterfall offers structure and predictability, which can be useful when requirements are clear and unlikely to change. However, as we saw through our own project work, even the most detailed plans can overlook important details, and rigid processes can make it hard to adapt to new information or feedback.

Personally, I found myself preferring the Agile methodology. I appreciated its flexibility and responsiveness. No matter how meticulously a project is planned, things can be missed, and even a well-documented system might not fully meet a client’s expectations. Agile’s focus on regular feedback and continuous improvement feels more aligned with real-world needs, where change is inevitable and collaboration is key.

CST438 provided a meaningful introduction to both methodologies, but more importantly, it gave us hands-on experience in working iteratively as a team. It felt like a real-world development environment, where we had to plan, adapt, and build together. That practical exposure was one of the most valuable parts of the course.