Buy new:
$33.95$33.95
Arrives:
Wednesday, May 17
Ships from: Amazon.com Sold by: Amazon.com
Buy used: $16.43
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required. Learn more
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Project Retrospectives: A Handbook for Team Reviews
| Price | New from | Used from |
- Kindle
$14.99 Read with Our Free App - Paperback
$16.43 - $33.9524 Used from $9.96 2 New from $33.56
Purchase options and add-ons
Whether your shop calls them postmortems or postpartums or something else, project retrospectives offer organizations a formal method for preserving the valuable lessons learned from the successes and failures of every project. These lessons and the measurements they yield foster stronger teams and savings on subsequent efforts.
For a retrospective to be effective and successful, though, it needs to be safe. Kerth shows facilitators and participants how to defeat the fear of retribution and establish an air of mutual trust. One tool is Kerth's Prime Directive: Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.
Applying years of experience as a project retrospective facilitator for software organizations, Kerth reveals his secrets for managing the sensitive, often emotionally charged issues that arise as teams relive and learn from each project.
Don't move on to your next project without consulting and using this readable, practical handbook. Each member of your team will be better prepared for the next deadline.
- ISBN-100932633447
- ISBN-13978-0932633446
- PublisherDorset House
- Publication dateJanuary 1, 2001
- LanguageEnglish
- Dimensions5.5 x 0.5 x 8 inches
- Print length268 pages
-
- PaperbackCurrently unavailable
-
-
-
- PaperbackCurrently unavailable
-
- PaperbackCurrently unavailable
-
-
-
-
-
-
Managing Expectations: Working with People Who Want More, Better, Faster, Sooner, NOW! (Dorset House eBooks)Kindle Edition -
-
-
-
-
Currently unavailable : Currently unavailable titles are unavailable for purchase in this format.
Object-Oriented Computation in C++ and Java: A Practical Guide to Design Patterns for Object-Oriented Computing
Currently unavailable : Currently unavailable titles are unavailable for purchase in this format.
Best Practices for the Formal Software Testing Process: A Menu of Testing Tasks
The Practical Guide to Business Process Reengineering Using Idefo
Creating a Software Engineering Culture
Surviving the Top Ten Challenges of Software Testing: A People-Oriented Approach
Communication Gaps and How to Close Them
iTeam: Putting the 'I' Back into Team
Format unavailable : Format unavailable items are not offered in the selected format. Other format options may be available on the item's detail page.
Managing Expectations: Working with People Who Want More, Better, Faster, Sooner, NOW! (Dorset House eBooks)
1 or more items shipped or sold by sellers other than Amazon.com
Frequently bought together

- +
- +
What do customers buy after viewing this item?
- Most purchasedin this set of products
Agile Retrospectives: Making Good Teams GreatPaperback$10.54 shipping - Highest rated | Lowest Pricein this set of products
FunRetrospectives: activities and ideas for making agile retrospectives more engagingPaperback$10.52 shipping - This item:
Project Retrospectives: A Handbook for Team ReviewsPaperback$10.52 shippingOnly 13 left in stock (more on the way).
Product details
- Publisher : Dorset House (January 1, 2001)
- Language : English
- Paperback : 268 pages
- ISBN-10 : 0932633447
- ISBN-13 : 978-0932633446
- Item Weight : 12.3 ounces
- Dimensions : 5.5 x 0.5 x 8 inches
- Best Sellers Rank: #1,510,487 in Books (See Top 100 in Books)
- #1,158 in Production & Operations
- #12,520 in Business Management (Books)
- #157,997 in Health, Fitness & Dieting (Books)
- Customer Reviews:
About the author

