Requirements elicitation is the process of identifying the sources of requirements for a new system and obtaining those requirements from those sources.
Requirements elicitation is a crucial part of the Requirements Analysis and Documentation Process. Requirements elicitation is a very challenging activity that requires focus and skill from the business analyst.
There are many requirements elicitation techniques that may be used in various situations depending on the level of requirements as well as the type of stakeholder.
Requirements Elicitation Techniques Include:
- Brainstorming: Brainstorming sessions are used to let the stakeholders come up with creative ideas or new approaches to a problem
- Workshops: Workshops are facilitated meetings with multiple stakeholders to draw out and document requirements.
- Interviewing: Interviews are in-person meetings where the business analyst asks questions to get information from the stakeholder.
- Surveys: Surveys are used to gather information anonymously from the stakeholders.
- Documentation Review: This is the process of obtaining requirements from written documentation such as manuals.
- Prototyping: This is the use of partially finished versions of the software that have been created to help validate requirements
- Focus Groups: Focus Groups are group interviews where the business analyst raises issues and questions to obtain information from the stakeholders.
- Observation: Observation is when the business analyst watches the users performing their daily tasks and asks questions about the tasks and work.
A good business analyst should have excellent skills in eliciting good requirements and using the right elicitation technique for each situation. If you are not familiar with some of these elicitation techniques, consider Business Analyst Training to build up your ability to excel on the job.
by Kingsley A. Tagbo