Define Elicitation Techniques and Collaboration

Elicitation Techniques—There are 11 types of Elicitation Technique. 1. Brainstorming—Brainstorming is a technique where we will be going to conduct a session to generate new, different ideas. It is a formal group activity where participants generate as many ideas and solutions as possible without judgment. It's focused on the creativity and idea generation. 2. Reverse engineering—Reverse engineering is the process of analyzing an existing system/product to understand how it works, especially when documentation is missing, incomplete, outdated, or unavailable. Types of Reverse Engineering 1. Black Box • The product/system is studied without examining its internal structure. • Focus is mainly on inputs, outputs, and visible behavior. • We do not know how the system works internally. 2. White Box • The internal working and structure of the product/system are studied. • The analyst examines the internal processes, logic, components, or code. 3. Focus Group—A focus group is a requirement-gathering technique in which a selected group of people discuss a product, system, process, or requirement with a facilitator/business analyst. Types of Focus Groups 1. Homogeneous Group • Participants have similar characteristics, knowledge, or backgrounds. • Example: A focus group consisting only of HR employees. 2. Heterogeneous Group • Participants have different backgrounds, knowledge, roles, or perspectives. • Example: HR employees, managers, IT employees, and employees participating together. 4. Observation—Observation is a requirement-gathering technique in which the business analyst observes users performing their actual work/process to understand the existing system. It helps the BA collect information by directly observing the individual, process, or system. Types of Observation 1. Passive Observation The business analyst observed the subject matter expert working through the business routine but did not ask the question. 2. Active Observation The business analyst observes the current process and takes the notes. When BA has a question, he will ask the question right away. 5. Interview—An interview is a requirement elicitation technique in which the business analyst communicates directly with stakeholders to collect information, opinions, feedback, and requirements. Types of Interviews 1. Structured Interview • Questions are pre-defined in advance. • The same or planned questions are asked to the stakeholder. • It follows a fixed structure. 2. Unstructured Interview • Questions are not strictly pre-defined. • The discussion is more flexible. • The BA can ask follow-up questions based on the stakeholder's answers. • Useful for exploring new ideas and discovering unexpected requirements. Open-Ended and Closed-Ended Questions Open-Ended Questions Open-ended questions allow the stakeholder to provide a detailed answer in their own words. Closed-Ended Questions Closed-ended questions generally require a short, specific, or limited answer. 6. Workshop—A workshop is a structured meeting in which stakeholders, the business analyst, and project team members come together to identify, analyze, discuss, and agree upon requirements. 7. Questionnaire technique—Questionnaire technique is one of the most important elicitation techniques whenever the BA needs some information or feedback from the large number of stakeholders. Sometimes it is not possible to gather some feedback. So in this technique, the business analyst is going to prepare the survey form or feedback form. It is a method of collection; it is a survey. There will be a predefined question, and we will conduct one survey to know the feedback from the customer. 8. JAD session—A joint application development session. It is like a structured workshop involving the stakeholder, business analyst, and developer to gather the requirements and make some decisions and to get the clarity of the requirements. If any confusion arises, we will be going to collaborate with the client and development team. They will remove the confusion. It is like a structured session with a predefined agenda. 9. Document analysis—Document analysis is identifying the project documentation path and folder, drive, or cloud or Confluence. It raises a request for access, and a request will be sent to admin, and admin will approve. It locates the latest or most recent document on the basis of the highest version number or latest date. It goes through the document and prepares the query log. And it also read the same document again and refined the queries, consulted SMEs, updated the query log, and created an understanding document. 10. Prototyping—Prototyping is a business analysis technique in which a sample or early version of a system, screen, or feature is created to help stakeholders visualize how the final system will work. Use Case Spec—A use case specification is a detailed document that describes how an actor interacts with a system to achieve a specific goal. Collaboration Collaboration means working with different stakeholders to ensure that requirements are correctly understood, agreed upon, and implemented. A BA collaborates with: Business Stakeholders → Understand business goals and requirements End Users → Understand user problems and expectations Project Manager → Discuss scope, timeline, budget, and risks Developers → Explain functional requirements and clarify doubts UI/UX Designers → Validate screens and user experience QA/Testers → Define acceptance criteria and validate requirements Product Owner → Prioritize requirements and manage the product backlog Management/Sponsors → Obtain approvals and make key decisions Elicitation Techniques—There are 11 types of Elicitation Technique. 1. Brainstorming—Brainstorming is a technique where we will be going to conduct a session to generate new, different ideas. It is a formal group activity where participants generate as many ideas and solutions as possible without judgment. It's focused on the creativity and idea generation. 2. Reverse engineering—Reverse engineering is the process of analyzing an existing system/product to understand how it works, especially when documentation is missing, incomplete, outdated, or unavailable. Types of Reverse Engineering 1. Black Box • The product/system is studied without examining its internal structure. • Focus is mainly on inputs, outputs, and visible behavior. • We do not know how the system works internally. 2. White Box • The internal working and structure of the product/system are studied. • The analyst examines the internal processes, logic, components, or code. 3. Focus Group—A focus group is a requirement-gathering technique in which a selected group of people discuss a product, system, process, or requirement with a facilitator/business analyst. Types of Focus Groups 1. Homogeneous Group • Participants have similar characteristics, knowledge, or backgrounds. • Example: A focus group consisting only of HR employees. 2. Heterogeneous Group • Participants have different backgrounds, knowledge, roles, or perspectives. • Example: HR employees, managers, IT employees, and employees participating together. 4. Observation—Observation is a requirement-gathering technique in which the business analyst observes users performing their actual work/process to understand the existing system. It helps the BA collect information by directly observing the individual, process, or system. Types of Observation 1. Passive Observation The business analyst observed the subject matter expert working through the business routine but did not ask the question. 2. Active Observation The business analyst observes the current process and takes the notes. When BA has a question, he will ask the question right away. 5. Interview—An interview is a requirement elicitation technique in which the business analyst communicates directly with stakeholders to collect information, opinions, feedback, and requirements. Types of Interviews 1. Structured Interview • Questions are pre-defined in advance. • The same or planned questions are asked to the stakeholder. • It follows a fixed structure. 2. Unstructured Interview • Questions are not strictly pre-defined. • The discussion is more flexible. • The BA can ask follow-up questions based on the stakeholder's answers. • Useful for exploring new ideas and discovering unexpected requirements. Open-Ended and Closed-Ended Questions Open-Ended Questions Open-ended questions allow the stakeholder to provide a detailed answer in their own words. Closed-Ended Questions Closed-ended questions generally require a short, specific, or limited answer. 6. Workshop—A workshop is a structured meeting in which stakeholders, the business analyst, and project team members come together to identify, analyze, discuss, and agree upon requirements. 7. Questionnaire technique—Questionnaire technique is one of the most important elicitation techniques whenever the BA needs some information or feedback from the large number of stakeholders. Sometimes it is not possible to gather some feedback. So in this technique, the business analyst is going to prepare the survey form or feedback form. It is a method of collection; it is a survey. There will be a predefined question, and we will conduct one survey to know the feedback from the customer. 8. JAD session—A joint application development session. It is like a structured workshop involving the stakeholder, business analyst, and developer to gather the requirements and make some decisions and to get the clarity of the requirements. If any confusion arises, we will be going to collaborate with the client and development team. They will remove the confusion. It is like a structured session with a predefined agenda. 9. Document analysis—Document analysis is identifying the project documentation path and folder, drive, or cloud or Confluence. It raises a request for access, and a request will be sent to admin, and admin will approve. It locates the latest or most recent document on the basis of the highest version number or latest date. It goes through the document and prepares the query log. And it also read the same document again and refined the queries, consulted SMEs, updated the query log, and created an understanding document. 10. Prototyping—Prototyping is a business analysis technique in which a sample or early version of a system, screen, or feature is created to help stakeholders visualize how the final system will work. Use Case Spec—A use case specification is a detailed document that describes how an actor interacts with a system to achieve a specific goal. Collaboration Collaboration means working with different stakeholders to ensure that requirements are correctly understood, agreed upon, and implemented. A BA collaborates with: Business Stakeholders → Understand business goals and requirements End Users → Understand user problems and expectations Project Manager → Discuss scope, timeline, budget, and risks Developers → Explain functional requirements and clarify doubts UI/UX Designers → Validate screens and user experience QA/Testers → Define acceptance criteria and validate requirements Product Owner → Prioritize requirements and manage the product backlog Management → Obtain approvals and make key decisions