Cheryl LeeBusiness Analysis and Project Management Consultant and Instructor| Knowledge AdaptersThornhill, Ontario, Canada
The Business Analysis for Practitioners Guide has many techniques that a BA could have in their toolkit. What are 5 of the core techniques that you use to conduct business analysis? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The best source to understand that (in my opinion) is the book "Business Analysis Techniques: 72 Essential Tools For Success Author: James Cadle, Paul Turner, Debra Paul Publisher: British Informatics Society Ltd." It is not easy to talk about a tool because you will use a tool for each section on the practitioners guide. So, my recomendation is to use the tool that is best suited to work with your stakeholders. The communication with your stakeholders is what has to guide you when selecting the tool. For example, I have been working into initiatives where my stakeholders loved Use Cases and in fact, when I do not recomend that, they loved to create the Use Cases and validte it with me. Saving Changes...
Cheryl LeeBusiness Analysis and Project Management Consultant and Instructor| Knowledge AdaptersThornhill, Ontario, Canada
Great point that the technique has to be dependent on the situation and stakeholders that you are working with. There are a few though that probably keep popping up. Use cases are a great example of that. Probably one of the more commonly used modelling techniques, along with process models. Saving Changes...
Steven ZacharyDirector| Alberta Health ServicesCalgary, Alberta, Canada
This is so hard...only 5. I want to say "it depends" but that is a cop out. I use different techniques depending on the size of the project, the maturity of the organization, the project methodology...etc. My top 5 techniques are:
1) Listen (simple yet unbelievably undervalued)
2) Make it visual (I'm a visual model addict)
3) Focus on content not tools (your tool can be pretty, but make sure the content is correct).
4) Ask stupid questions (if you are new to a field, don't be afraid to ask anything...it's your job).
5) Most important; Trace back to the business value of your work. You should be able to describe at the atomic requirement level how it supports the anticipated business value. This goes hand in hand with;
6) Know your stakeholders; know the difference between an approver, a user, and the recipient of the business value. Saving Changes...
