[Home]ProjectRetrospectives

FrontPage | BookOfChanges | Preferences

Project Retrospectives, a Handbook for Team Reviews 2001, 268pp, Dorset House [ISBN 0932633447 (amazon.com, search)] by NormKerth
Read a portion of chapter 2 here: http://www.retrospectives.com/pages/Anatomy.html
I picked this up at the AYE conference, and found it very much to my liking. It reads well in linear form and is organized in reference modules for later random reference. I liked the way Kerth summarized JerryWeinberg's works in reference as well as VirginiaSatir's.

Norm's style matches my preferences, (we're both the same INFP in Myers-Briggs) and his way of using case stories then discussing points of variance seems to highlight main points and places to drill for more. His description of dealing with people's emotional trauma issues in either post-mortem (after a failed project) or retrospective for an organization with a painful culture helped me see how to get past obstacles I encounter.

Recommended.

--BobLee November, 2002

I was expecting to enjoy this book after reading Bob's review. I wasn't disappointed. I found myself in a similar dilemma to when I read JerryWeinberg...too much to underline! Although the book is the reference on retrospectives, I believe that the wisdom that Norm has imparted through this book is applicable in a much broader context. Being an INFP as well, I'm interested in what a more pessimistic reader would take from the book. --DaveHoover August, 2003


I keep it close at hand at work and have found the tips in this book very useful. Some of the techniques need slight adjustment to work for more frequent retrospectives (every 2 weeks). ENFJ. Optimist :) RachelDavies


I facilitated a "retrospective" not too long ago with the teaching team (of which I am a part, I suppose) for a rather innovative software engineering course. I have known of some of the techniques for reviews of this kind for quite a while. From Norm's book I got the part that lets the exercise be a success:

Now, I don't think those things are described in Norm's book quite that way. However, having read his book, my POV on a retrospective was different enough that this is what I did, and what I had in mind. Before reading Norm's book, like a good problem-solving type, I'd be all ready to go solve problems in a retrospective. That's not too helpful in a room full of big-brained problem solving types all charging off to solve problems too, and maybe dueling about who's quicker, smarter, or more creative. Making room for the humanity of the people and the heat likely left over from the project is something I think I learned from Norm's book. With retrospectives "premature solution" is unsatisfying for everyone but the source. (And I know that phrase isn't from Norm's book.)

Lots of people talk about learning in organizations, or learning organizations. They tend to be a bit short on how to do it. This is how to do it. It's work, real work, to have a retrospective but worth the effort I think. It's nice to be able to channel someone wiser than yourself when you're doing it; someone like Norm Kerth. -- JamesBullock

It's fallen to me to run to facilitate "retrospectives" (far too short for a real retrospective, but better than nothing) at WDS, and I've found Project Retrospectives invaluable in fulfilling that need. I do tend to cherry-pick activities and artifacts, but then I have to get somehting useful out of half-a-day at most. --KeithBraithwaite (INTP, for what it's worth)

The most important thing in this book is to remind us that teams and people need maintenance too. --SteveFreeman

A BookOnTheBookshelf


Locations of visitors to this pageFrontPage | BookOfChanges | Preferences
Edit text of this page | View other revisions
Last edited November 2, 2006 11:58 am by ElizabethWiethoff (diff)
Search: