Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior [Paperback]

Tom Demarco (Author), Peter Hruschka (Author), Tim Lister (Author), Suzanne Robertson (Author), James Robertson (Author), Steve McMenamin (Author)

Book Description

Publication Date: March 3, 2008 | ISBN-10: 0932633676 | ISBN-13: 978-0932633675

Adrenaline junkies, dead fish, project sluts, true believers, Lewis and Clark, template zombies . . .

Most developers, testers, and managers on IT projects are pretty good at recognizing patterns of behavior and gut-level hunches, as in, I sense that this project is headed for disaster.

But it has always been more difficult to transform these patterns and hunches into a usable form, something a team can debate, refine, and use. Until now.

In Adrenaline Junkies and Template Zombies, the six principal consultants of The Atlantic Systems Guild present the patterns of behavior they most often observe at the dozens of IT firms they transform each year, around the world.

The result is a quick-read guide to identifying nearly ninety typical scenarios, drawing on a combined one-hundred-and-fifty years of project management experience. Project by project, you'll improve the accuracy of your hunches and your ability to act on them.

The patterns are presented in an easy-reference format, with names designed to ease communication with your teammates. In just a few words, you can describe what's happening on your project. Citing the patterns of behavior can help you quickly move those above and below you to the next step on your project. You'll find classic patterns such as these:

* News Improvement
* Management By Mood Ring
* Piling On
* Rattle Yer Dags
* Natural Authority
* Food++
* Fridge Door
* and more than eighty more!

Not every pattern will be evident in your organization, and not every pattern is necessarily good or bad. However, you'll find many patterns that will apply to your current and future assignments, even in the most ambiguous circumstances. When you assess your situation and follow your next hunch, you'll have the collective wisdom of six world-class consultants at your side.

Editorial Reviews

Review

"Another masterpiece from the folks who brought you Peopleware. Anyone who has survived a software project or two will surely recognize many of these patterns and will be able to learn from most of them. Adrenaline Junkies and Template Zombies is a real joy." --Joel Spolsky, author of Joel on Software

"Who else but these particular authors could mine 150 years of software team experience to capture memorable names for oft-encountered situations? I suspect you will start using these phrases in your work--I already have." --Alistair Cockburn, author of Agile Software Development

"utterly delightful collection of essays about 86 'project patterns' . . . These 'patterns' are grimly familiar to anyone who has worked in project-related organizations; and unfortunately, they can be found in small companies as well as large ones. Fortunately, some of the patterns ('Rattle Yer Dags' and 'Nanny,' for example) are good ones, and should be encouraged. Sadly, though, far too many of them ('Dead Fish,' 'Project-Speak') are not only depressingly familiar, but astonishingly destructive to productivity, quality, and the morale of the project team. . . . I really love this book, not the least because each pattern can be read and understood in a moment or two, since they take only 2-3 pages to explain. . . . If Adrenaline Junkies and Template Zombies gets the attention it deserves, Scott Adams may have to return to Corporate America and get an honest job as a project manager." --Ed Yourdon, author of Death March

About the Author

If your organization builds systems of any kind, chances are that some of the methods and approaches that it uses came originally from the Atlantic Systems Guild. Collectively, the authors have published nearly twenty previous books, including Peopleware, Mastering the Requirements Process, The Deadline, Essential Systems Analysis, Waltzing With Bears, and Process for System Architecture and Requirements Engineering.

Product Details

• Paperback: 248 pages
• Publisher: Dorset House (March 3, 2008)
• Language: English
• ISBN-10: 0932633676
• ISBN-13: 978-0932633675
• Product Dimensions: 6.4 x 0.6 x 9 inches
• Shipping Weight: 12.8 ounces (View shipping rates and policies)
• Average Customer Review: 4.6 out of 5 stars  See all reviews (17 customer reviews)
• Amazon Best Sellers Rank: #602,730 in Books (See Top 100 in Books)

More About the Author

James Robertson trained as an architect, but switched to Information Technology because computing is more interesting than concrete, and bits have more possibilities than bricks.

With his wife Suzanne Robertson, he moved from his native Australia to the United Kingdom (the reverse of the usual migration path) and although he has a home in London, his work has taken him to every continent. James is a co-founder and principal of the Atlantic Systems Guild www.systemsguild.com.

James' work has been largely in the requirements side of IT. Getting the right requirements is crucial to correct software development, but so is innovation. James is a leading proponent of the principle of introducing innovation into the requirements process. His controversial article "Eureka: Why Analysts Should Invent Requirements" in IEEE Software, has been widely quoted and discussed.

He is co-creator of the Volere requirements techniques www.volere.org, which are being used by thousands of organizations worldwide.

James is a keen skier and lives in the French Alps when the snow is falling.

Most Helpful Customer Reviews

16 of 16 people found the following review helpful

3.0 out of 5 stars Funny and easy to read, but most of the content is well known September 27, 2009

By Henrik Warne

Format:Paperback

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.

9 of 9 people found the following review helpful

4.0 out of 5 stars Another Day, Another Pattern Book March 31, 2008

By Earl Beede

Format:Paperback

Patterns are all the rage these days in software development. You can't be a serious software person unless you invoke a pattern here or a pattern there. The bright folks at the Atlantic Systems Guild have named us 86 project patterns so that more of us can drop a pattern name here and there and get the mantel of being serious project folks.

Most of what you read in this book are patterns of things gone wrong patterns more than patterns of things gone right. I think that this is OK though I did find it a bit frustrating at times. There would be a suggestion on how to disrupt the negative patterns occasionally but, given the short, blithe entries, not a lot of detail. This book is more about diagnosis than about treatment.

So, read it more for enjoyment rather than serious project help. Anyway, most of the patterns, certainly the names, are all made up. "We make no claim to the universality of our observed patterns." Not measured, not tested, just observed. However, these are keen observers and I found myself agreeing with most of the entries.

7 of 7 people found the following review helpful

5.0 out of 5 stars Another classic from "those Peopleware guys" July 20, 2008

By Rob S. VINE™ VOICE

Format:Paperback

The title and cover caught my eye (today!) in the bookstore and after flipping through, I couldn't wait to get home and blow through it.

It's clear why this is getting a 5-star average here @ Amazon. Written by the same folks who authored Peopleware (classic skilled-person management book), it contains ~80 patterns of project behaviour alternating between helpful and harmful.

Almost immediately I had several, "Ohhh yeah! That's what's going on!" moments. The authors do a terrific job of identifying patterns and the reasoning behind them. Being relatively new to a management gig, this sort of resource is invaluable. You might not be able to fix some of the issues, but you'll certainly be able to notice them more quickly - which is really the first step.

Each pattern is about 2-3 pages long, clearly identified in the table of contents and with pattern headings that stand out. This presentation allows me to quickly refer back to find out the suggested cure.

Most patterns are presented with prescriptive, corrective behaviour. Granted it's not a detailed dissertation on how to fix organizational issues, but enough to get an idea of the scope of the fix; work through it, or time to find another employer?

I'm already in the process of recommending this to my peers. It's such a brief, valuable read that anybody with skin in the game (from developers to CEOs) should give it a look.