Which is better for business analyst: Agile or Waterfall?

In the SDLC there are four methodologies. We studied two methodologies, such as Waterfall and Agile. We check which is the best methodology for business analysts. Waterfall Methodology: The waterfall model is one of the oldest and most commonly used in software development. In waterfall methodology, a step-by-step process is followed, such that each stage must be completed before the next one begins, and going back to the previous phase is very difficult. The model is sequential and follows a strict order. Requirement gathering: In the requirement gathering stage, business analysts collect requirements from stakeholders and users by using elicitation techniques. After collection requirements, BA applied the MoSCoW technique to prioritise the requirements. Then I validate requirements using the FURPS technique. Then BA finally applied the prototyping elicitation technique. By creating simple mock-ups and screens to show how systems work and behave. Requirement Analysis: After requirement gathering, the BA prepared a UML diagram. The first use case diagram shows a relationship between different actors and system functions, and the BA prepared a use case specification. Then prepared an activity diagram to describe the flow of the process step by step. After finalising the diagrams, BA prepared the (BRS) Business Requirement Specification and (SRS) Software Requirement Specification. Design: From the use case diagram, prepared test case documents. Communicate with the client on the design and solution document. Then updated the requirement traceability matrix (RTM) to confirm that each requirement met its development, design and test cases. Development: In the development phase, an organised JAD session with stakeholders and the technical team was held for clarifying requirements. Also, BA helps in clarifying queries of the technical team during coding by referring to documents and diagrams. BA continuously conducts meetings with the client and technical team to clarify their doubts. Overall, BA maintained smooth communication between the client and technical team during development. Testing: In the testing phase, prepared test cases from the use cases to make sure every requirement was properly validated. BA performed high-level testing to check the overall system workflow was working smoothly as per business needs. And continuously updated RTM. After testing is completed, BA conducts UAT (User Acceptance Testing). Deployment: In the deployment, forwarded RTM to the client, which was later attached to the closure document. BA shares the end-user manual and conducts a training session for the end user. Agile Methodology: Agile is a flexible methodology where we build the project in small parts. Making changes in agile is very easy, and we can apply changes any time, any phase. In Agile, first performed market analysis to study customer needs, market trends and product gaps. Then applied enterprise analysis to check if the project was financially and strategically feasible. On this basis, create a product vision and roadmap to guide the team with goals and timelines. BA also manages product features by prioritising based on business value and ROI. And then handling product backlog main work to add, prioritise and refine user stories. BA writes user stories after gathering requirements and prioritises them by BV in the product backlog, then the developer selects user stories from the product backlog and puts these user stories in the sprint backlog, and In the sprint we build a small part of the project. A sprint is a fixed time box generally conducted for 2-4 weeks, and after completing one sprint, we show it to the stakeholder and take their feedback. After looking at all the processes, Agile is best for business analysts compared to Waterfall. In waterfall work, it follows in sequence if any changes are needed. It is not possible or very costly. But, in agile, changes can be made any time, which makes the project easier. That is why agile is the best for a business analyst.