The Business Analysis Blog

Building a Stakeholder Matrix requires analytical skills and soft skills. It is something you build as you interact with more and more people.

• accountable to bring in the change,
• motivated to bring in the change,
• responsible for bringing in the change,
• ideating the change and
• paying to affect the change.

• Satisfaction is must: The stakeholder matrix also helps a Business Analyst to find the stakeholders who are high on influence but the change may not be impacting them as much. Please ensure that pay attention to such stakeholders and keep them satisfied with your solution or ideas.
• Ensure Collaboration: The stakeholder matrix helps in identifying the stakeholders with whom a Business Analyst must collaborate and ensure that you have their support and agreement. These are generally the stakeholders who have high influencing powers and are greatly impacted because of the change.
• Keep a check: The stakeholder matrix also gives you the list of the stakeholders who are low on influence and are not being impacted by the solution. You can safely ignore these stakeholders but keep an eye on them in case there is any change in impact or influence.
• Keep informed: The stakeholder matrix helps you to classify people who just need to be in the loop but may not have high influence.

• I always keep a matrix, like the one shown above, in my notes. It helps me to classify people I meet into various quadrants. Since I keep it handy, I can easily update the quadrant of any stakeholder based on the latest information that I receive.
• When you are new in the project start with the organization chart, that can give you the initial list of stakeholders and their influence and impact based on their position.
• Next, when you meet the sponsor of the project as her a simple question: "who else could I contact to get more information on this?
• In your meetings with various stakeholders you can deduce who has more influence. It will mostly be the person who is getting referred by most of the other stakeholders.
• Prepare a RACI matrix.
• Perform a process mapping exercise, it is a great tool to identify the impacted people.

Business Analyst helps organizations fulfill the Business Needs within the constraints of Time, Budget and Regulations by defining an Optimal Solution.

Only define requirement for new work when the Queue steps forward

Just in Time Requirements
Just Enough Requirements
that are constantly validated.

It is important to ensure, as a Business Analyst that, stakeholders have spent enough time to have a clear Vision for an Agile Project. It is then important that, you make them spend time on creation of a high level scope and initial design. Ensure that, you draft an initial features list which can be groomed later in the project.

Without Vision, Roadmap and Success Criteria Agile Projects can go on forever

Tanya, an experienced and well appreciated Business Analyst, keeps running into Jen, a tough client who is always critical of Tanya's work. Jen makes it a point to criticize even the smallest of the shortcomings of Tanya's deliverable and always escalates it to crazy levels.

Rahul went for lunch after a hectic morning requirement gathering session with Jack. On returning he was shocked to see an escalation email from Jack complaining about the lack of quality of the requirement documents. It was shocking because Rahul had an interactive session with him and Jack did not even mention anything about the quality of documents.

Professionalism is what you display when the times are tough

• Think from Client's perspective. Step into the client's shoes and think of the issues that are bugging them. It will help you to understand the situation from their standpoint.
• Ask your fellow BAs for review. It is always a good strategy for BAs to work in packs. Make sure that you inculcate the practice of reviewing each other's work. This will not only to help you to reduce the number of client review comments but also to keep a tab on all the requirements that the client is listing for the project.
• Involve more people in your session. To ensure that you don't miss out on any of the things that client is suggesting in the requirements workshops or any other session, you should involve more people in the meetings. You may want to add a scribe to take the notes (again use you fellow BAs), an SME to simulate the discussion around the domain areas. It is also sometimes a good idea to ask a senior BA to facilitate the session for you.
• Professionalism is what you display when the times are tough times. Stay calm and always take your time to respond. If you are writing an email take a break and get something cold to drink before responding.
• Cover your back; keep records of your dealings with difficult clients. You may be targeted for political reasons.
• Take healthy criticism as learning. Criticism is not always bad; it shows that people still care for what you are doing. If there are things to learn from the criticism do learn them and become a better Business Analyst.
• Look for shortcomings and plug the gaps ASAP. Do a self critical analysis to find out your shortcomings and make sure you work on them to improve as a Business Analyst. Due to the nature of our profession we only get feedback from our clients or self analysis. Ensure that you use both the sources.
• Keep an eye on your deliverable. If they are not adequate do complete them.

