A common question asked by teams adopting agile is "what does business analysis look like in agile?" The common answer is "writing user stories".
Okay, maybe not wrong, but certainly not the whole story (pardon the pun). Business analysis in agile is concerned with understanding the problem and possible solutions in order to ensure the team is building the right thing. User stories can be helpful, but are certainly not sufficient for doing that.
In this session, Kent McDonald describes how you can perform just enough business analysis to discover the right things to build. This includes how to really use value to decide what to build first, why process flows, data models, and mockups are still extremely helpful, and why the function of user stories is more important than their form.
Along the way, Kent shares examples from a system replacement project he is working on and suggests ways you can apply these techniques to your own projects.