What is the difference between Agile and Waterfall methodologies, and in what scenarios would you choose one over the other?

During my final year, I worked on a group project to develop a mobile app. We opted for the Agile methodology as we wanted to incorporate feedback from our peers and professors frequently. We started with a basic prototype, held sprint reviews every two weeks, and adapted our features based on the feedback we received. This iterative process allowed us to refine our app significantly before the final submission, leading to a successful project that earned us high marks.

In my role as a volunteer for a community service group, we organized a charity event. We used a more Waterfall approach since the event had a clear timeline and specific requirements—like booking a venue, securing permits, and arranging catering. We created a detailed plan, followed it step-by-step, and ensured everything was executed in order. This structure helped us meet deadlines and deliver a successful event, highlighting when a linear approach works well.

In my first job as a marketing assistant, our team worked on a campaign for a product launch. We initially used the Waterfall approach to outline our strategy and timeline, as the client had strict requirements and deadlines. However, as the campaign progressed, we encountered unexpected challenges that required us to pivot and adapt our messaging. Recognizing the need for flexibility, we began to incorporate Agile elements, such as weekly check-ins to reassess our plans and make changes based on real-time feedback, blending both methodologies effectively.