Skip to content

Requirements and Agile Interview Questions for Business Analytics

47 Requirements and Agile questions with answers for business analytics roles — 14 easy, 30 medium, 3 hard.

About Requirements and Agile

This topic covers the core BA craft: eliciting, documenting and managing requirements, and working inside Agile teams. Interviewers ask about BRDs, user stories, acceptance criteria, process modelling, UAT, change control and Scrum or Kanban ceremonies. Scenario questions test how you handle vague requests, late changes and disagreements between business and development teams.

Sheet progressStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

Agile vs Waterfall?

Save to ▾
Show answer
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.
02

What are wireframes and why are they useful for a BA?

Save to ▾
Show answer
Low-fidelity layouts of screens that help stakeholders visualise and agree on requirements before development starts.
03

BRD vs FRD?

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

What is Agile and how does Scrum work?

Save to ▾
Show answer
Agile delivers value in small increments with feedback. Scrum organises work in sprints with planning, daily stand-ups, review and retrospective, led by a Scrum Master and Product Owner.
05

What are functional and non-functional requirements?

Save to ▾
Show answer
Functional requirements describe what the system does (login, reports); non-functional ones describe how well it does it (speed, security, availability, usability).
06

What is scope creep and how do you control it?

Save to ▾
Show answer
Uncontrolled growth of requirements. Control it with a clear scope statement, change control process, impact analysis and sponsor approval for additions.
07

What does a Business Analyst do?

Save to ▾
Show answer
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.
08

What is a use case diagram?

Save to ▾
Show answer
A UML diagram showing actors and the actions (use cases) they perform with the system, giving a quick view of scope.
09

Write a user story with acceptance criteria for password reset.

Save to ▾
Show answer
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
10

What is gap analysis?

Save to ▾
Show answer
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.
11

What is the hierarchy of epic, feature and user story in Agile?

Save to ▾
Show answer
An epic is a large body of work that delivers a major business goal and spans several sprints, such as 'Online loan application'. It is broken into features or capabilities, such as 'Document upload'. Each feature is split into user stories small enough to finish in one sprint, such as 'As an applicant, I want to upload my PAN card photo so that I do not need to visit a branch'.
12

What is backlog refinement and what is the BA's role in it?

Save to ▾
Show answer
Backlog refinement, also called grooming, is a regular session where the team reviews upcoming backlog items to clarify, split, estimate and order them, so the next sprints have ready work. The BA prepares the stories in advance with business context, acceptance criteria, rules and examples, answers questions from developers and testers, and captures follow-ups. It is usually a short weekly session, not a sprint ceremony.
13

What is the difference between a sprint review and a sprint retrospective?

Save to ▾
Show answer
A sprint review is held at the end of the sprint with stakeholders to demonstrate completed work, gather feedback and adjust the backlog; it is about the product. A sprint retrospective is an internal team meeting afterwards to discuss what went well, what did not and what to improve in the way of working; it is about the process. The BA often helps demo stories in the review.
14

How is Kanban different from Scrum?

Save to ▾
Show answer
Scrum works in fixed sprints with defined roles such as product owner and scrum master, planned sprint goals and ceremonies like planning, review and retrospective. Kanban has no sprints: work flows continuously across a board, and work-in-progress limits on each column prevent overload. Kanban measures cycle time and throughput. Scrum suits product development with planned increments; Kanban suits support, operations and reporting requests that arrive unpredictably.
15

Use case vs user story?

Save to ▾
Show answer
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.
16

What is a traceability matrix?

Save to ▾
Show answer
A table linking each requirement to design, test cases and delivery status, ensuring nothing is missed and helping assess change impact.
17

How do you prioritise requirements?

