Business Analyst and Agile Scrum Interview Questions (2026 Master Guide)

Q1. What is the primary role of a Business Analyst (BA) in an IT project?

Foundation • 0-2 Yrs

A Business Analyst acts as the bridge between business stakeholders and technical development teams. The BA elicits, analyzes, documents, and validates business requirements, models operational workflows, resolves ambiguities, and ensures the delivered technology solves the business problem.

Q2. What is the difference between a BRD, FRD, and SRS?

Foundation • 0-2 Yrs

BRD (Business Requirements Document): High-level document detailing 'WHAT' the business needs and expected ROI. FRD (Functional Requirements Document): Technical translation explaining 'HOW' the system functions will operate. SRS (Software Requirements Specification): Comprehensive document detailing functional and non-functional requirements, interfaces, and architecture.

Q3. What are the key requirement elicitation techniques used by a BA?

Foundation • 0-2 Yrs

Interviews (1-on-1 with stakeholders), Focus Groups, Workshops (JAD sessions: Joint Application Development), Brainstorming, Questionnaires/Surveys, Document Analysis (reviewing legacy systems/SOPs), Observation/Job Shadowing, and Prototyping.

Q4. Explain the difference between Functional and Non-Functional Requirements.

Foundation • 0-2 Yrs

Functional Requirements define specific behaviors, actions, and features the system must perform (e.g., 'User can reset password via email OTP'). Non-Functional Requirements (NFRs) specify system quality attributes, performance, and constraints: Scalability, Security, Performance (response < 500ms), and Availability (99.9% uptime).

Q5. What is a User Story and what is the standard template?

Foundation • 0-2 Yrs

A User Story is a concise, non-technical explanation of a software feature written from the perspective of the end user: 'As a , I want , so that .'

Q6. Explain the INVEST criteria for writing high-quality User Stories.

Foundation • 0-2 Yrs

I - Independent (can be developed/released on its own); N - Negotiable (open to discussion); V - Valuable (delivers tangible user value); E - Estimable (can be estimated by developers); S - Small (fits within a single sprint); T - Testable (has verifiable acceptance criteria).

Q7. What are Acceptance Criteria and how is the Given-When-Then format written?

Foundation • 0-2 Yrs

Acceptance Criteria define the boundary conditions under which a User Story is accepted as complete. Gherkin format: 'Given , When , Then .'

Q8. What is Agile and how does it differ from traditional Waterfall methodology?

Foundation • 0-2 Yrs

Waterfall is a linear, sequential approach where each phase (requirements, design, build, test) must be completed before the next begins (rigid, slow feedback). Agile is an iterative, incremental approach delivering working software in short sprints (1-4 weeks), adapting rapidly to changing requirements.

Q9. What are the 4 core values of the Agile Manifesto?

Foundation • 0-2 Yrs

1. Individuals and interactions over processes and tools; 2. Working software over comprehensive documentation; 3. Customer collaboration over contract negotiation; 4. Responding to change over following a plan.

Q10. What are the 3 Scrum Roles and their responsibilities?

Foundation • 0-2 Yrs

Product Owner (PO): Owns the Product Backlog, prioritizes features, and maximizes business value. Scrum Master (SM): Facilitates Scrum ceremonies, removes impediments/blockers, and coaches the team. Development Team: Cross-functional professionals who build and test the increment.

Q11. What are the 5 official Scrum Ceremonies (Events)?

Foundation • 0-2 Yrs

1. Sprint (1-4 week container); 2. Sprint Planning (defining sprint goal and selecting backlog items); 3. Daily Scrum / Standup (15-min daily sync); 4. Sprint Review (demoing working increment to stakeholders); 5. Sprint Retrospective (inspecting team processes and continuous improvement).

Q12. What is the difference between a Product Backlog and a Sprint Backlog?

Foundation • 0-2 Yrs

