| Can I Come Look At These Items? | | This online store is in association with Amazon.com, so these great, high-qualiy products will come from their warehouse or from other partners. Thanks for shopping! |
|
|
|
Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) | 
 enlarge | Author: Andreas Rueping
Publisher: Wiley
Category: Book
List Price: $50.00
Buy New: $22.23
You Save: $27.77 (56%)
New (24) Used (7) from $18.99
Avg. Customer Rating:  4 reviews
Sales Rank: 443573
Media: Paperback
Number Of Items: 1
Pages: 244
Shipping Weight (lbs): 1
Dimensions (in): 9 x 7.5 x 0.7
ISBN: 0470856173
Dewey Decimal Number: 005.15
EAN: 9780470856178
ASIN: 0470856173
Publication Date: September 19, 2003
Availability: Usually ships in 1-2 business days
Shipping: International shipping available
Condition: Brand New, Perfect Condition, Please allow 4-14 business days for delivery. 100% Money Back Guarantee, Over 1,000,000 customers served.
|
| Also Available In:
|
| Similar Items:
|
| Editorial Reviews:
Product Description
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 Rueping 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.
|
| Customer Reviews:
 Left me wondering what to actually do ... October 30, 2008
I was a bit disappointed with the book since our team has struggled with documentation. The general consensus was that this book was OK but did not really clear a whole lot things up for us.
 Useful book! July 4, 2008
1 out of 1 found this review helpful
This book about Agile Documentation turned out to be very useful, and is a kind of book I have been looking for. A lot of the same issues and conclusions regarding Software documentation we have discussed in our own Company are discussed in this book, and the advices from the author is very good. Written in a style that makes it easy and fast to read.
Everyone working with documentation in the software business should read this book!
Great concept May 7, 2008
As a tech communicator with long experience in various engineering environments, I am enthused about the concepts espoused here. We need to write "documentation" the way we like to read "documentation"; it needs to have the content needed particularly by us, in the style we need, and concise and to the point when our need begs for that. We need to look toward long term relevance and up-to-dateness - of all technical information, especially technical reference information, and it is more likely to be so if it is concise and focused to start with. We are all scanners, doing stuff or acquiring information in a hurry, doing tasks in a hurry. Another book told about how a new guy on a project was given a thick document about the project. Two days later, he had a headache; couldn't get the picture. If he were given an agile-ly written doc, he would have gotten the picture. Ginny Redish (Letting Go of the Words) is another great one along the same thinking.
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".
 Documentation, But not very agile October 28, 2007
3 out of 3 found this review helpful
Ruping did a good job of covering the topic of software documentation, albeit somewhat generically, i.e. not that specific to software development. He quotes a lot of others in his book and identifies that the goal (of agile documenting) is 'light-weight but sufficient'. If you're working on developing a system for documenting software development (or really any other technical project) this would make a good reference, but start at the back of the book. He uses patterns in his book as his technique to cover the topic. They are recognized problems and solutions, and he lists all of them in the back of the book in thumbnail form. The middle of the book provides the elaboration. The first part of the book is his professional history (sorry Ruping, but not that interesting), and his how-to-use-the-book section.
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 cliche. But again, if you're looking for a reference on the topic of technical documentation - this is not bad.
|
|
|
| |
News 
