[bb01100100]

Please don't. You do not have experience... Therefore you're misrepresenting yourself and wasting the time of other team members who will expect you to know what you're doing.

If you don't know what you're doing, you introduce risk into a project by getting reqs wrong, not being able to engage all the correct stakeholders, not having a methodology for carrying out analysis and getting to the real issues, etc.

Given that most BA jobs involve gathering reqs for IT change/dev projects, get involved with that first.. Writing reqs catalogues and getting experience talking to different stakeholders outside of IT.

Try and get involved with writing business cases (the business part of a BA), and find a senior BA to talk to, in order to find out what value you need to deliver.