Most developers, testers, and managers on – Selection from Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior [ Book]. The authors of Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior have seen a lot of wrongheaded. Adrenaline Junkies and Template Zombies has ratings and 30 reviews. Wendy said: I really want to give all my coworkers copies of this book. Because t.. .
|Published (Last):||1 May 2010|
|PDF File Size:||15.70 Mb|
|ePub File Size:||5.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
Goodreads helps you keep track of books you want to read. Want to Read saving…. Want to Read Currently Reading Read. Refresh and try again. Open Preview See a Problem? Thanks for telling us about the problem. Return to Book Page. Adrenaline Junkies and Template Zombies: Adrenaline junkies, dead fish, project sluts, true believers, Lewis and Clark, template zombies.
Most developers, testers, and managers on IT projects adrenalone 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 usab Adrenaline junkies, dead fish, project sluts, true believers, Lewis and Clark, template zombies.
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. In Adrenaline Junkies and Template Zombies, the six principal consultants of The Atlantic Systems Guild present the patterns of zombied they adreanline often observe at the dozens of IT firms they transform each year, around the world.
The result is a quick-read templste 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 adrenakine 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 juknies help you quickly move those above and below you to the next step on your project. You’ll find classic patterns such as these: 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.
Paperbackpages. Understanding Patterns of Project Behavior. To see what your friends thought of this book, please sign up. To ask other readers questions about Adrenaline Junkies and Template Zombiesplease sign up. Be the first to ask a question about Adrenaline Junkies and Template Zombies. Lists arrenaline This Book. Sep 02, Wendy rated it really liked it Shelves: I really want to give all my coworkers copies of this book.
Because the coolest thing about it is that it gives you a language to talk about software development projects with. This book is basically a dictionary teemplate “project patterns” – patterns of behavior, good and bad, that software development groups often zo,bies.
Anyone who has worked in software or probably on other complex projects is going to recognize many of zobmies patterns. Although, I’m personally very grateful that I don’t recogn I really want to give all my coworkers copies of this book.
Although, I’m personally very grateful that I don’t recognize some of the really dysfuntional ones. Since reading this book, I find myself wanting to say, “Hey, I smell a dead fish,” when we’re junnkies about a schedule that we all know we can’t meet, but no one wants to say anything.
Or, “Wow, that new hire is totally Ben,” when I’m trying to convey that she clearly loves her job and makes the workplace better for everyone around her. You’ll pick up some practical tips and advice from this book as well, but by far the most valuable thing is being able to describe stuff that you’ve tmeplate known about, but never had words for.
Aug 12, Roman Chumakov rated it it was amazing Shelves: As with most pattern books, this is one you flip through in an hour and then save it to refer back to. The strength of software management and development pattern books is describing problems that commonly occur, not really telling you how to fix them.
Thus, they tend to be frustrating because you’re left thinking, “how am I going to get this to work in my organization? Still, they’re extremely helpful things to keep in mind which you may be forgetting “The Empty Chair” or no longer think applies to you “Young Pups Old Dogs”helpful advice if you must do it “Offshore Follies”to some that can be reduced to a clever quip, as in “War Room” where DeMarco says, “I’m beginning to think that a project not worth a war room may be a project not worth doing.
As far as patterns books go, this one was pretty light on the “pattern” part. It was more a series of short essays about things observed on project teams. Some of them offered advice. Some of them were more anti-patterns–things to avoid. Some were just strange. The “IT seems to have a higher proportion of musicians” was a particularly useless ‘pattern’. There are a few gems in here, especially around distributed development and high performing teams.
There was lots that will be familiar to Agi As far as patterns books go, this one was pretty light on the “pattern” part. There was lots that will be familiar to Agile practitioners, and there was lots that you’ll recognize as happening in your own organization, both good and ill. Overall, this is an easy read with some value, but if you’re trying to learn about project management, you’d be better off starting with more focused books.
On the other hand, if you’re currently running a team or three, it couldn’t hurt to leaf through here to remind yourself what you’re doing right–and what you need to fix. Jul 30, David Lindelof rated it really liked it Shelves: Reading this book felt a bit like going to church to listen to the nth version of the same sermon.
You agree with everything that’s being said, you are comforted in your own beliefs, and you would certainly give this book to a newcomer to the field. That said, anyone who’s been through Peopleware or similar books will probably not learn any really new things from this book.
It’s very fun to read about those behavioral patterns that the authors have documented, but I would be much more interested Reading this book felt a bit like going to church to listen to the nth version of the same sermon. It’s very fun to read about those behavioral patterns that the authors have documented, but I would be much more interested in reading about patterns that work, rather than anti-patterns. It’s definitely a good, well-researched book, but I would prefer Coplien’s “Organizational Patterns of Agile Software Development” book instead.
Oct 22, Henrik Warne rated it liked it. 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 mu 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.
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 oneswhich is useful.
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, tooit 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: 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. 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 templae agile methods like XP iunkies Scrum, then you will recognize a lot of the patterns and advice as standard agile working zombifs “Straw Man” is another example of this.
Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior
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 templaet Deliverables” both deal with places where the measure of progress is documents, not working softwareand “Cider House Rules” rules are made by people unconnected to the project.
Adrfnaline 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.
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.
Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior by Tom DeMarco
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 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. Jul 20, Mircea Nistor rated it really liked it Shelves: Some of the stories typologies are no longer actual but most are and you should be afraid that you might find yourself in one of the not so nice ones.
Apr 28, Ben Linders rated it it was amazing. 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 applicabl 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. They are not necessarily good or adrenallne 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.