Agile is best for Business analyst to develop clear & fast development project

First we need to know about this Agile and Waterfall. Agile and Waterfall are the methodology were the software development company will use this methodology to build and application or project. so, this both methodology's have different way's to develop the project. First we discuses about the Agile, The Agile is a frame work and in the Agile there will be continues customer interaction will there to know the customer feedback and the changes and in Agile the Business analyst will prepare the User stories based on the customer requirements and needs the business analyst will prepare in step by step to understand the development team to develop the application. And in the user stories the business analyst will thing from the user point of view to know the needs and the business analyst will prepare the as user and in user stories the business analyst will mention the priority, Business value (BV) , Complexity points (CP) and Acceptance criteria each and everything in clear to understand the developers And after completing the each sprint the team will interpret the customer to know about the feedback and if customer want any changes they will work on that change request easily this will help the project success. The product owner will decide the what should and what work will need to work first in the product backlogs, based on the product owner priority the team should work. The product owner and business analyst will collaborate will the stakeholders to get information. And in Agile there are meeting like sprint planning, daily scrum meetings, sprint review and sprint retrospective. This meetings are conducted by product owner and business analyst in this meeting the whole team and other teams will gather and discuses about project updated, feedback, and improvements about the project and bugs and errors and corrections. The team will work based on the product owner priority. Waterfall by use this methodology this is old methodology in this waterfall we have elicitation techniques to collect the requirements and need from the customer and we have some many elicitation techniques like brainstorming, interviews, document analysis, focus group, Revers engineering, Prototype etc, So, this are the techniques we use to collect the requirements from stakeholders. In the brainstorming: we can generate more ideas about the particular problem this will discuses the team to get more idea about the problem, Interviews: In this the business analyst will prepare some question for the stakeholders to take feedback and requirements, in interviews we have structured and unstructured, In the structured the business analyst prepare some question for the stakeholders and in unstructured the business analyst will ask question based on there topic. Document analysis in this the business analyst will verify the existing the document to know the current problem and old documents. In this waterfall we have to prepare the documents like Business requirement document (BRD) and Functional requirement document (FRS). After prepare the documents the development team will develop the application based on the documents. In waterfall methodology after completing the whole project only we can see the application.