Save to ▾
Show answer
Use MoSCoW (Must, Should, Could, Won't), value versus effort scoring or the Kano model, agreed with stakeholders based on business value and risk.
18

What techniques do you use to elicit requirements?

Save to ▾
Show answer
Interviews, workshops, surveys, observation, document analysis, prototyping and brainstorming, chosen according to stakeholders and project stage.
19

What is Kano model in prioritisation?

Save to ▾
Show answer
A model classifying features as basic, performance or delight attributes based on how they affect customer satisfaction, helping decide what to build first.
20

How do you handle changing requirements?

Save to ▾
Show answer
Log the change, assess impact on scope, cost and timeline, get approval through change control or backlog grooming, and update documents and stakeholders.
21

What is a BRD review and who signs it off?

Save to ▾
Show answer
Stakeholders and the sponsor review the Business Requirements Document for completeness and accuracy, and the business owner gives formal sign-off before design begins.
22

What are acceptance criteria?

Save to ▾
Show answer
Clear, testable conditions a story must meet to be accepted, often written as Given-When-Then scenarios.
23

What is the role of a BA in Scrum?

Save to ▾
Show answer
They help the Product Owner refine the backlog, write stories and acceptance criteria, clarify details with developers and support testing and demos.
24

How would you prioritise 10 features with a limited budget?

Save to ▾
Show answer
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.
25

What is a product backlog vs a sprint backlog?

Save to ▾
Show answer
The product backlog is the ordered list of all desired work; the sprint backlog is the subset the team commits to in the current sprint.
26

What is a process flow and which tools do you use?

Save to ▾
Show answer
A diagram of steps, decisions and owners in a process, made using BPMN or flowcharts in tools like Visio, Lucidchart or draw.io.
27

What is a feasibility study?

Save to ▾
Show answer
An early assessment of whether a proposed solution is technically, economically, operationally and legally viable before committing budget.
28

What is a user story and what makes it good?

Save to ▾
Show answer
A short requirement written as 'As a user, I want X so that Y', backed by acceptance criteria. Good stories follow INVEST: independent, negotiable, valuable, estimable, small and testable.
29

What is the difference between Definition of Ready and Definition of Done?

Save to ▾
Show answer
Definition of Ready is a checklist a story must meet before the team pulls it into a sprint: clear description, acceptance criteria, dependencies identified, designs attached and estimated. Definition of Done is the checklist for calling work complete: coded, reviewed, tested, acceptance criteria passed, documented and deployable. The BA mostly drives readiness, while the whole team owns done. Both reduce rework and arguments at sprint end.
30

Why do Agile teams estimate in story points rather than hours?

Save to ▾
Show answer
Story points measure relative effort, complexity and uncertainty compared with a reference story, using a scale like 1, 2, 3, 5, 8. People are better at comparing sizes than predicting exact hours, and points do not depend on who does the work. Over a few sprints the team's velocity, points completed per sprint, makes forecasting reliable. Points should never be used to compare productivity across teams.
31

What is AS-IS and TO-BE process modelling, and where does BPMN fit in?

Save to ▾
Show answer
AS-IS modelling documents how a process works today, including pain points, delays and handoffs. TO-BE modelling shows the improved future process after changes or a new system. Comparing the two reveals the gaps and requirements. BPMN, Business Process Model and Notation, is the standard notation, using events, tasks, gateways for decisions and swimlanes for roles, so both business and IT read the diagrams the same way.
32

What is User Acceptance Testing (UAT) and what is the BA's role in it?

Save to ▾
Show answer
UAT is the final testing phase where real business users check that the system supports their work and meets requirements before go-live. The BA helps plan UAT, prepares business scenarios and test cases from requirements, arranges test data, supports users during testing, triages defects versus change requests and tracks sign-off. UAT is not about finding code bugs, which earlier testing should have caught.
33

What is a change request and how does change control work?

Save to ▾
Show answer
A change request is a formal proposal to modify agreed scope, requirements, timeline or budget. In change control, the request is logged, the BA analyses impact on effort, cost, schedule, risk and other requirements, and a decision body such as the sponsor or change board approves, rejects or defers it. Approved changes update the requirements, plan and traceability. In Agile, most changes go through backlog reprioritisation instead.
34

How is a product owner's role different from a business analyst's role?

Save to ▾
Show answer
The product owner owns the product vision and the backlog order, makes final priority decisions and accepts completed work on behalf of the business. The business analyst works on understanding problems in depth: eliciting and analysing requirements, modelling processes and data, writing detailed stories and acceptance criteria and supporting the team and testers. In smaller teams one person may do both, but the PO decides what, while the BA clarifies how it should work.
35

In the middle of a sprint, a senior stakeholder asks to add an urgent feature. What do you do?

Save to ▾
Show answer
Understand the urgency and the business impact of waiting until the next sprint. Bring it to the product owner, who decides. If it truly cannot wait, the team agrees to swap out work of similar size so the sprint goal stays realistic, and the trade-off is made visible to the stakeholder. If it can wait, add it to the top of the backlog for the next sprint. Avoid silently adding scope.
36

A stakeholder's only requirement is 'make the app faster'. How do you turn this into clear requirements?

Save to ▾
Show answer
Ask which screens or actions feel slow, for which users, on which devices and networks, and how it affects the business, such as checkout drop-off. Gather current timings from monitoring data. Then write measurable non-functional requirements, for example 'the search results page loads within 2 seconds for 95 percent of requests on a 4G connection'. Confirm targets with the stakeholder and agree how they will be tested.
37

Developers and testers interpret the same user story differently. How do you fix this?

Save to ▾
Show answer
The story is ambiguous, so bring the three amigos together: BA or product owner, a developer and a tester. Walk through concrete examples, including edge cases and error cases, and write them as acceptance criteria, ideally in Given-When-Then format. Add business rules, sample data and mock-ups where needed. Update the story and use the same practice in refinement for future stories, so gaps are found before coding starts.
38

Write Given-When-Then acceptance criteria for applying a discount coupon at checkout.

Save to ▾
Show answer
Given a cart of 1,200 rupees and a valid coupon SAVE10 with a minimum order of 1,000 rupees, when the user applies it, then 10 percent is deducted and the new total is shown. Given an expired coupon, when applied, then the message 'This coupon has expired' appears and the total is unchanged. Given a cart below the minimum, when applied, then the user is told how much more to add.
39

Split the epic 'Customers can track their order online' into user stories.

Save to ▾
Show answer
Possible stories: As a customer, I want to see my order status (placed, packed, shipped, delivered) so that I know its progress. As a customer, I want an SMS or email when the status changes so that I do not have to check. As a customer, I want the expected delivery date so that I can plan. As a customer, I want a courier tracking link once shipped. As support staff, I want to see the same timeline so that I can answer queries.
40

What steps would you follow to create an AS-IS process map for a customer refund process?

Save to ▾
Show answer
Define the scope: where the process starts, such as a refund request, and where it ends, such as money credited. Identify the roles involved and draw swimlanes. Interview and observe each role, capturing steps, decisions, systems used, handoffs and time taken. Draw the flow in BPMN, mark pain points like rework loops and waiting time, and add measures such as average refund time. Validate the map with the people who do the work.
41

Tell me about a time you discovered a missed requirement late in a project.

Save to ▾
Show answer
Situation: two weeks before go-live of a billing system, a finance user asked how GST credit notes would work, which we had not covered. Task: assess and recover. Action: I analysed the impact with developers, found a simple configuration path for most cases plus a manual step for rare ones, and presented both options with dates to the sponsor. Result: we went live on time with a documented workaround and delivered the full fix next sprint.
42

What is a spike in Agile and when would a business analyst request one?

Save to ▾
Show answer
A spike is a time-boxed story used for research or experimentation to reduce uncertainty, not to deliver a feature. Its output is knowledge, such as a recommendation or a prototype. A BA might request one when the team cannot estimate a story because an external API, a data source or a regulation is unclear, for example checking whether a payment gateway supports partial refunds. The time box, often one to three days, prevents open-ended investigation.
43

What is user story mapping and how does it help plan releases?

Save to ▾
Show answer
User story mapping arranges stories in two dimensions. Across the top is the user journey as a sequence of activities, for example search, compare, buy and track. Below each activity, stories are stacked by priority. Drawing horizontal lines across the map creates release slices, where the first slice is a thin end-to-end MVP that covers every step at a basic level. It prevents a flat backlog where teams build one area deeply while the journey stays incomplete.
44

Write non-functional requirements for an online payment page.

Save to ▾
Show answer
NFR-01 Performance: the payment page loads within 2 seconds for 95 percent of requests at 500 concurrent users. NFR-02 Availability: 99.9 percent monthly uptime outside planned maintenance. NFR-03 Security: card data is never stored by the application, and all traffic uses TLS 1.2 or higher. NFR-04 Compliance: the flow meets PCI DSS and RBI payment guidelines. NFR-05 Usability: works on mobile screens from 360 pixels wide. NFR-06 Audit: every transaction attempt is logged with a timestamp.
45

You must gather requirements to replace a 15-year-old legacy system with no documentation. How do you approach it?

Save to ▾
Show answer
Combine several sources. Interview and observe users doing real tasks, and review screens, reports and outputs to infer business rules. Analyse the database and logs to see which data and functions are actually used. Work with long-serving staff and IT support for hidden rules and workarounds. Build AS-IS process maps, decide what to keep, drop or improve, and validate the findings with users. Plan data migration requirements early.
46

A release passed all system testing, but business users reject it during UAT. What went wrong and what do you do?

Save to ▾
Show answer
The team built what was written, but not what users needed, which points to gaps in elicitation, missing real-world scenarios or users not involved early. Capture each rejection and classify it as a defect, a missed requirement or a new request. Prioritise blockers with the product owner and agree on a fix plan and date. Going forward, involve users in demos every sprint and base UAT scenarios on real workflows.
47

Describe a time you led the requirements phase of a large project.

Save to ▾
Show answer
Situation: our company was replacing its loan origination system across five business units. Task: lead requirements with two other BAs in three months. Action: I set up a stakeholder map, ran structured workshops per unit, used shared templates and a traceability matrix, and held weekly review checkpoints with the sponsor to resolve conflicts quickly. Result: requirements were signed off on time, change requests in build stayed low, and the template was reused for later projects.

Frequently asked questions

How important is Requirements and Agile in Business Analytics interviews?

This topic covers the core BA craft: eliciting, documenting and managing requirements, and working inside Agile teams. Interviewers ask about BRDs, user stories, acceptance criteria, process modelling, UAT, change control and Scrum or Kanban ceremonies. Scenario questions test how you handle vague requests, late changes and disagreements between business and development teams.

How should I use the Requirements and Agile sheet?

Go top to bottom — easy to hard. Answer before opening each answer, tick what you solved and save misses to Last-Minute Revision.