Author Topic: Elicitation Techniques in Business Analysis  (Read 13362 times)

1190761312

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Elicitation Techniques in Business Analysis
« Reply #75 on: October 05, 2021, 08:07:53 pm »
Requirements are the key foundation for a business analyst and knowing elicitation techniques are key feature of BA to start a project. Some of the elicitation techniques are as follows.
1. Document Analysis
2. Reverse Engineering
3. Brainstorming
4. Prototyping
5. Focus Groups
6. Observations
7. Workshops
8. Interviews
9. Questionare
10. JAD

12105103006

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Elicitation Techniques in Business Analysis
« Reply #76 on: October 15, 2021, 12:42:18 pm »
Gathering the requirements that must be accounted for in order to achieve a project's goal is the process that forms the foundation for its success. The BA typically has responsibility for managing this phase. Requirements elicitation is the set of activities where information is given by stakeholders, users, and customers to be applied to the design of the initiative or the solution.

Elicitation Techniques in Business Analysis:

Various elicitation techniques provided by business analyst are:
?   Brainstorming
?   Document Analysis
?   Focus Groups
?   JAD
?   Interface Analysis
?   Interviews
?   Observation
?   Prototyping
?   Requirements Workshops
?   Reverse Engineering

12131122607

  • Global Moderator
  • Newbie
  • *****
  • Posts: 12
Re: Elicitation Techniques in Business Analysis
« Reply #77 on: October 20, 2021, 12:56:41 pm »
Elicitation techniques are used to get most of the information about requirements from stakeholders, subject matter experts (SME).
Various elicitation techniques
*Brainstorming : Brainstorming works by focusing on a topic or problem, and then coming up with many radical solutions to it. This technique is best applied in a group as it draws on the experience and creativity of all members of the group

*Document Analysis : Document analysis is technique of gathering information from the documents of existing system.

*Focus Groups : It includes participant of same interest from the specific product/service. The idea is to make participant share, interact and describe the need.

*Interviews : It is the one to one interaction with the User/stakeholder to understand their actual requirement or expectation.

*Observation : It includes observing the user while doing their job. It helps to understand the existing processes.

*Prototyping : Prototyping is Visual presentation of Idea or requirement which gives clear picture of requirements. Visual Presentation are given terms Mock-up screens or graphical designed or requirement prototype.

*Workshops : workshop includes bringing user and stake holder to gather and have a conversation in more innovative tasks for example:collaborative games, tasks.

*Survey/Questionnaire : Useful for obtaining Limited system requirements from users or stakeholders who have a minor input  or are geographically remote.

*Reverse engineering : If an existing system has outdated documentation, it can be reverse engineered to understand what the system does. This is an elicitation technique that can extract implemented requirements from the system.

*JAD(Joint application development) : Joint Application Development (JAD) technique is an extended session to the workshop. In the JAD session stakeholders and project team works together to identify the requirements. These sessions allow the business team to gather and consolidate large amounts of information. The JAD team includes business process owners, client representatives, users or stakeholders, business analysts, project managers, IT experts (developers, quality assurance, designers, and security).