A reader writes in with the following problem….
I have a position as a business analyst, in the IT department.. but my question is I’m not an IT person like I haven’t studied IT .. I’m helping with some inventories, testing, reporting. And I’m doing well so far (actually great like my manager always says to me.).
My question is, does the business analyst role have to have a background in IT? Or all it takes is some client engagement and mapping their requirements?
And if so, what exactly in IT I have to study? How long will it take? I’m really confused; I want to do something for my future.
An Analyst Is…..
Pshaw! Absolutely not! A business analyst, by definition in the BABOK, is:
A business analyst is any person who performs business analysis activities, no matter what their job title or organizational role may be…
Notice in this definition that there is no reference to activities as they align to IT or any other area of an organization. If you are performing recognized tasks that are associated with business analysis (requirements elicitation and engineering/management, process analysis, etc.), then you are an analyst. Some cynics might also include making coffee, taking out the trash, and waxing the developer’s car as necessary tasks of an an analyst. 
In all seriousness, the question’s verbiage indicates that this analyst’s boss might see something in him/her and your capabilities that might not be a personal realization. This is the beginning of understanding what business analysis is all about and there is plenty that a new analyst can do to begin to understand what that means to personally and professionally. A business analyst’s career can be housed in many different business units, so I would focus on what day-to-day actions are and how those actions affect/impact other areas of an organization. For instance, if an analyst happens to be on the business side, time spent will most likely be in analyzing things that make a difference to daily operations, business processes or organizational structure. In proceeding through these tasks, think about where the impacts will be to other areas of the organization. If a recommendation is made to business management that a new function is needed to allow a business user to do something, who in the organization will need to make that happen? In thinking in this fashion, one begins to see how business and IT operate together and how one’s actions affects others.
New Analyst Next Steps
For career growth, one the first things that a new analyst can do is to download a copy of How to Start a BA Career. It’s one of the best “get me going” books that I’ve read and covers many things a new BA needs know, yet are forgotten by writers after they’ve become seasoned. If any reader is developing enjoyment and an early passion for what analysis, I would encourage you to start reading everything that you can get you hands on, and there is no shortage of material. There are several major blogs, like this one, that provide insight about the profession from those working in the thick of it. This is important perspective that is not usually found in books. Here are some links that you might find useful:
- requirementsnetwork.com
- modernanalyst.com
- batimes.com
- practicalanalyst.com
- http://delicious.com/DougGtheBA/business_analysis (my own list of 100+ bookmarks that hold interest for me)
Join Up!
If you feel that you will likely stay in the field and wish to accelerate your learning, you can also invest in your future by joining the International Institute of Business Analysis (IIBA). International membership is around $95 USD (with discounts based on purchasing power disparity in some countries) and required before you can join a local chapter in most instances. Usually, local dues are around $25. As a new learner, you will find that the online library at theiiba.org that contains 350+ analysis titles and is free with membership, is a vast resource and pretty much pays for the membership fees after you’ve read a few books. Local chapter involvement and networking is a great way to find out where you stand, what you have to do, who can help you and what the business environment is like in your area.
|
By Doug Goldberg. Doug Goldberg is a Senior Business Analyst in the Dallas, TX, USA market. He has 15 years experience as an analyst in application development for financial, health care and technology companies. He has also programmed Java/J2EE for a period of time. Additionally, Doug is an avid business analyst mentor both online and in-person, a facilitator for CBAP study groups, an active guest blogger, and the current VP of Professional Development for the Dallas Chapter of the IIBA. View more blog posts by Doug Goldberg |
Related posts:
{ 1 trackback }
{ 4 comments… read them below or add one }
A really brief introduction to some of the buzz-words/concepts of IT is at: http://pmcentersusa.com/Portals/0/2009-09-22%20Technical%20Skills%20for%20Business%20Analysts%20Webinar.wmv
I believe it is free, about a half hour long and you will have to register to get it.
The most important basic “technical skills” you need as a BA are computer literacy and good to excellent mastery of the Microsoft Office suite (especially word, excel, PowerPoint and outlook). Sometimes you need some Visio skill or some MS Project skill.
I agree a business analyst should not have to be an IT guru to be a good BA. Just like Meg Whitman didn’t have to have a techie background to lead a techie company like ebay!
A good business analyst should
1. be a good listener
2. ask the right questions to the right people
3. be good at working with people
4. should be interested in understanding how the business works
I agree with Tom’s comments though:
The most important basic “technical skills” you need as a BA are computer literacy and good to excellent mastery of the Microsoft Office suite (especially word, excel, PowerPoint and outlook). Sometimes you need some Visio skill or some MS Project skill.
I’d drop the “skills” and use “understanding”, for both the technical side and the business side. You don’t need to be able to write code or build a PC from scratch, just understand how it can be done and some of the considerations that need to go into the process.
Similarly you don’t need to be able to audit accounts or fly a plane to deal with users who do these things and want a solution to their problem.
Obviously, YMMV depending on the industry you work in.