Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects Paperback – Aug 26 2003
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
??many (Test Documents) would benefit from this treatment?? (Professional Tester, October 03)
"...applicable to documentation for any project...highly recommended..." (CVu, Vol 16(4), August 2004)
From the Back Cover
Documentation is the castor oil of programming. Managers think it is good for programmers, and programmers hate it! Jerry Weinberg in Psychology of Computer Programming
Andreas Rüping sugars the pill by giving sound advice on how to produce lean and lightweight software documentation. It will be welcomed by all project team members who want to cut out the fat from this time consuming task. Guidance given in pattern form, easily digested and cross-referenced, provides solutions to common problems. Straightforward advice will help you to judge:
- What details should be left in and what left out
- When communication face-to-face would be better than paper or online
- How to adapt the documentation process to the requirements of individual projects and build in change
- How to organise documents and make them easily accessible
- When to use diagrams rather than text
- How to choose the right tools and techniques
- How documentation impacts the customer
Better than offering pat answers or prescriptions, this book will help you to understand the elements and processes that can be found repeatedly in good project documentation and which can be shaped and designed to address your individual circumstance. The author uses real-world examples and utilises agile principles to provide an accessible, practical pattern-based guide which shows how to produce necessary and high quality documentation.See all Product Description
Top Customer Reviews
One of the things that help me decide whether or not to buy a book is its table of contents:
Ch. 1 Finding the Right Topics
Ch. 2 Structuring Individual Documents
Ch. 3 Layout and Typography
Ch. 4 Infrastructure and Technical Organisation
Ch. 5 Management and Quality Assurance
Most Helpful Customer Reviews on Amazon.com (beta)
The problem I had with the book is that I didn't see anything new and innovating. I didn't have an `ah-ha' moment where I finally understood the real principles behind 'agile' documentation. I didn't find this book 'agile' at all. I also did not agree with all of his solutions, most seemed cliché. But again, if you're looking for a reference on the topic of technical documentation - this is not bad.
ONE distractor: He wrote the book with a bit of his own fluff. Maybe to give the book a slight bit of thickness. Could have been more to the point. An engineer I used to work with used to say "paid by the pound".
Given what it is, it's a good primer for developers to use for specs and so on. If those are well-done, the end-user docs are much easier to craft, so I'd recommend it to the intended audience.
Everyone working with documentation in the software business should read this book!
Look for similar items by category
- Books > Business & Investing > Skills > Communications
- Books > Computers & Technology > Computer Science > Systems Analysis & Design
- Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Technology > Project Management > Agile
- Books > Computers & Technology > Software
- Books > Professional & Technical > Engineering > Industrial, Manufacturing & Operational Systems > Manufacturing