nw-bdd-requirements

# BDD Requirements Discovery "If you're not having conversations, you're not doing BDD." -- Liz Keogh BDD discovers "what we don't know we don't know" through collaborative exploration with concrete examples, not tools or formats. ## The Three Amigos Three perspectives revealing each other's blindspots: 1. **Problem Owner** (PO, BA, Domain Expert): business need | acceptance criteria | domain knowledge 2. **Problem Solver** (Developer, Engineer): technical constraints | implementation complexity | technical edge cases 3. **Skeptic** (Tester, QA): failure modes | edge cases and boundaries | challenge assumptions ### Session Structure (25-minute timebox) 1. Read user story aloud (2 min) -- shared context 2. Identify acceptance criteria/rules (8 min) -- "what must be true for done?" 3. Explore examples per rule (12 min) -- concrete scenarios, edge cases 4. Capture questions (ongoing) -- unknowns on red cards 5. Review and summarize (3 min) -- shared understanding check If unmappable in 25 min: too large (split) | too uncertain (spike) | team needs practice. ## Example Mapping ### Four Card Types - Yellow: User Story (1 per session) | Blue: Business Rules/AC | Green: Concrete Examples | Red: Questions/Unknowns (blockers) ### Visual Layout ``` [Yellow] User Story: Transfer money between accounts | +-- [Blue] Rule: Amount must not exceed source balance | +-- [Green] $500 balance, transfer $400 -> succeeds | +-- [Green] $500 balance, transfer $500 -> suc...