If the business analyst role is to gather the requirements, then that would NOT be a difficult job! In fact anyone can get requirements by taking orders. In practice there are many ways that the BA can go and gather the requirements from the stakeholders such as:
- Asking the stakeholders to give them the requirements either in interview or workshop sessions.
- They can read the existing information about the project, such as a business case or charter and gather the requirements from those documents.
- Or they can go out and observe the organization to gather the requirements.
The BA’s real role is to create the requirements and not to get or gather the requirements. The BA should be in the business of getting information that is used to generate requirements. The information they collect has to be analyzed and from that analysis they will produce requirements. When the BA gets requirements from the customers or stakeholder, they are making the assumption that the customer or stakeholder knows what is needed to solve the problem or achieve the desired business objective, but this may not be the case.
Here are some steps that a junior BA should follow in generating requirements
- The information they need will be about the problem or the needs of the stakeholders.
- In order to gather information to create requirements, the BA has to ask the right people the right questions.
- The BA need to know what questions they should ask and who they should ask to get the right information.
- The BA needs to determine which stakeholder(s) to get involved with the project.
- The BA must develop an information gathering plan.
- The BA must go out and collect the information.
- The BA must create models to analyze the information and derive the requirements.
The BA’s role is not to gather requirements, but it is to go get the right information and then create the requirements.