Hi aAziz,

I would have to disagree with your mentor - I don't think it's necessary to have any technical background in order to be a 'good BA'.  I've known many great BA's who did start out as developers, but I've also known many who have no technical background.  I would suggest this path only if it's already of interest to you - and I'm guessing that if you're looking for a second opinion, it's because the developer path may not hold as much interest for you.

There are lots of different BA career paths, and as you gain experience you'll begin finding types of work that you prefer and that are a good fit to your personal strengths. What is it about a career in business analysis that attracts you at this point?  The answer to this question may help you find a starting path for your new career.

A Requirements Engineer is a person who focuses on requirements definition and analysis, whereas a Business Analyst title could refer to a wide variety of different responsibilities that fall under the BA profession.  A Business Requirements Specification usually refers to requirements that are purely business-oriented, with no reference to any system functionality.  A Software Requirements Specification (often called a Functional Requirements Specification) is a way of documenting required functionality for a system ('what' the system needs to do, not 'how'...). 

And no question is stupid - so ask away!

Sandy

Hi aAziz,

Based on your response to Sandy it sounds like being a BA would be an interesting avenue for you. Does your company require that you get experience in another role before becoming a BA? You mentioned that other graduate colleague have already entered the role, but I was not sure if that was at your firm or not.

If you want to stay with your current company, I would suggest talking to supervisors of BAs and find out how you can apply for a position, and what, if any, roles you need to take on before they will consider you. If you are willing to move companies, start talking to recruiters or other firms in your area to understand what you would need. As a start, I would suggest talking to your colleagues who have already landed BA positions to find out how they got heir jobs.

aAziz,

I started out as a technical programmer - I wrote compilers and patched operating systems. This may sound very detailed and systems oriented, and it is. But to be a good BA one must be able to abstract the essence from the detail - something that Tony Markos articulates consistently and passionately; but very few appear to get this fundamental point!

To become a good BA there is no short-cut. There may be many paths, but eventually you need a few years under your belt to be called a good BA. Don't fret over the title (associate BAs) of your contemporaries ; know that it takes a few years before you're a good/excellent BA. To become a CBAP you need at least a few years practical experience; so plan your career. But more importantly, practice getting to the essence of things! So after you've been given lots of details, asked yourself the questions "what are they doing?","what do they want?"; and "what do they need?" 

Back to your mentor. If what you are specifying as a BA is going to become an IT system, then its good to have some knowledge (and experience) of systems. Case in point: Utzon the architect of the Sydney Opera house designed the building without much regard to the construction of the building. It took a lot of government funding and construction engineering know-how to get it built; and lots of un-happiness!. Read  http://en.wikipedia.org/wiki/Sydney_Opera_House

warm regards,

K