Approach to Requirements Elicitation
By Kristian Bainey
Requirements problems are among the most common causes of project failure, and most of them originate in how requirements were gathered. This article sets out a structured approach to elicitation. Kristian Bainey covers preparation, including identifying the right stakeholders and understanding the business context before the first session, and then examines the techniques available, such as interviews, workshops, observation, document analysis and prototyping, with guidance on when each is appropriate.
The article gives particular attention to confirmation. Capturing what a stakeholder said is not the same as understanding what the business needs, so the piece covers restating requirements, resolving conflicts between stakeholder groups, and validating that documented requirements are testable and traceable to business objectives.
Written for business analysts and project managers, it is equally relevant to technical leads who inherit requirements and need to judge whether they are complete enough to build from.
Key takeaways
- Preparation and stakeholder identification determine elicitation quality.
- Technique selection should match the context, not personal preference.
- Requirements must be confirmed, testable and traceable to business objectives.
This is an original summary published by K-PIC Systems. Read the full original article