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 Manifesto: “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 process, and some tips and tricks, that have worked for me and I’m sure will help you.
"synopsis" may belong to another edition of this title.
BookAuthority listed my book as one of the "Best Scrum Books of All Time" (bit.ly/BestScrumAllTime) and one of the "Best New Scrum Books to Read In 2019" (bit.ly/BestScrum2019)
"One of the best new Scrum books" - BookAuthority"One of the best Scrum books of all time" - BookAuthority
"About this title" may belong to another edition of this title.
(No Available Copies)
Search Books: Create a WantCan't find the book you're looking for? We'll keep searching for you. If one of our booksellers adds it to AbeBooks, we'll let you know!
Create a Want