Validating the quality of requirements is a problem on many projects. Agile processes can make this tendency worse, especially if people think that they are supposed to start implementing a solution quickly. This is where a quality assurance person earns the big bucks.If Agile projects insist on trying to work with "requirements as conversation," someone on the team, ideally the quality assurance person, has to take on the task of creating a permanent record of these conversations.The QA person should be proactive in recording what the user expects to be able to do once the software is delivered. Appropriate documentation for requirements in agile projects is the topic of this talk.