Hey infobeese friends J First of all thanks for taking time out and thinking of giving this article a read. Being a business analyst for past six years now, I want to dedicate my first post to all mates, co-workers who have shown interest in getting into this profession.
I usually come across this line: “Ravi, I want to become a Business Analyst”
My first response to all of them is always, what do you know about Business Analysis? I always get weird answer to this question because mostly they are people at early stages of their career getting attracted with the nature of the job (client facing, travels, uncertainty to name a few).
Of course, it is an exciting and respectful job and you want to become a business analyst but you should first invest genuine time and learn about the same.
I always show a deep interest in those candidates who start the conversation with asking questions like: “Ravi, what is actually Business Analysis?”
What is Business Analysis?
I am not going to type IIBA definition of Business Analysis here but will try to explain in my own words. For those of you wondering what is IIBA? - IIBA (International Institute of Business Analysis) is a professional association for Business Analysis profession and serves as Business Analysis Body of Knowledge.
Business Analysis is the very act of identifying business needs and depicting a solution. There you go, that is it. If you can do that – you are a Business Analyst.
You must be thinking where are IT systems here? – Well, depicting a solution does not mean you have to always suggest an IT system but rather it could be one of the solutions that you can possibly suggest to your customers.
The very job of the Business analyst is to identify business need and suggest solution. Anything that suffices the business need is a solution. The gap between business need and probable solution is a “Requirement”. Our job is to highlight these requirements.
Ok, now you understand what Business analysis is – what skills do you require to become a BA?
As a BA, everyone expects you to speak clearly so that those involved in solving the business problem understands you. You should convince stakeholders in your suggested solution so that they buy-in. Once stakeholders agree on a solution, you need to communicate the same to people who will develop or work on the solution. If you have suggested an IT solution, these people will be developers. The pre-requisite here is that you have to communicate as simple as you can. You are there on a project to simplify things not to complicate. Why use Jargon and flashy words then.
You should learn the art of communicating with two hats on:
Business Hat: Wear this hat, when you’re speaking to customer, executives, and managers. These people are usually interested in the output and how it is going to solve their problem. I would suggest do not move into dirty level details unless asked for. Of course, we’ll go into detail but considering the audience.
For example: A CEO who is investing the money in a project would not be interest in how you are keeping the sales information in database with primary and foreign keys. But a Techie at customer end would love to get into discussion of this sort with you. As a BA, you should have a big heart and open mind to welcome discussions at any level.
Analyst Hat: Wear this hat, when you’re playing with low level details. These people are usually interested in how unique is your solution, how you are keeping the data, the screens, the workflows, the processes, et al.
You might want to go to white board, have a small visual and then start explaining. Take your time – BA’s are also human J. I like pictures; they speak more than my words.
All in all your talk should be cohesive, interesting, short but complete – otherwise people will eventually lose interest in you. In business world, time is money. No one wants to invest time with you unless they get something concrete out of it.
Writing Requirements
Oh, so you mean BA is a technical writer? If you’re a BA or an aspiring one – you must have faced this question many times till now.
Well - not at all, we are not technical writer. Technical writing is a special skill and require different bent of mind set. I won’t talk much about technical writer profile here but recommend you to Google it. May be we can invite a technical writer for future posts.
We cannot be everywhere – Stakeholders, developers, Integration system vendors, the teams are getting distributed these days. You should be able to clearly document the business problems, the requirements and the shared vision of solution to bring everyone on consensus. The key here is to write unambiguous requirements where anyone can only make one interpretation. Write in active voice and focus on defining what system “must” do rather than “should” do. I usually use “musts” and “wills” because it gives clear instructions.
Finally, I would suggest you to sit first with stakeholders and then with developers to give them your vision and understanding of the requirements. It would be very beneficial to have lead developers explain you what they have got from your session.
I came across a nice article depicting rules of how to write unambiguous requirements:
http://tynerblain.com/blog/2006/06/12/writing-unambiguous-requirements/
“Do you know? – The misinterpretation of requirements is the source of 40% of all the bugs.”
Be a good listener if you want to get a real knack of customer’s problem. They have hired you (or your company) because there is a need to achieve a goal. You must get a clear understanding of their problems before even trying to suggest any solution.
Do not interrupt when they are in a flow and telling their story of problems. You will miss some key pain areas that otherwise would have been put forward had you given them their time to speak. Wait for your turn and ask right questions at right time.
Back in your mind keep a track of all pain areas. The business is facing these issues because of some bad decisions from past. They are examples for you that you should learn from. If possible, build a knowledge base of these pain areas.
While listening to customers, understand their business model and need. There are so many wants at business level that requires your attention. They are waiting to originate provided you give them required attention. Ask right questions, move into detail, apply your brain and certainly you’ll find few questions that are unanswered. Throw these questions to your customer – try what if’s - they are usually beneficial in these scenarios. They might lead you to new path and new findings.
If you have got an idea, you have to bring it forward in front of everyone through any medium. Fire an e-mail, reach to your co-workers, give a phone call to anyone from customer’s team and discuss your idea with them. If you believe in something, you got to speak up.
Think of it this way, what is worst that can happen if you discuss your idea? I can only think of them saying, no this is not going to work for me, let’s brainstorm further. But there is a chance of your idea working for them and my friend – you’re recognized. It’s not that hard to be a BA. J
This small thing can be very effective in your BA career. Try to take control of customer’s requirement, own it and run the show. You don’t have to run away from the responsibility rather, take ownership. This will not only benefit you but provide you with more opportunities to learn upfront.
Try and learn about various software systems available in the market, learn from them and see how uniquely they are solving the problems. The analogy usually helps in solving business problems uniquely. These systems out there have some quality brain already applied on it. It is a knowledge source for you. Ask questions – why something is kept like that? Why like this why not like that?
You have to appreciate and love what you’re doing. You should always look at positive aspects in whatever you do whether it’s a BA or any profession. Keep yourself motivated, it’s an interesting job – you’ve been waiting to become a BA and here’s your chance. Prove yourself in couple of projects, you’re good to go!!
Don’t worry if you are missing with any of the above skills. Search for them and try to work on them. Being a BA is not an innate skill, it can be worked upon and develop. Work on yourself day after day – you’ll surely see improvement.
When there are some to-do’s, there are some not-to-do’s as well that you should not do as BA:
Yes, we are solving business problem but don’t do solution. Try to stay at a requirement level and identify behaviors expected from the system. Stick to “WHAT” is desired rather than “HOW” system/solution will achieve it.
Customer is king – but that doesn’t mean we have to say yes to everything. Rather, we are here to ensure the thinking applied should really solve the problem optimally and in a desired fashion. If you don’t like an idea or have a better one, challenge. Be sure to be diligent and bring your point to the fore.
Do not over complicate, keep things simple. It will help you in the long run. Try to break down problems into individual aspects and try resolving each and every aspect individually and then collectively. Simplifying things have great power - It makes life easy but is the most difficult thing to achieve. We humans tend to complicate simple things, try avoiding it.
Thinking where shall I start? Well there are lots of activities that you can plan and keep on adding in your kitty to reach nearer to the BA profile. You can start working as an assistant to a full-time BA and watch him in action for few weeks. Show interest and speak to your manager, senior, boss or anyone who can make this happen for you. Show that you’re really passionate about this profile and have learnt a lot. You may want to speak to that BA about the same to mentor you.
There are other qualities that I have seen in BA’s (me and other BA’s I’ve met) to keep them geared for the profile:
Read a lot; watch out how others are doing things and have an eagerness and hunger to learn. Buy some books, subscribe to few blogs/RSS feeds/newsletters that are of your interest. It can be anything from cooking to computers. These days content on any possible topic is easily available. I know you must be thinking about Infobesity but a little effort towards this area is worth.
Reading keeps your mind fresh and makes you open to new ideas.
There are many BA sites that are available where people write, share their experience, mentors other fellow BA’s who are seeking help. It will not only keep you up-to-date but also helps you connect to new people from the same profession. I am listing down few sites for you that you can join:
http://www.batimes.com/ - watch for Kupe Kupersmith (a wonderful BA always up for help)
http://www.bridging-the-gap.com/ - Laura Brandenburg (another wonderful BA always up – loved her writing style)
http://www.joenewbert.com/ - Joe Newbert (a fantastic guy from South Africa, a good connection)
http://www.theiiba.org – The IIBA official website.
All you have to do is network with BA’s through any medium and be a part of tribe. Twitter is a great place where you’ll find many full-time BA’s who are eager to help you. Search for #baot (business analysts on twitter) hash tag and you can simply follow to receive updates from them.
Don’t rush. There is no definite timeframe in which you can be a BA but will surely depend on amount of effort you will apply to reach the home. I wish you all best of luck. I am reachable at ravi.pardesi@gmail.com. Should you have any query, I am happy to help. You can also follow me on twitter at @rpardesi.
Liked the article - help spread the word. Share it!