Recently over the lunch table I was talking to one of my colleague who is struggling to improve some stagnated internal processes in his project. I offered to help him in my free time. Post lunch we went to his cubicle to discuss the problem in detail. As I got more involved I asked him if he has captured the details of the process in the current form (AS-IS) and if he has a vision of the future form of the process (TO-BE). He had done some impressive work and captured his understanding in Visio diagrams as well. It was very helpful to quickly understand the problem. I asked him if he has verified these diagrams with anyone else in the team. He denied saying he knew the processes really well and is capable of introducing the changes. I immediately raised my concern that to introduce a change he will need to involve the people who are concerned with the process. He asked me who all should he discuss this idea?

I put forward 4 simple questions in front of him to identify the people he needed to involve:

1. Who is/will be doing this task?
2. Whose head will roll if this goes wrong?
3. Anyone who can tell me more about this task?
4. Anyone whose work depends on this task?

• Too many Rs: Activity needs more analysis and may have to broken into smaller tasks.
• No Rs: Is this task worth pursuing? Who will do this task?
• More than 1 A: Who is taking the ultimate decision.
• No As: There must me an A.
• Too many Cs and Is: Do we need to consult and inform each one of them?

• Too many Rs: Do we need to assign more people to reduce his/her workload?
• Too many As: Do we need others to take few more decisions? Is there lack of delegation in the team?
• No blanks: Does this person/role have to be involved in all the activities?
• No As or Rs: Do we need this person in the team?

1. Identify the roles and responsibilities
2. Get the commitment of the team for tasks/activities.

A lot of people have asked me how should they start their career as a Business Analyst. To answer I always end up saying it is a long process. It is not as simple as some of the other areas of work where you attend a few trainings, get certified and you are there on the job. To become a professional Business Analysis will take its own time. You will have to work, learn and practice the skills. I am writing this post keeping it generic and not focusing on any particular skills.



How to start and grow as a Business Analyst?

• Shadow a Business Analyst: It is a important that you learn from someone who is already working in the area where you wish to grow. Shadowing a Business Analyst is a great technique for a budding BA to learn. If possible always prefer to shadow an experienced BA over a new one. While shadowing take note of the tasks that the BA is performing.
  TIP: Make sure to spend extra time with the BA to clarify your queries. I have found that lunch time, coffee break, travel time works out to be the best time for such discussions. If there is time available with the BA ask him to mentor you.
• Perform Business Analysis in your current project: There is no better place to start your Business Analysis career than the project you are currently part of. Seek guidance from the Business Analysts in your project and ask if you can move into their team. Taking up peripheral tasks to start with, the idea is to get into the team. This will give you unlimited time to shadow, learn and get coached from the experienced Business Analysts. It will always be easier for you to move into a different role in your current project than to get into a completely new project as a fresh Business Analyst. Since BAs are closer to the customer, I doubt any team will take a risk of hiring a completely fresh BA for the job. On the other hand if you move into the BA role in your current team they may accommodate you and shield you from the tougher responsibilities.
  TIP: Remember to soak as much as you can from this experience as it is going to define what kind of BA you will turn out to be in future.
• Start as a junior BA in a new project: Once you have gained enough experience make sure you get to work in a completely new project. As we have discussed earlier in this blog that the role a BA changes with time in a project. Hence it is important that you get to work in different stages of a project. At the start of a project the senior BAs are responsible for a lot of important tasks. The good thing for you, a fresh BA, is that they are always looking for junior BAs to do some of the not so critical tasks or perform some critical tasks under their guidance. That I believe is a golden opportunity for a fresh BA. Make sure you spend a lot of time understanding the client, the tasks and also get on the job mentoring from the senior BA. In my personal experience this is the most difficult stage a BA's career. There is always a doubt and apprehension if s/he belongs there.
  TIP: Make sure you don't give up and keep seeking guidance from your seniors.
