Business Requirements Elicitation Techniques
I have said this before, but I am going to say it again. There is no "right way" to do business analysis, but there are plenty of wrong ways to do it!
The reason I say there is no right way is because there are many different techniques, styles, types of documentation and types of diagrams to use to do your job.
I look at this as a good thing - it means I have options. I can determine what I believe is the best tools to use based on the type of project I'm working on.
For every tool you have at your disposal, you can either use it correctly or incorrectly with great results or bad (sometimes disastrous) results.
Getting business requirements from your stakeholders is the single most important thing you will do. Without those, you have nothing to document, nothing to create diagrams for.
This means that you MUST have various techniques at your disposal that you are comfortable using. If you use the same elicitation technique for every project - and only use one - you will find that you miss requirements and have gaps in your documentation and processes. Those gaps can lead to expensive fixes down the road!
You must be able to communicate with your stakeholders in the way that is best for them - not you. If it's difficult for them to communicate their needs, guess what happens. They don't.
Be sure you are considering the needs of your stakeholders when you are determining the type of techniques to use for requirements elicitation.
Want to learn more about how to be successful eliciting requirements? Watch this video on one of the elicitation techniques.