How do you determine the most appropriate methodology for a project you are working on?

During my final year in college, I worked on a group project aimed at developing a mobile application. Given the project’s evolving requirements, we decided on the Agile methodology. This allowed us to work in sprints, gather feedback from our peers, and make necessary adjustments quickly. For instance, after our first sprint, we realized that the user interface needed significant changes based on user feedback. By using Agile, we could adapt our approach without starting over completely, which ultimately led to a successful project presentation. This experience taught me the importance of being flexible and responsive to change.

I volunteered to organize a community event where we needed to coordinate multiple aspects like venue booking, speaker arrangements, and marketing. We chose to follow the Waterfall methodology because the tasks had to be completed in a specific order. First, we secured the venue before reaching out to speakers, and once that was confirmed, we focused on marketing. By following this structured approach, we ensured that each phase was completed before moving to the next, which helped us stay on track and ultimately led to a well-organized event. This experience highlighted how understanding the sequence of tasks can be crucial in achieving project goals.

In my first job as a project assistant, I encountered a situation where we had to deliver a marketing campaign under a tight deadline. The team decided to blend methodologies—using Agile for the creative development process while utilizing Waterfall for the logistical aspects. This approach allowed us to quickly iterate on creative ideas while ensuring that our timelines for logistics were met. By combining these methodologies, we successfully launched the campaign on time and received positive feedback from our stakeholders. This real-world experience taught me how to evaluate and adapt methodologies effectively to achieve project outcomes.