Elaborating Scenarios

Interview Phase (Optional)

When to Interview: Skip if the user has already specified: scenario coverage depth (happy path + validation + state violations), known edge cases to include, and stakeholders available for review. Interview when coverage goals are unclear or edge cases haven't been identified.

Interview Strategy: Align on scenario depth and coverage strategy to avoid under-specification or excessive documentation. Identify stakeholders who can validate business rules.

Critical Questions

When scenario coverage is uncertain:

1. Scenario Depth & Coverage Goals (Impact: Determines scope—happy path only vs. comprehensive coverage)
   • Question: "How comprehensive should scenario coverage be? (A) Happy path + basic validation, (B) All command variations, (C) Comprehensive including edge cases and error paths"
   • Why it matters: Affects time investment and implementation complexity; production code needs (C), design validation might use (A) or (B)
   • Follow-up triggers: If (C) → ask "How many scenarios per command is reasonable?"; if (A) → clarify MVP vs. production distinction