or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
More Buying Choices
Have one to sell? Sell yours here
Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series)
 
 
Tell the Publisher!
I'd like to read this book on Kindle

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) [Paperback]

Andreas Rueping (Author)
3.4 out of 5 stars  See all reviews (5 customer reviews)

List Price: $50.00
Price: $25.95 & this item ships for FREE with Super Saver Shipping. Details
You Save: $24.05 (48%)
  Special Offers Available
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
In Stock.
Ships from and sold by Amazon.com. Gift-wrap available.
Want it delivered Monday, January 30? Choose One-Day Shipping at checkout. Details
Textbook Student FREE Two-Day Shipping for Students. Learn more


Book Description

0470856173 978-0470856178 September 19, 2003 1
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.


Special Offers and Product Promotions

  • Buy $50 in qualifying physical textbooks, get $5 in Amazon MP3 Credit. Here's how (restrictions apply)

Frequently Bought Together

Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) + Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process + Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series)
Price For All Three: $94.07

Show availability and shipping details

Buy the selected items together


Editorial Reviews

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)

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.


Product Details

  • Paperback: 244 pages
  • Publisher: Wiley; 1 edition (September 19, 2003)
  • Language: English
  • ISBN-10: 0470856173
  • ISBN-13: 978-0470856178
  • Product Dimensions: 9.3 x 7.4 x 0.6 inches
  • Shipping Weight: 1 pounds (View shipping rates and policies)
  • Average Customer Review: 3.4 out of 5 stars  See all reviews (5 customer reviews)
  • Amazon Best Sellers Rank: #226,171 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

 

Customer Reviews

5 Reviews
5 star:
 (2)
4 star:    (0)
3 star:
 (1)
2 star:
 (2)
1 star:    (0)
 
 
 
 
 
Average Customer Review
3.4 out of 5 stars (5 customer reviews)
 
 
 
 
Share your thoughts with other customers:
Most Helpful Customer Reviews

7 of 8 people found the following review helpful:
3.0 out of 5 stars Documentation, But not very agile, October 28, 2007
By 
Ken (Tucson, AZ USA) - See all my reviews
Amazon Verified Purchase(What's this?)
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) (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.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


3 of 3 people found the following review helpful:
5.0 out of 5 stars Great concept, May 7, 2008
Amazon Verified Purchase(What's this?)
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) (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".
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


1 of 1 people found the following review helpful:
2.0 out of 5 stars Interesting book that is not about Agile Information Development, October 21, 2010
By 
Timohuatl (San Francisco) - See all my reviews
This review is from: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects (Wiley Software Patterns Series) (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.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No

Share your thoughts with other customers: Create your own review
 
 
 
Most Recent Customer Reviews



Only search this product's reviews



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
Key Phrases - Statistically Improbable Phrases (SIPs): (learn more)
agile documentation, agile attitude, big picture document, documentation infrastructure, documentation portfolio, frequent reorganisation, careful ruling, document landscape, coherent pages, agile project, data access layer, source code comments, application landscape, agile development, other project activities, agile approach, logical key, agile software development, project documentation, lowercase alphabets, configuration management system, technical organisation, consultancy projects, target readers, usage concept
Key Phrases - Capitalized Phrases (CAPs): (learn more)
Project Persistor, Project Navigator, Project Vista, Project Contentis, Project Extricate, Agile Manifesto, Alistair Cockburn, Alistair Cockhurn, Technical Basis, Scott Ambler, Content Editing, Forces Documentation, Forces Project, Jim Coplien, Project Openl, Project Paracelsus, Return Codes, Agile Modeling, Gulbins Kahrmann, Gulhins Kahrmann, Solution Project, Topic Building
New!
Books on Related Topics | Concordance | Text Stats
Browse Sample Pages:
Front Cover | Table of Contents | First Pages | Index | Back Cover | Surprise Me!
Search Inside This Book:





Tags Customers Associate with This Product

 (What's this?)
Click on a tag to find related items, discussions, and people.
 

Your tags: Add your first tag
 

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 


Active discussions in related forums
Search Customer Discussions
Search all Amazon discussions
   
Related forums





Look for Similar Items by Category


Look for Similar Items by Subject