ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ 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 1918 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:
Organizational Patterns of Agile Software Development
Author:
James Coplien&Neil Harrison
ISBN:
0-13-146740-9
Publisher:
Prentice Hall
Pages:
401pp
Price:
Reviewer:
Francis Glassborow
Subject:
patterns
Appeared in:
C Vu 17-

This book was a run-away seller at the recent ACCU Conference. Blackwells sold every single copy available in the UK. I know that because the publishers shipped 40 copies from the US for sale at the conference on the strict condition that they might not be sold anywhere else. Apparently it is not currently for sale in the UK. Neither the lead author nor anyone else I know has been able to discover why this is the case.

Now to the book itself. As you would expect from the lead author it is well written and challenges your thinking. It covers almost 100 organizational patterns culled from a study of more than 100 software development organizations.

The idea for Patterns was imported from the works of Alexander who was concerned with architecture (of buildings). The pattern concept was first applied to the ideas of software architecture. While I think that the idea has sometimes been abused or at least greatly over used, I am sure that it has done much to help software development.

In this book, we move on from the architecture of software to the 'architecture' of organisations that develop software. In my opinion, there is nothing very special about such organisations. Good organization is good organization regardless of the product. The reason I make that comment is that I find this to be not only an excellent study of software development organisation, but also an excellent study of organization.

Very little other than the examples in this book is specific to software. It is sad that the title will result in the book being stuck on the specialist shelves of bookstores. I would love to see this book rewritten and re-titled so that it will be read far more widely.

In the meantime, if you are involved in managing software development, buy this book, read it carefully and consider how you can apply the ideas to your own work.

In addition, if the publishers are still not distributing it in your country ask them what they are playing at because you deserve access and the authors deserve their royalties.