On a broader note you should consider the role of the BA on an Agile project.  Many BAs and PMs will tell you thst BAs are really useful for Agile projects, but when you look at the books and articles on Agile they don't often talk about the role of a BA.

Instead you have a focus on putting the client in the room with developers and letting high bandwidth communication between these two groups solve the requirements elicitation, analysis and prioritisation activities.

However, in an enterprise of any size you are rarely able to make this work in practice.  Firstly few product managers or process owners can spare enough time to give you the level of access required.  Secondly, larger enterprises suffer from the "too many chiefs" syndrome, whereby there are many stakeholders with suffienct voice to be able to veto any design decision after the fact.

This highlights the role of the BA.  The BA on an Agile project is the voice of he collective cutsomers; that is, the many various departments that are stakeholders to the projects, and even the actual real customers in some cases.  ANd they sit in the project war room acting in place of the client.