The BA Role in Scrum
Part of the Business Analyst Roadmap
In short
Scrum officially has three roles, and 'Business Analyst' isn't one of them. Yet many Scrum teams have a BA. Here's where you fit and what the team leans on you for.
In Scrum, BA responsibilities often blend into the Product Owner role, or the BA works closely alongside one — clarifying requirements, refining the backlog, and ensuring the team understands the 'why' behind each story.

Think of it like this
The wedding caterer's coordinator
The head caterer decides the menu. The cooks cook. The coordinator sits with the family and asks: how spicy, how many Jain plates, what time is dinner? Then makes sure the kitchen knows exactly that. In Scrum, that coordinator is often the BA.
Watch it happen
One story, passed through the BA
Customers want refunds
1/6A stakeholder describes a need in their own words. The BA asks why and who is affected.
The big ideas
What you need to know
Three official roles
Scrum defines Product Owner, Scrum Master and Developers. A BA usually sits within the team, often supporting the PO.
You own clarity
The PO owns what gets built first. The BA often owns making each item clear, testable and well understood.
Always available
Developers will have questions daily. Quick answers keep the sprint moving; slow ones block it.
Close the loop
You check the finished work against the business need, not just against the ticket text.
Save yourself the pain
Common mistakes
Oops
Acting as a gatekeeper who passes every message between developers and stakeholders.
Do this instead
Connect people directly when it helps. Your job is shared understanding, not controlling the channel.
Oops
Disappearing after writing the stories.
Do this instead
Stay with the team during the sprint. Most of the useful clarification happens while work is in progress.
Your mission
Map a real team
Quick check
A developer is blocked because the story doesn't say what happens if a payment fails. Who should usually help first?
Go deeper
- 1Read how BA and Product Owner responsibilities typically split (or merge) on a Scrum team.
- 2Learn why a BA in Scrum needs to work in smaller, more frequent increments than in waterfall.
- 3Understand this varies significantly by company — always clarify the specific expectations.
More topics at this stop
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.