The BA does the same kinds of work in every project. What changes is when and how much at a time.
In a waterfall project, analysis is a phase. The BA elicits and documents the requirements, the sponsor signs them off, and design, build and testing follow. Changes after sign-off go through a change request. It suits work with fixed rules, contracts or regulators who want to approve the scope up front.
In an agile team (Scrum, for example), requirements emerge. The product owner owns the backlog; the BA often works beside them, writing stories and acceptance criteria and refining the next few sprints' worth in detail while the team builds the current one. Change is expected and cheap.
Many organizations run a hybrid: a signed-off scope and business rules, then delivery in sprints with stories written as they go. Interviewers like to ask how your work changes between the two; the answer is timing, depth and who decides.