Product Backlog: Prioritized, dynamic list of all features, enhancements, and bug fixes for the entire product, owned by the PO. Sprint Backlog: Subset of Product Backlog items selected by the dev team for execution during the current active sprint, along with their delivery tasks.

Q13. What is Definition of Done (DoD) vs Acceptance Criteria?

Foundation • 0-2 Yrs

Acceptance Criteria is unique to an individual user story (verifying specific business logic). Definition of Done (DoD) is a universal checklist applied to all stories across the team before they are marked complete: unit tests passed, code reviewed, QA verified, deployed to staging, and documentation updated.

Q14. What is Story Point estimation and why is Planning Poker used?

Foundation • 0-2 Yrs

Story Points estimate the relative effort, complexity, and risk of a user story (using Fibonacci sequence: 1, 2, 3, 5, 8, 13) rather than raw hours. Planning Poker is a consensus-based technique where team members reveal estimates simultaneously, discussing divergences to eliminate estimation bias.

Q15. What are Burn-Down Charts and Burn-Up Charts in Agile?

Foundation • 0-2 Yrs

Burn-Down Chart: Tracks remaining work (story points) over time during a sprint, showing whether the team is on track to complete the commitment. Burn-Up Chart: Shows total work scope alongside completed work over time, highlighting scope changes during a release.

Q16. How do you handle Scope Creep during an active project as a BA?

Experienced • 3-5+ Yrs

1. Document the requested change in a Change Request (CR) log; 2. Perform Impact Analysis (cost, timeline, dependencies); 3. Present tradeoffs to Product Owner and steering committee; 4. If approved, add to Product Backlog and re-prioritize existing features (trade-off) rather than overloading the active sprint.

Q17. Explain Gap Analysis and what framework you use to conduct it.

Experienced • 3-5+ Yrs

Gap Analysis identifies the difference between Current State ('AS-IS') and Desired Future State ('TO-BE'). Steps: 1. Document AS-IS business processes (BPMN); 2. Define TO-BE requirements; 3. Identify gaps (process, technology, data, skills); 4. Formulate transition roadmap to bridge the gap.

Q18. How do you resolve conflicting requirements between two senior executive stakeholders?

Experienced • 3-5+ Yrs

1. Facilitate a collaborative alignment session; 2. Trace requirements back to overarching corporate strategic goals and financial KPIs (ROI, regulatory compliance); 3. Present data-driven impact analysis and user research; 4. Propose phased compromise; 5. Escalate to Executive Sponsor for final arbitration if deadlocked.

Q19. Explain the Kano Model for feature prioritization.

Experienced • 3-5+ Yrs

The Kano Model classifies customer preferences into 5 categories: 1. Basic/Must-Have (essential, causes dissatisfaction if absent); 2. Performance (satisfaction scales linearly with execution); 3. Excitement/Delighters (unexpected features creating high satisfaction); 4. Indifferent; 5. Reverse.

Q20. What is MoSCoW Prioritization and how do you apply it to backlogs?

Experienced • 3-5+ Yrs

Classifies requirements into: Must have (critical non-negotiable for release), Should have (important but workarounds exist), Could have (desirable if time permits), Won't have this time (deferred to future releases).

Q21. How do you model complex business processes using BPMN 2.0?

Experienced • 3-5+ Yrs

BPMN (Business Process Model and Notation) visualizes workflows using: Pools and Swimlanes (representing departments/roles), Events (Start, Intermediate, End), Activities (Tasks, Sub-processes), Gateways (Exclusive XOR, Parallel AND, Inclusive OR), and Sequence/Message Flows.

Q22. Explain Use Case Diagrams and how Use Cases differ from User Stories.

Experienced • 3-5+ Yrs

Use Case Diagrams model interactions between Actors and System boundary. A Use Case is a comprehensive, structured functional document detailing Main Success Scenario, Alternate Flows, Exception Flows, Preconditions, and Postconditions. A User Story is lightweight, conversational, and focused on user value.

