I want to move myself from IT support in to a BA role a quick backgroup; I've 5+ years exp in doing IT support and I enjoy communicating to both technical and non-technical ppl, I think im pretty good at it too. I have 2 college diplomas, 1 in computer and the other in business. So, anyway like most of u here, Im having the chicken/ egg problem. I cant seem to get my foot in to the door without any actual BA experiences?

I tried number of times trying to get a similar role (ie. System analyst , PM) but again still running in to the same chicken/egg problem. So I decided to make the best out of my current role as a IT support. Right now, I've an opportunity where I need to conduct a monthly meeting with our users on what kind of improvement they want to see from the IT department (ie. Better support,better software,etc) then I will then return this back to our IT HQ. so,I want to make the most of this. wish to use this for applying for a BA role here are my questions

1) can any1 show me the right direction, how to accomplish this in a structured way (the BA way)??? I just need a simple break-down on what needs to do… reference,etc


2) Any other way to get my foot in; beside what I'm already doing??? (ie.educaiton, association to join ,etc)??

Thanks guy..go easy on this newbie=)

First, Thank you for your reply=)

to answer your questions:

• BAs need strong problem solving and analytical skills -> Yes, i've be doing support for 5 years and i use my problem solving and analytical skills everyday
• BAs need strong communication, facilitation, and negotiation skills ->Im wouldn't say Im good at it but i've to communication to business users on technical issues, i might need some work in my writing skills thou.
• You need to have a good understanding of the role of the business analyst, the types of tasks that a BA performs, and the types of tools and techniques that an analyst uses -> I already took the BA essential course but it only gave me a brief intro to BA. It really dosen't have much infos on how to conduct a structure process on things like gather requirement, enterprice analysis, etc.

With all that said , is there any resources (websites, books, name of the tools,) that can assist me on conducting a structure process in doing what i need to do (refer to my first post) . I dont need a detailed protocol, just brief general step-by-step  to get me started.

again thank you for taking the time =)

Hi Edwardo,

You said "With all that said , is there any resources (websites, books, name of the tools,) that can assist me on conducting a structure process in doing what i need to do (refer to my first post) . I dont need a detailed protocol, just brief general step-by-step  to get me started."

If you want a step by step approach refer to my article "The Fundamentals of Business Analysis". What you will find is that business analysis is all about analysis and analysis is not a series of instructions that can be performed step by step: it is a process of building up requirements in a logical, rational, justifiable way. Mastering the concepts of the process is relatively easy compared to implementing it! If you want help with implementing it I would suggest you visit my website which is geared at doing just that for Business Analysts.

There is also an article on that website about breaking in to the field - but in general: the number 1 criteria employers look for is relevant experience but how can you get that without getting a first job?

In my experience Junior BAs usually aren't born - they mutate! The scenario I am thinking of is how I came to be a BA and one I have seen in my capacity as trainer many times: people from IT or the Business get a reputation for problem solving and get dumped in to the role when circumstances in their company change. Sometimes they jump in to the role but most often they seem to be dumped.

The question is - how did they get a reputation for problem solving? Answer: they were working alongside or even in change projects in some capacity and as a problem arose, the analysed it, solved it and got the reputation.

So there may be a strategy here: instead of looking for junior BA roles look for roles that involve working alongside projects (e.g. project management office) - in the UK there are always loads of temp agencies trying to fill these positions. Once in a project, make sure you have researched the role of a BA and know the outline of the theory at the very least. Then do your job, watch and wait for your opportunity and start volunteering to help BAs, sort out requirements issues and so on. Get a few months of that under your belt and then you can update your CV to reflect that you have actually been doing analysis, and you might even be able to transfer in the organisation you have been gaining experience in. You can then start applying for BA roles with the justification of having done the job even though you haven't been called a BA.

Oh - the other things are get testimonials (preferably from Project Managers and BAs) and keep copies of the analytical work you do: suitable anonymised, nothing impresses interviewers like examples of your own analysis and testimonials if you can get get them (I haven't been refused one yet!).

The good thing about your position is that you already in this process and I commend your intitiative on seeking advice for the best way to capitalize on it. If you would like any informal support on an on-going basis about what you are doing, how you are going about it and the risks and issues you face, then please email at [email protected]

Hope some of the above helps and good luck!!!

Guy