DOS and DON’TS as BUSINESS ANALYST

Business Analyst plays an important role in every stage of the project lifecycle from requirement gathering to delivering the solution product to the client. Any mistake even if it is a smaller one also costs the successability of entire project. So, every business analyst must know the dos and don’ts for business analysts. Here we discuss below some of the important dos and don’ts for business analysts.

No space for ‘No’ word in BA role

Be nice with the stakeholders while interacting with them, lesson carefully until they finish their talks, and never say No to them even if you think their requirements are irrelevant or not suitable to the project, and don’t try to convince them with your words. Saying ‘No’ or interrupting them while talking creates a misconception and feeling of rudeness on the business analyst.  Hence, it is always better to approach SME and take his voice and convey the same to the stakeholders to make them understand

Ask questions

Most stakeholders often cannot state their requirements clearly in a normal discussion. Hence, The BA should not hesitate to ask anyone any questions that needed to be asked to get clarity. Moreover, asking the question is the only way to fill the gaps in our understanding and lead to the clarity of clients’ requirements.

While asking questions the BA should keep the below points in his mind

o   Don’t ask the complex questions

o   Frame the next question based on the answer of  the previous  one

o   Always remember to ask a kind of question, those answers should lead to the other issue.

Document everything

As a business analyst, it is very vital to document everything starting from the client’s requirements, progress, and any change that occurred during the project. Share these documents with stakeholders and take confirmation and get approval from the project manager. If BA having any emails confirmation or conversation, always keep the project manager in the loop. These documents and emails will be useful for future reference

Establish an effective communication system

Establishing effective communication with stakeholders is crucial for BA as he constantly interacts with stakeholders and the development team and he should hold meetings and conversations for the healthy progress of the project.

Work out in advance

As business analysts, he/ she must always be prepared with proper arrangements, especially in the case of meetings with stakeholders like meeting notes, a list of questions to be answered, and required documents. This could shorten the meeting time and save both stakeholders and BA time.

Don’t leave unclear requirements behind

Sometimes BA sets aside the unanswered implicit requirement and thinks they will discuss it later after some time.  This kind of attitude results in missing the crucial requirement and if these unclear requirement questions lead into change requests and risk at the middle of the project

Don’t make haste while gathering requirements

Give ample time to capture the requirement as project success is hugely depending on understanding the stakeholder’s requirement. So, don’t be rushed it may cost you in terms of effort, time, and cost.

Don’t come up with a common solution

The client needs are different from client to client. So don’t deal with the client’s problem with the same approach. Hence, see the client’s needs with a fresh look and choose the suitable approach based on the project to deliver the suitable solution.

Don’t hold any Cross swords with the client

Don’t make an argument with the client while discussing the requirement, this may create a negative perception of stakeholders on BA and as a result lack of cooperation of stakeholders during requirement gathering.

Don’t jump to the conclusion with our assumptions

Never put own assumptions and experience while drawing a solution concept. It can mislead and ruin the entire project.

Don’t go for gold leaf

Work out towards the actual solution and focus on the minimum viable product rather than go for a gold leaf by adding extra unnecessary features which consume delivery time and sometimes distract from the original concept.

Don’t go beyond purview of your role

Last but not least, a business analyst always remembers that their responsibility is to deliver the solution but not how to develop the solution that will be taken care of by the developing team. Additionally, it will distract you from your core activities