CST 438 Week 7

Question Describe some of the differences between using an Agile process and using a  Plan and Document (or Waterfall) process. 

This week we compared Agile development with the more traditional Plan‑and‑Document (Waterfall) approach, and it’s surprising how differently the two processes shape a project. The first major difference is the process structure itself. Waterfall moves in a straight line from requirements to design to implementation, while Agile works in short, repeating cycles. Instead of waiting until the end to see results, Agile teams build, test, and adjust continuously.

Another key contrast is how each method handles requirements. Waterfall expects everything to be defined upfront, which can be difficult when the team doesn’t fully understand the problem yet. Agile takes the opposite approach: requirements evolve over time as the team learns more and receives new input. This makes Agile much better at adapting to change.

The two methods also differ in documentation style. Waterfall emphasizes heavy documentation early in the project, often before any code is written. Agile focuses on “just enough” documentation to support development without slowing the team down. Finally, the way each process handles feedback is completely different. Waterfall tends to gather feedback late, usually after most of the work is already done. Agile builds feedback into every iteration, allowing teams to adjust quickly and avoid surprises.

Overall, Agile feels more flexible and responsive, while Waterfall is more structured and predictable. Both have their place, but the differences in how they handle structure, requirements, documentation, and feedback can dramatically change how a project unfolds.