Requirements elicitation is the process of drawing out, clarifying and refining what a system or feature needs to do by talking with stakeholders, asking questions and exploring scenarios. It is also called requirements gathering or requirements discovery, and is a core skill for business analysts and, increasingly, for testers and test managers.
Why it matters: Requirements rarely arrive complete. Gaps, assumptions and unclear edge cases become defects if they are not found early. Testers bring a useful angle to elicitation because they naturally think about what could go wrong, which helps teams change requirements before any code is written.
In practice: Elicitation usually happens through conversations rather than documents alone. Common approaches include:
- Three Amigos sessions where business, development and testing perspectives review a feature together.
- Working closely with business analysts to understand the business logic and objectives behind a feature.
- Walking through happy paths, negative paths and edge cases for each user journey.
- Asking what business problem a work item or feature is meant to solve.
Findings are fed back into the requirements and into planned test coverage.
Examples:
- Reviewing a feature in a Three Amigos session when it moves into analysis on the team board, and raising questions about missing permission rules.
- Working with a business analyst on integration logic that moves users between two applications, and agreeing the positive, negative and edge-case scenarios to be tested.
- Asking "what if" questions about a user journey that lead to changes in the requirements before development starts.
Common pitfalls:
- Waiting until testing starts to ask questions, when changing requirements is far more expensive.
- Treating elicitation as the business analyst's job alone, so testability concerns are never raised.
What is the difference between requirements elicitation and requirements analysis? Elicitation is about drawing information out of stakeholders. Analysis is about examining, organising and validating that information so it can be built and tested.
Why should testers get involved in requirements elicitation? Testers spot ambiguities, risks and missing scenarios early, which improves both the requirements and the test coverage.
