What are elicitation techniques ? Why do we need different elicitation techniques and what are they

Requirement elicitation techniques are methods used to gather information about the requirements of a project or product from stakeholders such as customers, end-users, project sponsors, and subject matter experts. The purpose of these techniques is to ensure that the requirements are well defined, complete, and accurately reflect the needs of the stakeholders. Some common requirement elicitation techniques include:

1. Interviews: One-on-one or group interviews with stakeholders to gather information about their needs and requirements. It will be classified as Structured interview and Un structured Interview. In Unstructured one the questions are fixed while in other type there are no fixed questions. It depends upon the answers of the stakeholder and it will get continued according to the requirement.
2. Focus groups: Bringing stakeholders together to discuss requirements and gather information in a collaborative setting.
3. Surveys: Distributing questionnaires to stakeholders to gather information about their requirements.
4. Prototyping: Creating a working model of the product to help stakeholders understand and provide feedback on the requirements.
5. Observation: Observing stakeholders using similar products or performing similar tasks to gather information about their requirements. It will be of 2 types. Passive observation and active observation. In passive observation the BA will just observe the work style of the stakeholder and will not interrupt him. The whole operation will be allowed to happen and then the question will be asked. In Active observation BA will interrupt the work and will ask question at the same time when operation is being performed to get the clarity.
6. Workshops: Bringing stakeholders together to brainstorm and define requirements in a collaborative setting.
7. Brainstorming: Encouraging stakeholders to generate ideas and requirements through open discussion and idea generation.
8. Document analysis: Reviewing existing documents, such as contracts, specifications, and standards, to gather information about requirements.

These techniques help ensure that the requirements for a project or product are well understood and accurately reflect the needs of stakeholders, thereby reducing the likelihood of misunderstandings or changes during the development process.

Different requirements elicitation techniques are used for various reasons and in different situations. Some reasons for using different techniques include:

1. To reach a diverse set of stakeholders: Different techniques may be used to reach stakeholders who have different perspectives, levels of involvement, or expertise. For example, interviews might be used to gather in-depth information from subject matter experts, while surveys may be used to gather information from a larger number of stakeholders.
2. To address different types of requirements: Different techniques may be used to gather different types of requirements. For example, observation or prototyping might be used to gather information about functional requirements, while workshops might be used to gather information about non-functional requirements such as usability or performance.
3. To accommodate different communication styles: Different techniques may be used to accommodate the different communication styles and preferences of stakeholders. For example, some stakeholders may prefer to provide requirements through writing, while others may prefer to provide requirements through oral communication or collaboration.
4. To increase stakeholder engagement and participation: Different techniques may be used to increase stakeholder engagement and participation in the requirements elicitation process. For example, focus groups or workshops might be used to engage stakeholders in a collaborative environment and encourage them to provide requirements.
5. To address constraints and limitations: Different techniques may be used to address constraints and limitations in the requirements elicitation process. For example, remote stakeholders might be engaged through phone interviews or surveys, while time constraints might require the use of more efficient techniques such as surveys or document analysis.

Having a variety of requirements elicitation techniques at hand allows project teams to choose the most appropriate technique for each situation and to gather requirements in a way that is most effective for each stakeholder and the project as a whole.