While the Agile Manifesto’s values clearly state they prefer working software over comprehensive documentation, the general misconception around Agile projects is that you don’t do any documentation. This session will cover what we truly mean by just-in-time requirements by discussing when to get details around requirements, best practices for storing/maintaining requirements, and how much detail is too little or too much. We will also cover other types of documentation such as design/architecture artifacts as well as end user documentation like help files/user guides and how they fit into an Agile process.