Choosing a technique to fit the source, observation and job shadowing, running a group discussion that does not collapse into debate, surfacing assumptions, and resolving conflicting requirements.

For readers gathering requirements from people who disagree with each other, or who cannot describe what they do.

By the end of this level you can get usable requirements from someone who cannot articulate their own work, run a group discussion that reaches agreement, and resolve two requirements that cannot both be met.

Eliciting from reluctant or unavailable sources, working through documents and systems when people are not available, validating requirements against evidence, and recognising a requirement that hides a constraint.

Written for people eliciting requirements where access is limited, the subject is technical, or the people involved have reason to be guarded.

The level leaves you able to reconstruct requirements from systems and documents when the people are unavailable, validate what you were told against what actually happens, and identify the constraint behind a stated need.

Why people misreport their own behaviour, the limits of asking, designing an approach for a whole programme, developing other analysts, and deciding when a requirement should not be met.

The most demanding level, concerned with why elicitation fails even when it is done correctly, and what to do about that.

You come away able to design an elicitation approach for an entire programme, allow for the gap between what people report and what they do, and recommend that a genuine requirement not be met.