Business analysis covers a wide range of tasks. In any organization where these tasks are not well understood, sponsors and stakeholders don’t perceive, recognize, accept, and realize all the work that goes into creating a requirements document.
Many techniques are used by business analysts (BAs) during the elicitation process for on-going project. Here is an example: let’s say, as a BA, you are working on a new healthcare software application project. The choice of the best techniques is critical for the following:
- Assessing the goals of the project
- Gathering the requirements
- Making sure the finished product answers customers’ needs and fill any gap on the market
- Creating and delivering a good requirements document to sponsors, stakeholders, and the development team.
The following steps can be followed during the elicitation process:
- Planning the work
- Elicitation of the requirements
- Analysis of the requirements
- Communication of the elicitation result to sponsors and stakeholders.
The approval of the elicitation results and the prioritization of the requirements can be hard to achieve in organizations that lack a good understanding of the function and role of business analysis. So based on my experience, the following techniques can help:
- Diagrams (e.g., BPMN, DMN, UML)
- Prototypes (e.g., mockup, wireframe).
These techniques will help you achieve your elicitation’s goal in most circumstances. They also help stakeholders, sponsors, and the development team understand how requirement changes will impact the project in the long run.
