by An Agile business analyst turns a vague business need into stories a development team can actually build, then keeps the backlog honest as priorities shift sprint to sprint. Interviewers want to know if you've lived the ceremonies, not just read about them: writing testable acceptance criteria, splitting an epic that's too big for one sprint, and handling a stakeholder who wants their feature moved to the top of the list.
Expect at least one question that asks you to write or evaluate a user story on the spot, and at least one about a real conflict between what a stakeholder wanted and what the team could deliver that sprint.
These 20 questions cover what Agile delivery teams actually ask, with sample answers built around specific sprints, tools, and numbers rather than general Agile talking points.
Agile business analyst at a glance
| Item | Details |
|---|---|
| Typical employers | Software companies, banks, healthcare systems, and government agencies running Agile delivery teams |
| Median pay | $101,860 for management analysts, the closest BLS category to this role (BLS, May 2025) |
| Job outlook | 10% growth from 2025 to 2035 for management analysts, about 94,100 openings a year across the broader occupation (BLS) |
| Education | Bachelor's degree is typical, often in business, information systems, or a related field |
| Certification | Not required but often preferred: the IIBA Agile Analysis Certification (IIBA-AAC). IIBA lists no formal prerequisites, though it recommends 2 to 3 years of agile analysis experience before the 85-question, 2-hour exam |
| Key tools | Jira, Azure DevOps, Confluence, story-mapping tools, sprint and backlog boards |
| Interview format | Interview with a delivery lead or product manager, often including a live exercise: writing a user story or working through a stakeholder conflict scenario |
How the interview usually works
- Resume and framework screen. Recruiters check which Agile framework you've worked in, Scrum, Kanban, or a scaled framework like SAFe, and for how long.
- Interview with a delivery manager or product owner. Mixes background questions with scenario-based ones on story writing and backlog prioritization.
- A live exercise, common at larger companies: writing acceptance criteria for a sample feature or walking through how you'd split an epic.
- Team fit conversation, often with a developer or scrum master, focused on how you handle mid-sprint changes and conflict.
General and background questions
1. What's your experience working as a business analyst on Agile teams?
Why they ask: They want your actual scope: which framework, team size, and how long, not a general claim of Agile experience.
How to answer: Name the framework, team size, and your specific responsibilities.
Sample answer: I've spent 3 years as a business analyst on a Scrum team of 8, including 2 developers, a QA engineer, a scrum master, and a product owner, building an internal claims-processing platform for a mid-size insurer. I own the backlog refinement sessions and write acceptance criteria for every story before it enters sprint planning, and I sit in on daily stand-ups to catch blockers early rather than waiting for the next ceremony.
2. Do you hold the IIBA-AAC or another Agile analysis certification?
Why they ask: Certification signals a working knowledge of Agile analysis beyond on-the-job habits, and they want an honest answer either way.
How to answer: State your certification status, or your specific plan and timeline.
Sample answer: I don't hold it yet, but I have the 3 years of agile analysis work IIBA recommends before sitting the exam, so I've registered for the AAC exam next quarter. It's an 85-question, 2-hour exam, and I've been working through the IIBA's agile extension materials on my own time over the past 2 months to prepare.
3. Which Agile framework have you worked in most, and how does that change your role?
Why they ask: The BA's role looks different in Scrum versus Kanban versus a scaled framework, and they want to know you've actually worked inside that difference.
How to answer: Name the framework and how your day-to-day work fits into it.
Sample answer: Most of my experience is in Scrum with 2-week sprints, where my role centers on refinement and writing acceptance criteria before planning. I also spent 8 months on a support team running Kanban, where there's no sprint boundary, so my job shifted toward continuously grooming a smaller, always-ready backlog instead of prepping a batch of stories every 2 weeks.
User stories and requirements questions
4. How do you write a user story so it's ready for a sprint?
Why they ask: A poorly written story causes rework mid-sprint, and they want to see your actual format and habits.
How to answer: Describe your story format and what makes it sprint-ready.
Sample answer: I write stories in the standard "as a, I want, so that" format, but the format matters less than the acceptance criteria attached to it. For a recent story about adding a saved-search filter, I wrote 4 specific acceptance criteria, including exactly what happens when a user saves a search with the same name as an existing one, since that edge case would have come up as a question mid-sprint otherwise. I also confirm story points with the team before it goes into the sprint, not after.
5. What makes acceptance criteria testable?
Why they ask: Vague acceptance criteria create disputes about whether a story is actually done, and they want to see specificity.
How to answer: Describe the difference between vague and testable criteria with an example.
Sample answer: Testable criteria state an exact input and an exact expected result, not a general behavior. "The system should handle errors gracefully" isn't testable. "If a user submits a claim form with a missing policy number, the system displays 'Policy number is required' and blocks submission" is. On a recent story, I rewrote 3 criteria that used the word "properly" into specific pass-fail conditions, since QA had flagged that "properly" gave them nothing to test against.
6. How do you split a large epic into sprint-sized stories?
Why they ask: Splitting work badly leads to stories that drag across multiple sprints, and they want a real method.
How to answer: Describe your approach, such as splitting by workflow step or user type.
Sample answer: I usually split by workflow step first, then by user type if a step is still too big. For an epic to add multi-factor authentication, I split it into separate stories for SMS-based verification, authenticator app support, and the account recovery flow, since each had a distinct backend and its own edge cases. That let us ship SMS verification in the first sprint and defer the authenticator app support to the next one without blocking the release.
7. How do you handle a story that's too vague to estimate?
Why they ask: Vague stories waste time in planning, and they want to know you can fix this before it derails a ceremony.
How to answer: Describe pulling the story from the sprint or splitting off a spike.
Sample answer: If the team can't estimate a story in planning, I pull it and schedule a follow-up conversation with the stakeholder rather than forcing a guess. For a recent story about integrating a new payment processor, the team couldn't estimate it because we didn't know the processor's API constraints, so I proposed a 1-day technical spike story first. That spike gave us enough information to write a properly scoped story for the following sprint.
Backlog and ceremony questions
8. Walk me through your role in backlog refinement.
Why they ask: Refinement quality determines how smooth planning goes, and they want to know your specific contribution, not just attendance.
How to answer: Describe what you prepare before the session and what you do during it.
Sample answer: Before refinement, I review the top 10 to 15 items in the backlog and flag any that are missing acceptance criteria or dependencies. During the session, I walk the team through each story's context and take notes on questions that come up, then update the story afterward rather than trying to finalize wording live in the meeting. On a recent project, this prep cut our refinement sessions from 90 minutes to about 50, since the team wasn't discovering missing information in the room.
9. How do you prioritize the backlog when multiple stakeholders disagree?
Why they ask: Competing priorities are constant, and they want to see a structured approach rather than picking whoever's loudest.
How to answer: Describe your prioritization method and how you present the tradeoff.
Sample answer: I bring both requests to the product owner with the business impact and effort estimate for each, since the decision belongs to them, not me. For 2 competing requests last quarter, a reporting dashboard from finance and a workflow fix from operations, I estimated the dashboard at 8 story points with a clear revenue-reporting benefit and the workflow fix at 3 points fixing a daily manual step for 12 people. Laying out both estimates side by side made the operations fix an easy call for the product owner, even though the dashboard request came from a more senior stakeholder.
10. What's your role in sprint planning versus the product owner's?
Why they ask: Overlapping BA and product owner responsibilities cause friction, and they want to know you understand the boundary.
How to answer: Describe the specific split of responsibilities on your team.
Sample answer: The product owner sets priority and decides what goes into the sprint; I make sure every story we're considering has clear acceptance criteria and no open questions before the team commits to it. In planning, I'm the person the developers ask clarifying questions to, and if I can't answer something, I flag it for a follow-up rather than letting the team guess and commit to a story with unresolved details.
11. How do you use the sprint retrospective to improve your own process?
Why they ask: They want to see self-awareness about your own contribution to the team's friction points, not just critique of others.
How to answer: Describe a specific change you made based on retrospective feedback.
Sample answer: In a retrospective 4 sprints ago, the team flagged that stories were arriving in planning with acceptance criteria that changed mid-sprint. I traced it to me finalizing criteria too close to planning day instead of during refinement. I moved my criteria review to 3 days before planning instead of the day before, and mid-sprint scope changes on our stories dropped noticeably over the following 2 sprints.
12. What do you do when a story doesn't meet the definition of ready going into planning?
Why they ask: They want to know you enforce the team's own standards instead of letting weak stories through under time pressure.
How to answer: Describe pulling the story or fixing it before planning starts.
Sample answer: I flag it before planning starts, not during the meeting, since raising it live puts the team on the spot. For a story missing a dependency check last sprint, I messaged the product owner the day before planning, and we agreed to swap it for a ready story further down the backlog rather than force an estimate on something with an open question.
Stakeholder and conflict questions
13. A stakeholder wants a feature the product owner has deprioritized. How do you handle it?
Why they ask: This tests whether you'll manage the conversation or just relay the conflict upward.
How to answer: Describe facilitating a direct conversation with the actual tradeoff laid out.
Sample answer: I don't make the prioritization call myself, but I make sure the stakeholder's request gets a fair hearing with real numbers attached. A sales director wanted a bulk-export feature moved up, so I got the product owner and the sales director on the same call, laid out the export feature's 5-point estimate against the 2 items it would bump, and let them work out the tradeoff directly instead of me passing messages between them.
14. How do you handle a stakeholder who keeps changing requirements mid-sprint?
Why they ask: Mid-sprint changes disrupt the team, and they want to see boundary-setting, not just accommodation.
How to answer: Describe your process for logging the change and protecting the current sprint.
Sample answer: I log the new requirement and confirm with the stakeholder that it's going into the next sprint's backlog rather than the current one, unless it's a genuine production issue. A stakeholder asked for a field change on a story already in progress, and rather than letting the developer absorb the change silently, I created a new backlog item for it and had the current story ship as originally scoped, which kept the sprint's velocity numbers accurate.
15. Tell me about a time you had to say no to a stakeholder's request.
Why they ask: They want to see you can push back professionally when a request doesn't fit the sprint or the roadmap.
How to answer: Describe the specific request and how you framed the no.
Sample answer: A marketing stakeholder wanted a promotional banner feature added 2 days before a sprint's demo, for a campaign launching that week. I told her directly it couldn't go into the current sprint without displacing a committed story, but I offered to fast-track it into the very next sprint and flagged it to the product owner as a priority candidate. She wasn't thrilled, but she understood the tradeoff once I explained what would have to be cut to fit it in.
16. How do you keep technical and non-technical stakeholders on the same page during refinement?
Why they ask: Refinement sessions often include people with very different vocabularies, and they want to see you can bridge that.
How to answer: Describe how you translate between the 2 groups.
Sample answer: I write acceptance criteria in plain business language first, then add technical notes underneath for the developers, so both groups can review the same document without translation. During a refinement session on an API integration story, a business stakeholder asked what "rate limiting" meant, and instead of letting a developer answer with jargon, I explained it in terms of how many requests our system could send per minute before the vendor would reject them.
Behavioral questions
17. Tell me about a time you found a gap in requirements before it caused rework.
Why they ask: Catching gaps early saves the team real rework, and they want a specific example, not a general claim of attention to detail.
How to answer: Describe how you found it and what it saved.
Sample answer: While reviewing a story for a refund workflow, I noticed the acceptance criteria didn't address partial refunds, only full ones, even though partial refunds made up about 30% of our support team's refund requests. I flagged it during refinement instead of after development started, and the team added a fifth acceptance criterion for partial refunds before the story was estimated, which avoided a rebuild that would likely have taken another half sprint.
18. Tell me about a sprint that went badly and what you changed afterward.
Why they ask: They want to see accountability and a real process fix, not a vague lesson learned.
How to answer: Describe the specific failure and the concrete change you made.
Sample answer: A sprint 6 months ago missed its goal because 3 stories turned out to depend on a database migration nobody had flagged during refinement. In the retrospective, we traced it to skipping a dependency check on stories that looked straightforward. I added a dependency question to our refinement checklist afterward, and we haven't had a similar miss since.
Situational questions
19. A developer flags that a story's acceptance criteria are impossible to build as written, mid-sprint. What do you do?
Why they ask: This tests your response under time pressure without derailing the sprint.
How to answer: Describe getting the facts, then working out a fix with the team.
Sample answer: I'd get the developer to explain exactly what's impossible and why, since sometimes it's a genuine constraint and sometimes it's a misunderstanding of the criteria. If it's a real constraint, I'd work with the developer and product owner to adjust the acceptance criteria to something achievable within the sprint, and if that's not possible either, I'd recommend moving the story back to the backlog rather than shipping something that doesn't meet the original need.
20. The product owner is unavailable for 2 days during active refinement. What do you do?
Why they ask: They want to see whether you can keep the team moving without overstepping the product owner's authority.
How to answer: Describe what you can decide versus what has to wait.
Sample answer: I'd keep refining the stories that don't need a priority call, clarifying acceptance criteria and flagging dependencies, but I wouldn't reorder the backlog or make scope decisions in the product owner's absence. For a 2-day gap like that recently, I prepared a list of 3 open questions that needed the product owner's decision and had them ready for her return, instead of letting refinement stall entirely or guessing at answers myself.
Questions to ask the interviewer
- What Agile framework does the team use, and how long has it been running that way?
- What tools does the team use for the backlog and sprint tracking?
- What's a recent example of a stakeholder conflict the team had to work through?
- How is the definition of ready enforced before stories enter planning?
- Is there support for pursuing the IIBA-AAC or a similar certification?
- What does a typical refinement session look like on this team?
How to prepare
- Bring a real story you've written, with its acceptance criteria, so you can walk through your actual format instead of describing it abstractly.
- Know your framework specifics: sprint length, ceremony cadence, and tools, since interviewers ask for these directly.
- Review a stakeholder conflict you handled, with the actual tradeoff you presented, since this comes up in nearly every Agile BA interview.
- Prepare 2 or 3 specific stories: a requirements gap you caught early, a sprint that went wrong, and a stakeholder disagreement you resolved.
- If you're pursuing the IIBA-AAC, know the exam format and your timeline, since certification status comes up directly.
If you're comparing this role to related delivery or analysis positions, our salesforce business analyst interview questions guide covers a platform-specific version of this work, and our functional lead interview questions guide covers a related delivery role. For a look at how this work differs from adjacent project roles, see our data analyst vs. project manager comparison.