rm-elicitation

Plan the elicitation by selecting stakeholders, techniques, session calendar, and guide questions, then conduct sessions and confirm findings with stakeholders. The Skill produces an rm-elicitation report artifact capturing needs, constraints, conflicts, and confirmations.

Choose based on context: interviews for key stakeholders with deep knowledge, JAD workshops for consensus across multiple stakeholders, shadowing for existing operational processes, surveys for large groups, and prototypes for visual requirements. Always combine at least one direct technique with one validation technique.

Skip elicitation when requirements are already fully documented and validated, when a prior elicitation was exhaustive with no new information sources, or when no stakeholders are available. In those cases proceed directly to requirements analysis or schedule sessions first.

Without confirmation, findings reflect the analyst's interpretation rather than the stakeholder's actual requirements. Confirmation methods include member checking, walkthroughs of results, and confirmation prototypes, and this step is mandatory before advancing to analysis.

Elicitation cannot capture latent needs stakeholders do not yet know, which emerge during design or testing. Cultural bias can affect multinational settings, and direct observation only works for existing processes, so new systems require prototypes or vision workshops instead.