Explanation on elicitation techniques for BA

There are 11 elicitation techniques as BA we can use. Below we have mentioned all the elicitation techniques for your reference. We can use one or more elicitation as per the scenario. Brainstorming: it will be done individually or groups. We will collect the ideas from everyone and group them. Then we will create consolidated requirements by removing duplicate and then we will prioritise the requirements. Document analysis: If we have any user manuals, document available on current process and future developments, we can read and analyse the documents and note down our understandings. Then we can confirm with any of the SMEs and create requirements Reverse Engineering: If our current process does not have any BRD, SRS, FRS Etc, we will analyse the current process and create all these documents for future development. This elicitation technique should be applied for all projects Focus group: A focus group is a means to elicit ideas and attitudes about specific product, services or opportunity in an interactive group environment. The participants share their impressions, preferences and needs, guided by moderator. Observation: It is the process of shadowing the users and understand the current process. We have two types in this, active observation where BA will ask questions while observing and Passive observations where BA will not ask any questions and just not it down all observations and questions. Workshops: Workshops comprise 6 to 10 or more stakeholders. Working together to identify requirements. Workshops tend to be of a defined duration, rather than outcome may need to be briefly repeated in order to clarify or obtain further details. Here stakeholders and developers will collaboratively work for the application JAD Sessions: Joint Application development extended, facilitated workshop. It involves collaboration between stakeholders and system analyst to identify needs or requirements in concentrated and focused efforts Interviews: it is the process of asking relevant question to a person or group and documenting their response. Based on their responses we can create requirements. In interviews we have two types structured and unstructured interviews. In structure interviews will have set of questions and will conduct in formal. Where unstructured interviews will not have set of questions and informal. Prototyping: It is useful to get feedback from the client. We will show sample prototype, screen or mockups and get feedback on further improvement. It should be implemented at beginning stage of the project so that we can implement any changes requested by client and client also will have proper idea on product from beginning itself. Questionary/Survey: It is us full to get the limited system requirements from stakeholders when they are not available in person and they can be accessible only offline or via web. Also we need responces from many stakeholders where BA unable to get requirements from all. Will create some questions and give all the stakeholders and get their responces. Based on that we will understand the requirements. Use case Spec: Use Case Specifications in requirements elicitation are detailed, structured textual narratives that define how a user (an actor) interacts with a system to achieve a specific goal.