- Paperback: 244 pages
- Publisher: Wiley; 1 edition (Aug 26 2003)
- Language: English
- ISBN-10: 0470856173
- ISBN-13: 978-0470856178
- Product Dimensions: 23.6 x 18.7 x 1.5 cm
- Shipping Weight: 454 g
- Average Customer Review: 4.0 out of 5 stars See all reviews (1 customer review)
-
Amazon Bestsellers Rank:
#339,794 in Books (See Top 100 in Books)
- #22 in Books > Computers & Internet > Project Management > Agile
- See Complete Table of Contents
|
||||||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||
Product Details |
Product Description
Review
??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)
Product Description
Software documentation forms the basis for all communication relating to a software project. To be truly effective and usable, it should be based on what needs to be known. Agile Documentation provides 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.
Inside This Book
(Learn More)
First Sentence
Before we plunge into the actual patterns, I'd like to take a brief look at the projects from which the patterns in this book were mined. Read the first page
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Before we plunge into the actual patterns, I'd like to take a brief look at the projects from which the patterns in this book were mined. Read the first page
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most helpful customer reviews
4.0 out of 5 stars
A Good Book to Have,
By
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Paperback)
A good book to have if you are involved with software project documentation in any environment, including agile. I particularly liked Chapter 3 - Layout and Typography. It deals with things like proportions, line length in relation to page size, blank space versus text, etc.One of the things that help me decide whether or not to buy a book is its table of contents: Foreword
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
3.4 out of 5 stars (5 customer reviews) 7 of 8 people found the following review helpful
3.0 out of 5 stars
Documentation, But not very agile,
By Ken - Published on Amazon.com
Amazon Verified Purchase(What's this?)
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Paperback)
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 cliché. But again, if you're looking for a reference on the topic of technical documentation - this is not bad. 3 of 3 people found the following review helpful
5.0 out of 5 stars
Great concept,
By Daniel Baker - Published on Amazon.com
Amazon Verified Purchase(What's this?)
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Paperback)
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". 1 of 1 people found the following review helpful
2.0 out of 5 stars
Interesting book that is not about Agile Information Development,
By Timohuatl - Published on Amazon.com
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Paperback)
The author misleads the audience with his title, "Agile Documentation." There is nothing about Agile methodology in the book, rather a way to produce "Lightweight Documents." It is conceivable that "Lightweight Documents" could be appropriate deliverables for products using Agile development, but he does not lay that foundation.
|
|
Listmania!
Look for similar items by category
- Books > Business & Investing > Skills > Communications
- Books > Computers & Internet > Computer Science > Systems Analysis & Design
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
- Books > Computers & Internet > Project Management > Agile
- Books > Computers & Internet > Software
- Books > Engineering > Industrial, Manufacturing & Operational Systems > Manufacturing
- Books > Professional & Technical > Engineering > Industrial, Manufacturing & Operational Systems > Manufacturing
Look for similar items by subject
Feedback
Would you like to update product info or give feedback on images?
|
