tad-elicit

Requirement elicitation is a structured process of gathering stakeholder input through 3-5 mandatory rounds of questioning to define project scope, constraints, and priorities. It enforces deterministic flows and uses 0-9 options instead of yes/no questions to ensure precise data collection.

Structured requirement elicitation differs from ad-hoc stakeholder interviews by enforcing a deterministic 3-5 round questioning flow and automatically recording round-by-round evidence for audit traceability. It uses 0-9 options instead of yes/no questions to capture precise priorities and constraints.

Yes, this requirement elicitation approach enforces the use of 0-9 options instead of yes/no questions to capture nuanced stakeholder priorities. You can use it for new engagements by loading the quick-start template to define scope, constraints, and priorities across 3-5 mandatory rounds.

Enforcing 3-5 rounds of requirement elicitation ensures thorough scope definition but may add overhead for simple engagements. The mandatory minimum of three rounds and deterministic flow might be excessive if stakeholder input is already well-defined and constraints are clear.

You can start requirement elicitation for new engagements by using a quick-start template that initiates a structured 3-5 round questioning flow. The process loads the elicitation task from a markdown file and immediately begins recording stakeholder evidence.