Q23. What is Velocity in Scrum and how do you calculate it?

Experienced • 3-5+ Yrs

Velocity is the average number of Story Points completed and accepted ('Done') by the development team per sprint. Calculated by summing accepted story points over the last 3-5 sprints and dividing by the number of sprints, used to forecast future release timelines.

Q24. How do you manage Technical Debt within Agile sprints?

Experienced • 3-5+ Yrs

Technical debt comprises accumulated suboptimal code shortcuts. A BA collaborates with the Scrum Master and tech leads to allocate a fixed capacity (e.g., 15-20% of every sprint) dedicated to refactoring, automated testing, and technical debt items on the backlog.

Q25. What is Root Cause Analysis and how do you conduct Fishbone (Ishikawa) & 5 Whys?

Experienced • 3-5+ Yrs

Fishbone Diagram categorizes problem causes into: People, Process, Technology, Policies, and Environment. 5 Whys drills down by repeatedly asking 'Why did this occur?' five times until the foundational systemic breakdown is uncovered.

Q26. How do you handle Epics and how do you split a large Epic into manageable stories?

Experienced • 3-5+ Yrs

An Epic is a large body of work spanning multiple sprints. Split via: 1. Workflow steps (split by sequential user action); 2. Business rules / variations; 3. Data types/channels (web vs mobile); 4. Happy path vs exception paths; 5. CRUD operations.

Q27. Explain the difference between Agile Scrum and Kanban.

Experienced • 3-5+ Yrs

Scrum: Time-boxed iterations (sprints), pre-defined cross-functional roles, prescriptive ceremonies, metrics based on Velocity. Kanban: Continuous flow without sprints, no prescribed roles, limits Work-In-Progress (WIP limits), metrics based on Cycle Time and Lead Time.

Q28. How do you document Non-Functional Requirements (NFRs) effectively?

Experienced • 3-5+ Yrs

Avoid vague terms like 'fast' or 'secure'. Quantify with measurable SLAs: 'The checkout API must process 1,000 transactions/second with response time < 250ms at 99th percentile under peak holiday traffic.'

Q29. What is Sprint Retrospective fatigue and how do you revitalize the team?

Experienced • 3-5+ Yrs

Occurs when retrospectives become repetitive complaint sessions without actionable outcomes. Revitalize via diverse retro formats (Start-Stop-Continue, Mad-Sad-Glad, Sailboat retro), focusing on 1-2 achievable action items with assigned owners tracked on the sprint board.

Q30. Explain User Acceptance Testing (UAT) and the BA's role in it.

Experienced • 3-5+ Yrs

UAT verifies the system satisfies real-world business operations before production rollout. The BA designs UAT test scenarios matching business workflows, coordinates business user testing, triages reported defects (classifying real defects vs new change requests), and obtains formal sign-off.

Q31. Write a complete User Story with Given-When-Then Acceptance Criteria for Password Reset.

Live Coding Challenge

User Story in INVEST format with happy path and error acceptance criteria.

Title: Self-Service Password Reset via Email OTP

User Story:
As a registered e-commerce customer,
I want to reset my account password using a one-time email OTP,
So that I can regain secure access to my account without contacting support.

Acceptance Criteria:
Scenario 1: Successful Password Reset
Given the customer is on the 'Forgot Password' page
When they enter a valid registered email address and submit
Then a 6-digit OTP valid for 10 minutes is sent to their email
And when they submit the correct OTP and a new 8+ character password
Then the password is updated and they are redirected to Login with a success message.

Scenario 2: Expired OTP Submission
Given the customer entered the OTP after 10 minutes
When they click 'Confirm Password'
Then an error message 'OTP has expired. Please request a new one' is displayed.

Q32. Write a SQL query commonly used by Business Analysts to find monthly revenue and customer count.

Live Coding Challenge

Aggregate monthly orders, sum revenue, and count distinct customers.

