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.
What are wireframes and why are they useful for a BA?
Show answer
BRD vs FRD?
Show answer
What is Agile and how does Scrum work?
Show answer
What are functional and non-functional requirements?
Show answer
What is scope creep and how do you control it?
Show answer
What does a Business Analyst do?
Show answer
What is a use case diagram?
Show answer
Write a user story with acceptance criteria for password reset.
Show answer
What is gap analysis?
Show answer
What is the hierarchy of epic, feature and user story in Agile?
Show answer
What is backlog refinement and what is the BA's role in it?
Show answer
What is the difference between a sprint review and a sprint retrospective?
Show answer
How is Kanban different from Scrum?
Show answer
Use case vs user story?
Show answer
What is a traceability matrix?
Show answer
How do you prioritise requirements?
Show answer
What techniques do you use to elicit requirements?
Show answer
What is Kano model in prioritisation?
Show answer
How do you handle changing requirements?
Show answer
What is a BRD review and who signs it off?
Show answer
What are acceptance criteria?
Show answer
What is the role of a BA in Scrum?
Show answer
How would you prioritise 10 features with a limited budget?
Show answer
What is a product backlog vs a sprint backlog?
Show answer
What is a process flow and which tools do you use?
Show answer
What is a feasibility study?
Show answer
What is a user story and what makes it good?
Show answer
What is the difference between Definition of Ready and Definition of Done?
Show answer
Why do Agile teams estimate in story points rather than hours?
Show answer
What is AS-IS and TO-BE process modelling, and where does BPMN fit in?
Show answer
What is User Acceptance Testing (UAT) and what is the BA's role in it?
Show answer
What is a change request and how does change control work?
Show answer
How is a product owner's role different from a business analyst's role?
Show answer
In the middle of a sprint, a senior stakeholder asks to add an urgent feature. What do you do?
Show answer
A stakeholder's only requirement is 'make the app faster'. How do you turn this into clear requirements?
Show answer
Developers and testers interpret the same user story differently. How do you fix this?
Show answer
Write Given-When-Then acceptance criteria for applying a discount coupon at checkout.
Show answer
Split the epic 'Customers can track their order online' into user stories.
Show answer
What steps would you follow to create an AS-IS process map for a customer refund process?
Show answer
Tell me about a time you discovered a missed requirement late in a project.
Show answer
What is a spike in Agile and when would a business analyst request one?
Show answer
What is user story mapping and how does it help plan releases?
Show answer
Write non-functional requirements for an online payment page.
Show answer
You must gather requirements to replace a 15-year-old legacy system with no documentation. How do you approach it?
Show answer
A release passed all system testing, but business users reject it during UAT. What went wrong and what do you do?
Show answer
Describe a time you led the requirements phase of a large project.
Show answer
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.