CAPM Practice: Determine how project methodologies influence business analysis processes

This principle (from XP) recognizes that written user stories don't capture everything — the conversation that happens around a story is where real understanding develops. Stories are memory aids that prompt conversation, not self-contained specifications meant to eliminate dialogue.

**Why not A:** This principle does not mean requirements never need to be written down. Written user stories and acceptance criteria still serve as memory aids and reference points. The principle emphasizes that the written artifact alone is incomplete without the conversation that gives it context and shared understanding.

**Why not C:** Requirements are not negotiated in real-time meetings and then frozen. In adaptive projects, requirements continue to evolve through ongoing dialogue. The conversation is continuous, and understanding deepens over time as the team learns more through implementation and feedback.

**Why not D:** Only verbal agreements counting as requirements would eliminate valuable documentation. The principle recognizes that both conversation and written artifacts play a role. Stories are written reminders that prompt conversation, and the combination of both creates shared understanding.