Discover more of the author’s books, see similar authors, read author blogs and more
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Project Retrospectives are review and improvement sessions which the project team does at the end of a project. A typical project retrospective takes a couple of days. During these days, there are a bunch of retrospective exercises which can be follows (and are described in the book). These exercises create a safe environment, help the project team remember the past and help them learn from it. An retrospective is not done properly if it doesn't also result in some improvement actions.
I've used Norm's exercises in my own retrospectives and they work exceptionally well. This book is therefore a treasure of practical advise. If you feel uncomfortable when reading the first description (as some exercises might), try not to discard the exercise, but try it out. Often you will learn and find that they work surprisingly good.
In the world of Agile Development, retrospectives have become an essential part of any agile method. These retrospectives are iteration retrospectives (or heartbeat retrospectives). They are shorter, but the ideas are the same. Much of Norm's exercises can also be used in that context.
As mentioned earlier, a must read for anyone serious in product development.
A retrospective is different than a post-mortem in that a post-mortem sometimes implies that the project was a failure. Kerth makes it clear that as long as knowledge is gained from mistakes made, and that steps are taken to avoid the repetition of those mistakes, then no mistake is a total failure.
Much of what Kerth writes about involves the tools and techniques of a facilitator. A facilitator is something like a psychotherapist for project teams. The facilitator's purpose is to get the members of the team, who sometimes do not work closely together either out of circumstance or preference, to share their opinions and observations about different aspects of the project in a non-threatening way.
A facilitator must be an excellent communicator and should not offer his or her own opinion, only help others to express their own. In Kerth's opinion, much of what makes a project successful involves interpersonal communication and through a project retrospective a facilitator can help a project team improve their communication skills.
I felt that the book offered some excellent suggestions. In particular, I liked Kerth's suggestions for illustrating to management of the value of a project retrospective. He provides an excellent checklist for preparing a proposal to management.
I also liked his suggestions for demonstrating to project teammembers the value of failure. One suggestion is to have everyone watch a movie that involves project management, such as Kerth's favorite, Flight of the Phoenix. Another of Kerth's suggestions is to discuss the explosion of the space shuttle Challenger. Kerth suggests pointing out how the fact that four of the five books written on the explosion are oriented toward children shows how our culture shuns failure, and then discussing how analyzing the causes of the explosion helped NASA prevent similar accidents in the future.
The book is intended for those intent on performing in-depth project retrospectives or project post-mortems. Much of the book consists of specific tips and techniques for those facilitating retrospectives. If I have a criticism of the book it is that much of the book is at a very practical level and that too little time is spent discussing how to make use of information garnered from project retrospectives in future projects.
Top reviews from other countries
Using the workshops suggested in this book I have seen some fantastic insights in to projects, and they are always fun to do!
Peter Taylor
[]
The lazy project manager: How to be twice as productive and still leave the office early
Allerdings darf man den Marketingsatz auf dem Buchcover ("belongs in the library of every project manager, for any kind of project") aus zwei Gründen nicht wirklich ernst nehmen: Einerseits handelt es sich eher um Tipps für Freelancer, die nicht am Projekt beteiligt waren und nur das Project Review durchführen (Norman Kerth geht auch mehrfach deutlich darauf ein, dass die Moderation des Reviews ein Außenstehender vornehmen sollte), andererseits sind die Beispiele stark auf Softwareprojekte und die daran beteiligten Personen zugeschnitten (weil das eben seine Erfahrungswelt ist).
Der Aufbau des Buchs ist gut gewählt. Nach einem groben Überblick über den Ablauf eines Reviews geht er in den späteren Kapiteln dann ins Detail, beschreibt die Durchführung einzelner Übungen und gibt Ratschläge, wann diese hilfreich oder angemessen sind und wann nicht. Dabei kommen auch Aspekte wie das Selling ("Warum denn ein Review? Ist doch nur Zeitverschwendung...") und die viel gerühmten Soft-Skills (Umgang mit den Teilnehmern, Auflockern der Atmosphäre) zum Tragen. Zu guter Letzt liefert er dann noch Beispiel-Zeitpläne und Protokollvorlagen.
Warum dann nur vier Sterne? Weil sich das Buch zu sehr um die Erlebnisse von Norman Kerth dreht. Das ist zwar authentisch, leicht zu lesen und sicher deutlich hilfreicher als die Ausführungen eines Theoretikers, welcher nur meint, das Handwerk zu beherrschen. Es schränkt die direkte Zielgruppe jedoch meiner Meinung nach etwas ein. Zu guter Letzt schreibt er ja aber selbst, dass man sich bei seinen Recherchen mehrerer Quellen bedienen sollte. Von daher kann man dem Autor definitiv keinen Vorwurf machen und etwas Gedankentransfer zu Nicht-Softwareprojekten hin kann man dem einen oder anderen sicher zutrauen ;-)
Was man hier noch neues lernt: Kerth geht sehr genau auf den gemeinsamen Lernprozess des Teams ein, und erklärt, was in so einem Softwareprojekt psychologisch und sozial mit dem Team passieren kann, und wie er verschiedene Elemente seiner Retrospektiven benutzt, um das Team wieder zusammen zu bringen und Wunden zu heilen. Wichtig ist dabei, dass man bei einer Projekt-Retro deutlich mehr Zeit braucht, als bei einer Iteration, nämlich etwa 2-3 Tage. Gerade in Projekten, wo sie ein starkes wir-ihr Verhältnis herausgebildet hat, und wo man in der nächsten Runde besser zusammenarbeiten will, lohnt es sich auf jeden Fall, eine Projekt-Retrospektive nach diesem wunderbaren Buch durchzuführen.
Den gezeigten professionellen, maximalistischen Ansatz und Mindset kann ich nicht nur in Retrospektiven sondern in alle Arten von Workshops anwenden.


