mediumConceptScenarioEntryMidSenior
What does a business analyst do on an agile team, and how does requirements work survive without a signed-off specification?
6 min readUpdated 2026-08-15
Answer
Short answer
The analysis does not shrink, it changes container: elicitation, rule-finding and precision now land in refined backlog items and acceptance criteria at the point of build.
Was this answer helpful?
Likely follow-ups
- Who writes acceptance criteria on your team, and who is allowed to change them once the sprint has started?
- A story is refined, estimated and pulled in, then a rule turns out to be wrong on day three. What do you do?
- How do you split a story that the business insists cannot be delivered in parts?
- Where do the rules that span several teams live, and who notices when one of them changes?
Related questions
- The business says this story cannot be delivered in parts. How do you split it anyway?mediumAlso on story-splitting and agile-ba4 min
- How do you split a story that is too big to fit in a Sprint?mediumAlso on story-splitting4 min
- What is the Definition of Done, who owns it, and what do you do with an item that misses it at the end of a Sprint?mediumAlso on acceptance-criteria4 min
- Everybody signed off the requirement and two of them still mean different things by it. How do you catch that before the build?mediumAlso on acceptance-criteria6 min