elicitation Techniques

Requirements elicitation technique is one of the most important responsibilities for business analyst to understand what the stakeholder really needs from that particular project. This process is called elicitation techniques. It is the first step in project that meets business goal and user expectation. Elicitation is not just about asking questions to stakeholder or clients it is about clarifying needs, resolving conflicts and documenting requirements. Business analyst use different techniques based on the type of project, stakeholder and information required. there are 11 types of elicitation techniques they are Brainstorming sessions, Document analysis, focus groups, Observation, Workshops, Reverse engineering, JAD sessions, Interviews, Questionnaires/Surveys, Prototyping, Use case specs. Some of the most common;y used techniques are 1. Brainstorming Brainstorming sessions are discussions where stakeholders freely share ideas with Business analyst. This is helpful in the early stages when requirements are not clear, or when innovative solutions are needed. Brainstorming with employees might generate new features for improving customer service. 2. Focus Groups Focus groups are the sessions were conducted with small group of selected stakeholders, they share opinions, expectations, and experiences. For example, gathering a group of employees from different departments to discuss what features they want for that project. 3. Observation Sometimes stakeholders cannot explain their processes clearly. At that time the business analyst observes how they perform their daily tasks. There are two types: Active observation and passive observation were in active BA participates in the process and were in passive BA silently observe the process. 4. Interviews Interviews are were one-on-one discussions with stakeholders. The business analyst asks open ended and closed ended questions to gather information about the process, problems and there expectations for that project. this is one of the most direct ways to understand what stakeholder wants. 5. Questionnaires/Surveys When there are too many stakeholders to interview individually, a questionnaire is a good option. The business analyst prepares the set of questions which can be multiple choices or rating scale. This methods fast the process when there are more number of stakeholders. 6.Document Analysis Existing documents such as process manuals, reports, or policy documents can provide valuable information. Document analysis useful when the stakeholder is not available or business analyst want to cross check complete details of that project. 7.Prototyping Prototyping involves creating a simple mock-up like screens and pages which will be shown for stakeholders. This helps stakeholders to verify and give feedback. Sometimes users won't understand what they want until they see it. for example : showing a sample to stakeholder that how it's going to work. 8.Workshops Workshops makes multiple stakeholders come together to discuss and agree on requirements.They are useful when quick decisions are needed. business analyst should make sure that everyone should participate in the session. 9.Joint Application Development (JAD) JAD sessions bring business users and developers together in a structured workshop. the main goal of this JAD session is to finalize requirements quickly with everyones input and the decisions are documented immediately. 10. Reverse engineering Reverse engineering is the process of analyzing an existing system or application, to understand how it works and documenting the requirements and design. business analyst needs to understand how the existing system supports the business process. the organizations can replace or upgrade the existing system. 11. Use case specification A use case specification tells that how a user interacts with a system to achieve a goal. It is part of requirements documentation that explains step by step what the system should do in different situations.