Elicitation is the art of drawing out requirements. The "123 Tools" resource emphasizes that there is no "one size fits all" approach; the technique must match the stakeholder profile.
1. Brainstorming Often undervalued due to its simplicity, structured brainstorming is essential for generating a large volume of ideas quickly. It requires a facilitator, a clear objective, and a method of categorization to be effective.
2. Interviews One-on-one interviews remain the gold standard for detailed information gathering.
3. Observation (Job Shadowing) In 2021, observation evolved to include digital surveillance of user workflows (via analytics) alongside traditional physical shadowing. It is critical for discovering tacit knowledge—things users do automatically but cannot articulate.
4. The Delphi Technique A consensus-building method used when stakeholders are in different locations or require anonymity to speak freely. Iterative rounds of questionnaires allow the group to converge on a solution without the pressure of groupthink. Elicitation is the art of drawing out requirements
Once information is gathered, it must be synthesized into a coherent structure. This section represents the technical core of the BA toolkit.
1. User Stories The staple of Agile methodologies. A User Story follows the format: "As a [role], I want [feature], so that [benefit]." The inclusion of the "benefit" ensures the requirement delivers business value. The 2021 context emphasizes the use of digital collaboration boards (like Miro or Jira) to manage these stories.
2. Use Cases and Scenarios While User Stories are high-level, Use Cases detail the interaction between the user (actor) and the system. They define the "Happy Path" (successful outcome) and "Exception Paths" (error handling), providing developers with clear logic flow.
3. Business Process Model and Notation (BPMN) BPMN provides a standard graphical notation for drawing business processes. It creates a visual language understandable by both business managers and technical developers. Day 7 — Integration & Review
4. Non-Functional Requirements Analysis Often the source of project failure if neglected. This focuses on how the system performs rather than what it does. The FURPS model is a common checklist:
Every technique has blind spots. Use them in tandem.
A Comprehensive Guide to the 2021 Toolkit for Modern Practitioners
Day 1 — Stakeholders & Elicitation
Day 2 — Requirements & Modeling
Day 3 — Process & Data
Day 4 — Prioritization & Risk
Day 5 — Prototyping & Validation
Day 6 — Strategy & Business Case
Day 7 — Integration & Review