SELECT 
    DATE_TRUNC('month', order_date) AS sales_month,
    COUNT(DISTINCT customer_id) AS active_customers,
    COUNT(order_id) AS total_orders,
    ROUND(SUM(order_total), 2) AS monthly_revenue
FROM orders
WHERE order_status = 'COMPLETED'
GROUP BY 1
ORDER BY 1 DESC;

Q33. Write a Business Requirements Document (BRD) Executive Summary template.

Live Coding Challenge

Professional BRD opening section outline.

/* BRD Executive Summary Outline */
1. Project Background & Business Need
2. Strategic Alignment & Key Objectives (e.g., 25% churn reduction)
3. Project Scope (In-Scope vs Out-of-Scope)
4. Key Business Stakeholders
5. High-Level Assumptions & Constraints
6. Financial Cost-Benefit Analysis (ROI & Break-even)

Q34. Write a JIRA JQL query to find all unresolved High Priority bugs in the current active sprint.

Live Coding Challenge

JQL query filtering by project, issuetype, priority, and sprint status.

project = "FINTECH" AND issuetype = Bug AND priority in (High, Highest) AND resolution = Unresolved AND sprint in openSprints() ORDER BY created DESC

Q35. Write a Change Request (CR) log entry format.

Live Coding Challenge

Structured table attributes for capturing change requests.

CR_ID: CR-2026-042
Requested By: VP of Marketing
Description: Add Google Pay and Apple Pay payment methods to checkout
Reason: Reduce mobile drop-off by 18%
Impact Analysis: 12 Story Points, 4 days backend API + 2 days QA
Decision: Approved for Sprint 14 by Product Owner

Q36. Write a Use Case document structure for an ATM Cash Withdrawal.

Live Coding Challenge

Use case template detailing preconditions, flow, and exceptions.

Use Case Name: Withdraw Cash from ATM
Actor: Bank Customer
Preconditions: Customer has active debit card and PIN
Main Success Scenario:
1. Customer inserts card and enters PIN
2. System validates PIN
3. Customer selects 'Withdrawal' and enters $100
4. System checks account balance and cash inventory
5. System dispenses cash, prints receipt, and returns card
Exceptions:
3a. Insufficient Funds -> Display error 'Insufficient balance' and return card
1a. Invalid PIN 3 times -> Confiscate card and notify bank security

Q37. Write a JIRA JQL query to find all stories completed in the last 30 days for velocity calculation.

Live Coding Challenge

JQL query filtering on resolutiondate.

project = "CORE" AND issuetype = Story AND status = Done AND resolutiondate >= -30d

Q38. Write a Stakeholder Matrix (Power-Interest Grid) classification.

Live Coding Challenge

Categorize stakeholders into 4 quadrants.

1. High Power, High Interest: Manage Closely (Executive Sponsors, Product Owner)
2. High Power, Low Interest: Keep Satisfied (Compliance Officers, CISO)
3. Low Power, High Interest: Keep Informed (End Users, Support Reps)
4. Low Power, Low Interest: Monitor (External vendors)

Q39. Write a Definition of Done (DoD) checklist for a software engineering squad.

Live Coding Challenge

Standard team quality gates.

1. All Acceptance Criteria verified by QA
2. Unit test coverage >= 80%
3. Peer code review approved by at least 1 Senior Engineer
4. Zero High/Critical SonarQube bugs
5. Deployed to Staging environment
6. Product Owner formal sign-off

Q40. Write an INVEST validation check for a story: 'Build entire reporting module'.

Live Coding Challenge

Critique showing why it fails and how to split.

Fails INVEST:
- 'S' (Small): Too massive, cannot complete in a single sprint.
- 'E' (Estimable): Too ambiguous to estimate accurately.
Resolution: Split into 3 independent stories:
1. Story A: Export CSV summary of daily transactions
2. Story B: View monthly revenue chart on web dashboard
3. Story C: Filter reports by customer region