I'm struggling to determine where capturing of user story elaborations and discussions fits into agile. A lot of what I have read and agree with is:
- You should be focusing on discussions with your BAs and clients to elaborate the stories.
- Figure out what needs to be done rather than documenting every single requirement.
How do we capture enough details so that in a month or so, when someone in those discussions comes back and their memory of it was different from ours, we don't get into a debate/discussion over whether it is a new story or a bug because we didn't implement right in the first place?
This debate occurs because of maybe the scale of the change required due to this disagreement. Do we need to capture every decision "on paper" to avoid debates? Doing this is appears a bit contrary to some of the Agile Manifesto.