Requirements are rarely lying around waiting to be collected — they must be drawn out of people, documents and behaviour, and no single technique does that for every situation. Learn to select and apply interviews, workshops, observation and document analysis using a technique-selection matrix matched to stakeholder availability, requirement complexity and time.
Watch the free preview
Why requirements must be elicited, not just collected — free to watch, no account needed.
What you'll learn
- Explain why requirements must be elicited rather than simply collected from stakeholders
- Describe the strengths and blind spots of interviews, workshops, observation and document analysis
- Select an elicitation technique using stakeholder availability, requirement complexity and time constraints
- Diagnose a technique mismatch and choose a better-fit approach for a real IT scenario
- Build a reusable Elicitation Technique Selection Matrix for your own team
Syllabus
Why Elicitation Is Hard, and What It Really Is
Why requirements must be elicited, not just collectedFree preview
The core elicitation techniques and their blind spots
Choosing the Right Technique
The dimensions that should drive technique choice
Matching each technique to the situation
Elicitation in Real IT Delivery
Elicitation across an Agile delivery flow
Case study — the BA who only ran interviews
Making Good Technique Choice a Habit
Building your Elicitation Technique Selection Matrix
Common elicitation traps and how to avoid them