Adrenaline Junkies and Template Zombies is a collection of 86 patterns of project behaviour collected and documented by a group of 6 authors from the Atlantic Systems Guild.

Each pattern is presented with a title, a picture, a one- or two-sentence summary, and a few pages describing the pattern in more depth. This format works pretty well, and the book is both funny and very easy to read. However, when I finished reading the book and asked myself what I had learnt from it, I had to answer "Not much".

That's not to say it's a bad book, just that if you have been working in software development projects for a few years, there aren't that many new insights here. However, the book does a good job of singling out and labelling various project behaviours (usually bad ones), which is useful.

Of all the patterns in the book, the ones I liked the best were "The Blue Zone", "Practicing Endgame", "Mañana" and "Time Removes Cards from your Hand".

"The Blue Zone" describes the green zone, which is anything that is explicitly ordered or allowed by the project, and the red zone, which is anything explicitly forbidden. The blue zone is everything else, activities that are neither explicitly allowed, nor explicitly forbidden by the scope of the assignment. In the authors' opinion (and in mine, too), it is good to sometimes operate in the blue zone, in addition to in the green zone, in order to achieve the best outcome. Or, in the words of the quote ending the pattern: "The correct amount of anarchy on a project is not zero".

In "Practicing Endgame", the idea is that you should be thinking about and testing against your release criteria continuously, as opposed to leaving that till the end. The analogy given in this pattern is that of the university course, where you may have several tests throughout the term, in addition to the final exam. This "continuous" exam preparation gives better results than the one-off method of only having the final exam.

The last two of the patterns I liked the most both deal with time.

"Mañana" simply states that if your goal date is more than 30 to 90 days out, you need to set sub-goals that are within 30 to 90 days, in order to make the people on the project feel the right sense of urgency.

"Time Removes Cards from your Hand" describes how you have fewer and fewer options the longer you pretend that everything is fine, even though things are not fine. You might end up with many half-finished features, instead of a few completely finished features, and it might not be the most urgently needed features.

Except for the concept of the blue zone, which I like and which I had never seen explicitly described before, even the patterns I liked are not really teaching me a lot that I didn't already know.

In fact, if you are using agile methods like XP or Scrum, then you will recognize a lot of the patterns and advice as standard agile working procedures ("Straw Man" is another example of this).

On the other hand, there are a number of examples of anti-patterns from (it seems) process-heavy larger companies, for example "False Quality Gates" (documents are check for format, not contents), "Paper Mill" and "Orphaned Deliverables" (both deal with places where the measure of progress is documents, not working software), and "Cider House Rules" (rules are made by people unconnected to the project).

When it comes to the names given to the different patterns, there are some hits and some misses. A name that is both catchy and describes the pattern in a good way makes the pattern so much easier to remember. My favourite is "Template Zombies", which I think is pretty self-explanatory, but "One Throat to Choke" is also very good. But naming is hard, and there are many patterns that I feel have pretty awkward or non-descript names, like "Lease your soul" (about how to adopt new technology - I'm thinking more in terms of a tool-box than selling/leasing your soul to some new technology) and "System Development Lemming Cycle" (that the process used isn't tailored - but where did the lemmings come from?).

Another complaint is that the different patterns presented in the book are not organized around themes - instead they are just put in random order. I would have preferred if they were grouped together, since many of the patterns deal with related concepts.

So, in summary, the patterns in the book cover many different project behaviours. The descriptions are useful and well written, but if you have been involved in software development projects for a while, most of the patterns should already be familiar to you. Still, they may serve as a useful reminder - plus, you get (in many cases) snappy names for some of the behaviours, which may make them easier to diagnose and talk about.

Also, if you're interested in this book, check out episode 131 at Software Engineering Radio. That podcast is an interview with Tom DeMarco and Peter Hruschka about this book, and it is well worth listening to. ( )

The book "Adrenaline Junkies and Template Zombies, Understanding Patterns of project behavior" contains 86 patterns, written in an easy readable and recognizable style which make you think about how people behave in projects. The authors have a lot of experience in various areas; their different views help you to get a broader understanding of issues that you can face in projects.

Patterns help us to understand things. They are not necessarily good or bad; in fact they may or may not be applicable given the situation at hand. I see many of the patterns my projects and daily work. Reading the patterns made me think on how we do things, and helped me to discuss them with colleagues. Below some examples of patterns, and an impression on how they helped me to understand and improve my way of working.

37: Talk then write: This pattern states that decisions made in meeting should be immediately afterwards communicated in writing. Pretty obvious, but I still see it happening that it takes a long time before we communicate what we decided, or that it is not communicated at all, that we do not inform all involved, etc. Due to time, the decision loses force, becomes unclear, forgotten, or it may even create resistance. With agile we have much better means now to communicate instantly, so let's do it! Use the war rooms, information radiators, wiki's etc, as much as possible, quickly after decisions are made, and update them when decisions are revised.

56: Undivided attention: This pattern states that undivided attention in a single project improves individual performance. With agile we usually have technical teams with full time members, focusing on the iteration at hand. But what about supporting functions? They are usually allocated to multiple projects, and also in process support, improvements, line support, etc. Task switching makes it difficult to give sufficient attention to each assignment, to build up relationships with the teams, and to really understand the issues and provide effective and timely solutions. Maybe it would be better to combine some of those part-time roles in a project, and have somebody working most of his/her time for one project? Or make the business case for a support role, increase the funding and assure that somebody can spend at least half time on one project, in stead of just of couple of hours or a day each week.

These are just 2 of the many patterns from the book that made me think about things. Reading the book made me feel like attending a good conference. There are a lot of interesting subjects in there, some which confirm what you already know, some which are less relevant for you, but there are certainly useful things in there. So most probably you will find some patterns that help to think about your work, to discuss it, and to improve it.
( )

I love the authors, but this list of patterns of project dynamics feels rushed, poorly argued, and unsatisfying. ( )