Requirements & Agile Interview Questions for Business Analyst

A BA bridges business and technology: gathers requirements, analyses data and processes, documents BRD/FRD and makes sure the final solution actually solves the business problem.

A BRD states what the business needs and why. An FRD details how the system should behave to meet those needs (functional specifications).

Clarify the goal behind each request, map them to business objectives, prioritise with MoSCoW, run a joint session, then document the decision and get sign-off.

As a customer, I want to reset my password by email so that I can get back into my account. Acceptance criteria: • Reset link expires in 15 minutes • Password rules are shown while typing • A success message appears after reset

Score them with RICE or value-vs-effort, align with goals, consider dependencies and risks, validate with stakeholders, then use MoSCoW for the release plan.

Compare the current state (as-is) with the desired state (to-be), list the gaps in process, people or technology, and plan actions to close them.

Waterfall runs fixed phases one after another with requirements frozen early. Agile delivers in short sprints with continuous feedback, so requirements can change. In Agile, BAs maintain the backlog and user stories.

A use case describes the full interaction between an actor and the system (main and alternate flows). A user story is a short statement of need from the user's point of view, refined with acceptance criteria.

Use STAR: Situation, Task, Action, Result. Show that you listened, found the underlying goal, used data to align people and reached a documented decision.