LARGE PRINT EDITION You've taken classes. You've read Agile and Scrum books. Not only do they not tell you how to handle documentation, they rarely even mention it. When documentation is mentioned, it's usually that line from the Agile "Working software over comprehensive documentation" (AgileManifesto.org). The manifesto refers to things like specifications and design documents, not customer documentation. So, now what? After years of experience facing that same situation, I've compiled some answers. These are methods and processes, and some tips and tricks, that have worked for me and I'm sure will help you.