ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1949 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
Agile and Iterative Development
Author:
Craig Larman
ISBN:
0-13-111155-8
Publisher:
Addison-Wesley
Pages:
342pp
Price:
£27-99
Reviewer:
James Roberts
Subject:
management
Appeared in:
16-2
This book is a high-level overview of agile and iterative development styles. It provides an overview of the reasons for agile development, giving the motivation for using these methods, and some contrasting and complementary descriptions of important examples.

The book is at its best in its descriptions and comparisons of four agile methods (Scrum, XP, Evo and RUP). The descriptions are in enough detail to give a good flavour of each one, and how they should (and should not) be applied - with extensive cross-references to each other. This both contrasts the strong and weak points of each method, and shows their similarity, which gives a good intuitive background of how agile methods work.

Although the book does not give enough information on the agile methods to allow the reader to start using them in anger, the book includes recommended further reading with each chapter.

I found the book somewhat evangelical - giving the impression that no waterfall-based project could possibly succeed (backed with large amounts of rather one-sided case study evidence). This grated at times. I would have liked to see more negative experiences on the agile side - not just on the waterfall side.

In summary, this is a readable book, which gives a good start point for anyone interested in agile methods. The main reservation that I have is based on its evangelical tone - the author's clear enthusiasm for iterative development seemed at times to overshadow his critical facilities.