I want to talk about Dos and Don’ts of Business Analyst. As Business Analyst is the person who speaks with client, he/she should know Do and Don’ts. This is part of Business Analyst Role and Responsibilities.
Let us observe here some of important Dos and Don’ts for Business Analyst..
1. Never say No to client.
When client is explaining his problem or giving requirements, listen carefully and try to understand what he/ she is trying to explain, and never say “No” to client affront, because here client is explaining his problem and he expects some solution from us.
So rather than say “No” we can provide alternate solution after speaking and discussing with our internal teams.
2. Never imagine anything in terms of GUI
Never imagine the requirements by seeing graphical representation ask right questions to client and get clarity on the requirements.
Login page may same for most of the websites but functionality is different.
For example: If you want to login to any website we need to enter correct user id and password to login the page. Here user id and password is common, but password length and validations differ from website to website based on the client requirement.
Example: Password should be 10 characters and it should have at least 1 capital letter and 1 special character.
3. Question Everything
Never feel bad to ask questions, ask the right questions and get clarity from the client. You can ask the questions till you get clarity. Sometimes client may not tell the complete requirement unless you ask the questions.
Example : Client will say I need login page. But here you need to ask multiple questions to client to get clarity. Let us see some sample questions here.
- What are the validations required,
- Terms and conditions are required or not.
- And when this button should be disabled or enabled.
- Which type of error message should be shown on the screen if user enters wrong password or user id.
- Password length should be how much and all.
4. Consult an SME for clarifications in Requirements
If requirement is not clear and you need more clarity on the requirement, then we can discuss with SME (Subject Matter Expert). And ensure to document the requirements what you discussed with SME and get approval from solution owner. And explain to him what you understand by discussing with the SME.
5. Every problem of client is unique.
Every problem of Client is unique, so talk to the client with a open mind with no assumptions from your previous experience.
Never come to any conclusion before listening or understanding all the aspect of requirement from client, if you have a slight amount of doubt about any demand or change it’s always preferable to clear it with the client, subject matter expert, or with your team member.
6. Do not interrupt the client, when he/she is giving you the problem.
Listen very carefully and completely to the client as well as to the end user and then ask question, don’t interrupt them in between.
7.Maximum try to extract the leads to solution from the client itself.
8.Never try to give solutions to client straight away with your previous experience and assumptions.
9. Should not be hurry.
Should not gather the requirements in hurry, conduct a meeting in a convenient time and take your own time to understand the requirement or gather the requirements. Because if you are in a hurry to capture the requirement then there is a chance to misunderstand the requirement, it may lead to project failure. As a Business Analyst you should be have open mind when you are gathering requirements.
10. BA should focus on “what” and “when” to develop rather than focus on “how” to develop.
As a Business Analyst our responsibility is to understand what to deliver and when to deliver the project, how to develop is the responsibility of development team or development manager. We need not to concentrate on this part and need not to worry. Always have a prior discussion with your project manager and sponsor before conducting a meeting.
11. Should not miss any requirement
Make sure that you have gathered all the requirements from the stakeholder for your project, missing out any information can results to unwanted redo the work as well as delay projects and increase cost.
12. Should know what the Scope of the Project is.
Sometimes non functional requirements of client are not feasible because of budget or time constraint, so it’s always better to liaison with your PM to find out what is out of scope so that all will be in the same page and avoid misunderstanding.