Well, we all agree that Business Analysis is an ongoing process and it demands improvement and innovation. Here I would like to list a few common mistakes and ways to avoid those.
1. Never assume any requirement: If you have any doubts on requirements, keep questions ready or write it as business analysis assumptions and highlight it in your document. Review it thoroughly with your stake holders as early as possible.
2.Jumping into ‘how to do’ instead of what they want. Never ever jump into functional requirements before you capture the business requirements. It is one big mistake which does not give you an option to be flexible later. Do it the agile way.
3. Get feedback. Get feedback about the requirements from your stakeholders. I always prefer keeping in loop my Product Managers (who have expertise in the product), the Testing team (so that they know the requirements are testable) and the Development team (so that you know the requirements are feasible). Always remember – incorrect requirements are worse than incomplete requirements.
4. Difficulty in dealing with some stakeholders. I used to do this mistake often – when I see a difficulty in dealing with a stake holder, I used to just ignore them; but now I know the best way to deal with them is to have a one-on-one meeting as soon as possible.
5. Ask more questions. A good trait of a smart BA – A smart BA doesn’t look bad when he asks a dumb question. He makes that dumb question smart. Interviewing a stakeholder and getting enough data is a must for any BA role.
6. Requirements trace-ability– The ability to trace business requirements into test cases and to propagate these into functional requirements and development tasks is very important. Never miss that. A good process makes a smart BA. If there are any changes in the requirement, the BA can easily tell which test cases will be impacted based on his analysis. That makes everyone’s life easy.
I will be glad to hear about your experiences, mistakes and ways to avoid those mistakes.