• Take up another project as a Business Analyst: Now that you have learnt a few things about the profession and have already been part of a couple of assignments. Ensure that you test yourself once again in a fresh project. Use all your experience from the earlier assignments and reflect where you need to improve. Make sure that you are not repeating your mistakes and improving your weaker areas. Seek guidance from your seniors in the areas where you feel you are lacking.
  TIP: This is the time where you should challenge yourself. Seek more responsibilities from your seniors. Ask them for bit of freedom to test your ideas. Make sure you put in extra efforts to ensure that you deliver.
• Mentor the new BAs as you move into the role of a Senior Business Analyst: It is responsibility if each senior BA that they mentor or guide the young ones who are striving to make a career in our area of profession. It is important that you impart knowledge which you have gathered over the years of working in this profession. Once you were mentored by your seniors and it is time to pass on that knowledge to your juniors.
  TIP: Imparting knowledge will always enhance your own knowledge.

Business Analysis as a profession demands proficiency in multiple skills. In a nutshell, it is a role of liaisoning with the clients and making sure that software being developed meets their requirements. It is not the role that develops the software or even designs it. It is not the role that defines what is to be developed but merely a role that bridges the gap between the client and the technical IT team capable of developing the software product. Though I over simplified the role in the last statement, let me assure you it is a complex role that changes very frequently in the lifetime of an IT project. Right from the time you produce the Business Case for the project to the UAT (User Acceptance Testing) and user training, BA has to perform a variety of tasks. The skills needed at each stage of an IT project varies greatly.



In an attempt to simplify the skills that a BA needs to possess I have put together a figure that might be helpful for those who wants to become a Business Analyst or are currently practicing professionals and want to grow in this field. I personally find this figure extremely helpful and I have been using it for a while both for mapping personal skills set and identifying areas to grow in and also to fill the gaps in BA teams I have been part of on various assignments.

As you can notice there are 3 core skills that converge to create the ideal Business Analyst. There are 3 areas that you need to grow in as a Business Analyst. As you spend more and more time in this profession you will realize that you can select any of the 3 paths and grow in them as well. If you focus on building your domain skills you can become an SME (Subject Matter Expert) in your domain. Similarly, if your interest lies in IT and technology side, you can grow into the role of an Architect. If you are good in communication and build on your skills you can become a facilitator.

This also means that a number of people from various fields can become Business Analyst. If you are strong in any of the core skills work on building the other skills and you can become a Business Analyst.

The immediate next steps for you are to analyze which skills you already possess and which skills you need to work on. Once identified the area of improvement start building your skills in that area. So which pie are you working on today?

The Business Analyst
Tarun Chandel

"It is the long history of humankind (and animal kind, too) those who learned to collaborate and improvise most effectively have prevailed." - Charles Darwin

