COMMENTS
Thats a wonderful post Sir,.
I was hired as a junior business analyst...and being raised from a novice to a BA, there are still more to learn to become a "Business Analyst"...I should say that its really hard to find a mentor for BA...
Very good subject brought out in an excellent manner! There are very few companies/ teams who train newbies to BAs. I was raised by my company and of course, there is still a lot to learn in this profession.
Very True!!. I am a victim of such a situation. However I'm still trying and would not stop my efforts until I find one. I have very keen interest in the business analysis. I have finished my masters in IS with a GPA of 6.56/7.0 and also have a business degree and am still strugling to find one job. When ever I apply or trie to find a place I get only one answer and thts lack of experience. Just really want ask is there anyway I can enhance myself anymore or is there any alternative to experience? How will I get experience if I don't get any opportunity. Its a deadlock for me.
Hi All,
This is Fareed. Currently working as a Consultant(Software Engineer) and want to move to business analyst role. Could you please guide me regarding this and if possible please provide me your contact details.
Regards,
Fareed.
Good article - although I would stress that I think it overstates the problem somewhat. All existing BA's began somewhere didn't we?
In answer to the concerns about "lack of experience" I believe that you will find a lot of organisations foster BA talent from within and this is being overlooked. I have seen this firsthand many times in large corporates I have worked for - call it an "environmental apprenticeship" if you will.
Therefore my advice to aspiring BA's is to find roles that allow you to demonstrate your aptitude and skills relevant to BA work. Characteristics such as initiative and persistence, good communication skills and work habits i.e. so called "soft-skills" will get you noticed by management - don't be shy about expressing your interest in a BA role as part of your career development either.
All going well when that next BA vacancy comes around you'll be the one getting hired ahead of someone externally
Cheers CT (NZ)
Adrian:
“You can’t drive the car until you know how to drive a car.”, is exactly the type of response I've grown accustomed to in my search for the elusive entry-level BA role.
Your blog does an incredible job of capturing the way that I feel. I graduated in the IT field, and from my experiences and observations as an intern in the telecom-IT world, I felt that a BA role was exactly what I craved for as a career.
Unfortunately its exactly as you say... the "real" world BA roles are all experience-heavy and its difficult to enter the game as a noob.
It is a disappointing realization (@C Tuohy), that the standard way to get into the BA-field, is to enter into another field, and hop-scotch your way across.
Hi Adrian,
I would suggest that companies are using the current economic slow down to:
1. Lower BA wages
2. Force BAs to either train for ridiculous certifications or require such extensive background that the company, in essence, gets two or three employees for the price of one.
3. Push senior BAs into junior roles.
http://almostasfunny.blogspot.com/2009/08/taking-advantage-of-bas-because-they.html
This is so absolutely true and not overstated. For me, it just opens up more questions ...
The BAs here: how did you get started in the field? It's likely you stumbled into it just like me and in multiple iterations of the analyst role: BSA, OA (Operations Analyst), Reporting Analyst, Project Analyst etc.
Remember that first interview? How did you prove you could do the job?
Have you noticed people who hire a BA know they need one but don't know how to utilize them? They all have to pave their own way ... maybe this is just projection though since I just discovered this site today and I've been doing this work for 10 years :)
I agree with this article. I have done a lot of the work that is what I see described as the Business Analyst's role.... ellicitation, use case, data discovery and the like, but in organizations that did not have defined Business Analyst positions, or for that matter, Project Manager positions. Not only that, there were no formalized systems in place for documentation that a BA produces. Most of the work I've done has been learned while wearing a Systems Analyst/Developer hat.
I want to formalize my experience within a company that actually has positions that are specified as Business Analyst positions. The problem I am running into is that finding good examples of various documentation, such as use case, HLD, FDD, etc don't seem to be available.
I am currently trying to find someone that can be something of a mentor to me, particularly around the areas of knowing what documentation and deliverables are used in each knowledge area. I am finding that to be a very hard task.
Being a BA is not a profession- there's no required curriculum nor does it require a license. That being said:
I think there are two or three ways one breaks into the BA title: a Developer who is using a BA line in his/her resume before continuing to a Project Manager role. Then there's the Help Desk/Installer or other 'expert' on a given application that is awarded the title when the business decides it needs a go between to the Development Team. Then there's folks like me who used to be Technical Writers who were watching what the BA did and said to themselves- i could do that and double my salary.
:Look around your current shop and see if there are projects on which you can gain experience, sell yourself as a BA (yeah, the first one's always hard, but there's someone out there that'll hire and mentor you) or eve n volunteer your services to a non-profit (Church, Red Cross, Mosque, Synagogue, Park District, School- you get the idea.
While you're learning, you will identify problem areas in which you'll think you failed. Bring 'em back here and we'll discuss them and what you can do to avoid them in the future (which might be a pretty dang good series for Adrian). Be sure you know how to create requirements from the people that think at the 60,000 foot level and/or the ones who are interested in the tiniest of detail. Hiint: You'll need to abstract the business process to express the functional requirements. VISIO is an excellent tool to help you diagram pseudo-code, abstraction and if you put 'em in color, the team won't be so obvious in ignoring your highly evolved Use Cases/Technical Specifications/Data Maps until you alpha test and start shaking the paper and yelling 'Why didn't you READ this?' and laughing to yourself because the DevTe3am is needless going to spend the couple of nights doing what they should have dome originally.