I suggest that, as a business analyst, you should focus more on agile modeling specfically, and less on agile in general.   The matra of agile modeling is to "model just enough".   That is to model what is essential (and only what is essential).   However, most recommend using UML techniques - which are very poor at capturing essential function inputs and outputs.   This is in large part the reason why you can read and read about agile and still not have a clear understanding of what a BA is suppossed to to. Nobody has yet thought through what essential modeling is.

Again, your task as a BA is largely to understand what essential modeling is - not, as most do, to learn 9,000 trival facts about agile, scrum, etc.

Tony