Recently I saw Erin Brockovich for the nth times (yes I can't remember how many times I have seen Erin Brockovich). It is needless to say that it is a great movie but at the same time it teaches you so much about how to go about your work. How can we Business Analysts learn from Erin Brockovich and perform our tasks better:

• When you get a business case or a business problem investigate a bit further, just like erin did. 
• Talk to people, visit them understand their problem. 
• If the business is new for you talk to the subject matter experts no matter from where you get hold of them. Talk to them try to understand the business and the industry. 
• Get involved in the project and keep the positive energy flowing. Be available for others to come and communicate with you. 
• Always be aligned to the client, even when you are talking about their costs. 
• Always take time out to build relationships with the client, it pays a lot. 
• There will be resistance from some people in the client take that in your stride. 
• Continue doing your good work and the resistance will melt away. 
• Take good care of your loved ones, take time out for them as they are the ones who are going to keep your lifeline going on. You don't want to lose them.

As Business Analysts we face some very hectic days, especially at the start of the projects. All of us have seen days when we keep running in and out of Requirement Gathering workshops and meetings with the stakeholders. These workshops and meetings generally last the whole day and the routine continues for days.In midst of all these meetings the Business Analyst is supposed to make sense of the business problems and keep working on the deliverables as well. There are so many things going on that it becomes difficult to stay on top of your work.

Here are some tools that I have been using, it works really well for me. I hope it helps you.

• Get Offline and maintain a personal notebook to record all the project related info: Yes it is very important that you get off your laptop. Your laptop is your workstation and it believe it will distract you with so many things like mails, pings from other people, your use cases and other documents and deliverables. It is important that you move away from your laptop to organize your work. Invest in a personal notebook to maintain all the project related information.
  

• Keep calendar marked for important dates and tasks: As there are tonnes of things going around in the project you need to stay on top of the so many different dates. When is the next workshop, whne is the next meeting with the stakeholder, when is the deliverable due dats, when is the date to respond to all the queries, when is your boss visiting you, when is the meeting with the tech team .... Yes the dates will drive you crazy. We do use Outlook for organizing our meetings but it is also very important that we keep an offline record in our notebook. So that we can plan our work accordingly.
  
• Tip: Paste prints of monthly and yearly views of the calendars
• Tip: Color code the meetings.
• Keep all the important numbers handy: We meet so many new people in a project and you never know who you might need at what stage of your project. Though we all have a phone and you have their number in it but it is difficult to remember all the name (yes it is not easy for me) and unless we have a phone with great search tool (my phone doesn't have it) it is better to have the list of number ready to use.
  
• Tip: Take a printout and paste the list at the start of the notebook.
• Divide the notebook into sections: Divide the notebook logical sections. This will help you to find the appropriate information quickly. Also it helps you to better organize the information.
• Spend half an hour at the start of everyday to plan your day: This is the most important activity. When you start our day by going through the notebook you get a quick snapshot of the current status of the project. You should start your day with looking at the upcoming important dates and tasks for the day. It will help you to plan your day and keep tab on the day's activities.
  
• Spend half and hour at the end of the day to fill the gaps and updating the work book: End your day with updating the notebook with the learnings of meetings and workshops you attended during the day. You must do this exercise without postponing it to the next day. It doesn't take more than half an hour to complete this activity but it will help you to stay on top of your work.
  
• Carry the book to every meeting and keep taking notes: Do carry this notebook to every meeting you attend and make small notes. This will help you to sync up at the end of the day. Believe me when you are attending more than one meeting everyday it takes a lot out of you and it becomes difficult to remember each and everything. These notes will help you to retain pointers to important decisions or discussions you had in the meeting.
  
• Over the time it will become the most important BA tool: If you maintain the notebook properly it will become the most important BA tool as it is going to help you to do you Business Analysis tasks better.
  

Points to remember:
Not easy to do, there is a learning curve.
Tip: Keep doing it religiously for a month and it will definitely help you to stay on top of your work.

Alrite it's been a really long time that I have posted anything here. Blame me, curse me but please excuse me for the long absence. I promise I will make up for the lost time in coming months.

I was recently reading a book from the Dalai Lama the leader in exile of Tibet and a quote just got stuck in my head. I modified the quote to make it relevant to the Business Analysis Blog (the embolden words are my modification).

We must ultimately develop more than mere academic knowledge of the Business Analysis. We must integrate the truths of the Business Analysis teaching into the depths of our very being, so that they become reflected in our lives.

Collaboration is of little value if it remains an idea. It must become our attitude towards others, reflected in all our thoughts and actions.

- Modified version of The Dalai Lama's Golden words, taken from his book An Open Heart

Matt was recently looking for a job shift. Matt is a Business Analyst and is open to relocate to any place given that the work he gets should be good and in the profile of a Business Analyst. When Matt started his search on internet job portals he stumbled upon a lot of job openings for Business Analysts. He soon realized that BAs are required almost all over the world be it USA, UK, Rest of Europe, South Africa, Australia, India, Singapore or New Zealand (place he always wanted to visit).

Here are some of the Business Analysis Job Ads that Matt found:

1. Where is the customer and
2. Where is the development team?

1. Lead working sessions with client to capture product requirements and translate those requirements into structured Product Definition Documents.
2. Developing process flows from high-level concepts.
3. Ask the right questions at sufficient detail in order to capture the essence of the product requirements.

1. Liaise with technology team to provide constant business understanding and support.
2. Serve as a client representative in briefings, meetings, and conferences.

1. Liaise with offshore and onshore teams to provide constant business understanding and support and keep both the team on the same page.

1. Experience in Solution Design, Business Analyst (BA), Architecture, Consulting
2. Ability to lead working sessions with client to capture product requirements and translate those requirements into structured Product Definition Documents

1. Demonstrates strong interpersonal skills, with the members of the Development Team.

1. Excellent Communication and Inter-personal Skills.

What are Storyboards?
Storyboards are graphic organizers such as a series of illustrations or images displayed in sequence for the purpose of previsualizing a motion graphic or interactive media sequence, including website interactivity. [Wikipedia]

How Storyboards are used by the Moviemakers and Business Analysts?

Movie makers use the storyboards to illustrate the story better. They break the story into scene and then they work on the details of one scene at a time. It is not necessary that they do the storyboarding of each and every scene. Sometime movie makers do the storyboarding of only few important scenes. In the software industry we learn from a variety of fields and storybording is something that we have picked up from movie makers. As a Business Analyst we try to see the bigger picture of the business problems of the client. To get it right storyboards help a lot.  Just like movie makers we break the bigger picture of Business into smaller sections and then focus on one section at a time. This way we enrich our knowledge of client's business piece by piece, section by section. We can easily identify where we need to more research, where we need more analysis. Storyboarding not only helps BA in creating a bigger picture but a High Definition bigger picture where you can zoom to finer details.

Uses and Benefits of using Storyboards:

1. Helps a BA in identifying the areas where more information is needed.
   
2. Helps a BA in identifying the areas where more analysis is needed.
   
3. View the bigger picture (in High Definition)
   
4. Easy to communicate the understanding to clients
   
5. Helps in organizing the work.

Storyboards help a Business Analyst in creating a High Definition Bigger Picture of client's business.

1. In the Enterprise Analysis Phase, for creating the Business Case.
2. In the Requirement Elicitation Phase just before the Prototype is created.

Creating a Storyboard on a brown paper wall with help of Storycards and Post-its helps in identifying the right sections to focus on. I use legend post-its (notice pink one) to identify sections where I need to do more analysis (dark pink) and where I need input from the client (light pink). Also I keep myself reminding about the Horizontal Analysis and Vertical Analysis.

1. Keep it simple: Keep the story simple, do not make it complicated. 
   
2. Break the story into scenes: Breaking the story into scenes or sections will help you to organize the story better. It will also help you in identifying the shortcomings, if any, in the story. While making a Storyboad, do the Horizontal and Vertical analysis of storyboard, that will ensure completeness of the story.
   
3. Make it collaborative: The idea behind storyboarding is to make the complete picture clear. To make sure that you have covered every aspect of the story, involve your clients in the storyboarding session. Check the logic flow (“necessary and sufficient” arguments)
4. Tell a good story: In the end keep in mind to tell a good story.
   

Business Analyst is the person who interacts directly with the client. Business Analyst is the face of implementation team for the client. As Business Analysta we have to communicate a lot with our client, it's important to keep in mind that we represent the whole team and the whole organization (especially in the current scenario of outsourcing). All our actions will make a difference in the manner client perceives our team or our company. It's the responsibility of a Business Analyst to build the confidence of client in himself and that in process will build the client's confidence in our team and in our organization.

Tarun Chandel
The Business Analyst

One of the tools that I have recently started using for carrying out my work as a Business Analyst is Mindmaps. It is a simple yet very effective way of organizing your thoughts. I personally find it very useful during the brainstorming sessions. During the brainstorming stage a Business Analyst has tons of ideas flying all around. Mindmaps allow a BA to clearly organize these ideas.

It is not necessary to use a Mindmap software to draw the mindmaps, we can simply use a notepad and a pencil. I personally tend to use the brown paper and stickies to make the mindmaps during the brainstorming session and after the session is over, I quickly make a soft copy of the final map using the software.

As a Business Analyst we should always keep ouurself updated with the future plans of our client. If the client is planning to change their strategies for future where can we fit in?

If we don't it may happen that one day we will wake up and project will be over as the client decided to move on to something else. Remember the idea is to be a trusted partner with our client.

Also we should keep your eyes and ears open about the market state of your client. It should not happen that your client is going bankrupt and we are the last one to know about it. We want to make sure that our company has sent the invoice to the client before such calamity hits them.

Follow the KYC Policy (Know Your Customer Policy) it will lead to less surprises and much less shocks.

Tarun Chandel
The Business Analyst

A Business Analyst should focus on the customers of his client.

You got it; the idea is to get more business from the same client.

1. What are the numbers they (client) are interested in?
2. Who are their customers and what do they serve to them? It is important that you do your share of research. It will help you understand better how your solution is going to help your customer.
3. How are they better/worse than their competitors? It is important because in case their competitors start eating the market share it will hit you someday.
4. Who are the decision makers? It is important to know the organizational hierarchy of the customer and at the same time do a RACI mapping of it. That way you will know the exact role everyone plays in the organization. This will help you to target right people to build your bonds with.
5. How can you help them?

A Business Analyst acts as a face of Customer to the Development team, most of the time. A Business Analyst should be credible enough and the team should have absolute faith in him. Development team should be able to ask any question regarding the system and they should believe in the answers that BAs provide.  If they start having doubts on the answers BAs provide they may get tempted to develop something that is not needed by the business or spend extra time in clarifying the doubt from various sources.

The development team should trust a BA; this was the first lesson that I got from a senior BA. When I asked him how to do it, he told me that you have to figure that out for yourself there is no proven formula. Some of the things that I tried and how they helped me in building a good rapport with the development team. 

• Interact with the developers regularly and keep asking them if they have any doubts. The idea is not to overdo it as they may get a feeling that you are trying to judge their work. Keep it simple and just make sure that they know you are there if they need any clarifications in the requirements.
• Make sure you run the development team through the requirements before they start with the implementation. Do it on module-to-module basis, plan with the Project Managers and Team Leads. Make sure you keep these sessions as informal as possible and try to make them understand the business pain points rather than teaching them (as they may switch off).
• Encourage the team to approach you for any clarification in the requirements. When they approach you make sure you clarify their issues or get the issues raised to correct person, if you are not the right one.
• It is a good idea to explain the business side to the developers and also let them know about the domain, as you have that knowledge. Have these talks at non-work timings like lunch, coffee or while traveling. Make sure you don't come out as a person who is bragging about his knowledge but as a person who is genuinely helping. Keep it honest; if you are not comfortable don't try it.

Stephan (name changed), a Business Analyst, was handling a small project. It was in very initial stage and he was interviewing the stakeholders, trying to understand the business problem. Somehow he was not able to link the problems, stakeholders were narrating, to their business. After a lot of interviews he realized that they were trying to automate a very small portion of a complex process. He prodded further and realized that this would solve their problem for just a department and overall time taken to complete the process may not shorten, it may even elongate as the other department will suddenly be dealing with high work volumes. He shared his findings with one of the board member of the client; he had become friend with while interviewing. Board member realized that they have to automate the overall process and not in bits and pieces. Stephen shared his calculations that if they automate the process across the departments then only the delivery time to client's customers will reduce else it will hardly make any difference. Stephen was asked to study the processes across the department and come up with a plan. Stephen studied the overall processes and mailed his findings back to his sales team, realizing that this project can be 10 times of the existing one. One month later Stephen's employer got a project that was more than 10 times of the existing project. Stephen later on got two more projects from the same client.

As the business is getting more and more dynamic, the requirement changes with every passing day. In such a dynamic scenario the role of a Business Analyst is becoming more and more important. With more and more IT solution providers in the market the role of a Business Analyst has evolved from being a mere requirement gathering person to a business ambassador of the IT Solution provider. BA has to use a lot of his soft skills, negotiation skills and social skills to build relations with the stakeholders on the customer side. Strong relations only will not help you to get more business from the customer but it will help you to understand what the customer needs and also what the customers of your customers need. Once you have understood the business needs of your customer, you should map out clearly where you can provide a solution that will help your customer to satisfy his customer better. Remember only having strong relations will not help unless you can provide solution that help them grow.

As a Business Analyst you should focus strongly on:

1. Building strong relations with the stakeholders
2. Build a strong understanding of the business of your customers
3. Learn about the customer of your customers
4. Keep mapping how your solutions will help your customer to satisfy their customers.

A Business Analyst (BA) works with different clients, clients from different cultures and in today's world clients from different geographies. It is imperative that a BA is comfortable working with people of various cultures.

I have faced differences in cultures on three levels:

1. Personal belief: Every individual is different and you need to treat them like that. The best way to handle such clients is not to judge them but accept them as they are, just like we do with friends in real life. In a way a BA needs to replicate a lot of things that he does in real life to the work environment.

2. Corporate culture: Evey organization has its own culture. The one that you will notice very early in your assignment is the hierarchy of the company and how employees treat their co-workers. In Capgemini we follow a very informal way of interacting and address everyone by their first name. But when you are working with your client, they may have a completely different way of addressing. One of my recent client had a culture of addressing people with their second names using appropriate salutation. Calling anyone by first name was considered disrespectful. Then there was another client where every senior was addressed as "sir" or "madam". I was lucky that my friend in the sales team informed me about this before I started my conversations with this client. Now I make it a point that I check this before I start working with any client. A small thing but it helps a lot in making the right connections.

3. Different geographies: This is the most natural difference. You can help yourself by reading about that particular geography. Though personally I have hardly found reading about cultures useful, but this does give you a lot of things to talk about at dinner, lunch or coffee. If you are thinking why it doesn't help to read about the cultures, as we discussed in the first point that every individual is different, so it is difficult to categorize people just by geographies. Try reading about your own culture on internet and you will realize you are hardly like what it states. So do not make perceptions about people depending on their geographies but reading will help you in having great and involved conversations :)

As a BA you should be able to adapt as quickly as possible to different people and places. If you are that kind of a person- great! However if you are not, you should work on yourself. This will help you in the long term and make you a better BA.

Tarun Chandel
The Business Analyst

The most exciting and yet difficult part of being a BA, is at the start of a project. Let me be more precise, the first time you meet the client. This is the time when client introduces their business and the problems that they want to solve with your help. This is also the time that, you introduce yourself and try to make a good impression on the client. What do you do to be at your best when you walk into that first meeting with the client? To start with, it always helps to do a bit of homework before the meeting.

As a Business Analyst you are involved in understanding the Business Requirements of your client and documenting them. It is essential for a Business Analyst to understand the requirements and for that it is necessary for a Business Analyst to understand the Business of the client. Hence it is imperative that you spend time on understanding the business of the client.

Steps to better understand the client before the first meeting:

• Talk to the people in the same account: Meet people in your organization who have worked with this client before.
• Search the Knowledge Base: Dig deeper into your organization's knowledge base.
• Use internet: If the client is new or there is lack of data, start searching on the internet.
• Past Communication: The most important is to read the communication that your organization has already had with the client. Go through the documents that have been exchanged, typically you will get some RFXs. These should give you a good ground to start your research.