![](https://image.librarything.com/pics/fugue21/magnifier-left.png)
![](https://images-na.ssl-images-amazon.com/images/P/0932633447.01._SX180_SCLZZZZZZZ_.jpg)
Klik op een omslag om naar Google Boeken te gaan.
Bezig met laden... Project Retrospectives: A Handbook for Team Reviews (2001)door Norman L. Kerth
![]() Geen Bezig met laden...
![]() Meld je aan bij LibraryThing om erachter te komen of je dit boek goed zult vinden. Op dit moment geen Discussie gesprekken over dit boek. This is the first book that I have read on retrospectives, after having seen Norm Kerth on the SM/ASM conference in 2001 presenting about retrospectives. It's a classic, even if you do agile retrospectives, as it describes the basic concepts and ideas behind retrospectives. A must read for anybody of is working agile, and want to continuously improve the way of working! geen besprekingen | voeg een bespreking toe
With detailed scenarios, imaginative illustrations, and step-by-step instructions, consultant and speaker Norman L. Kerth guides readers through productive, empowering retrospectives of project performance.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 changes identified by the community will 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. Geen bibliotheekbeschrijvingen gevonden. |
Actuele discussiesGeen
![]() GenresDewey Decimale Classificatie (DDC)005.10684Information Computer Science; Knowledge and Systems Computer programming, programs, data, security Programming Programming -- Subdivisions Business & Organizations Management ExecutiveLC-classificatieWaarderingGemiddelde:![]()
Ben jij dit?Word een LibraryThing Auteur. |
The target audience for this book is people running project retrospectives. It provides a wealth of material on the purpose of retrospectives, preparing for them, running them, and improving them. To a large degree, the book is targeted even more specifically at professional retrospective facilitators. The upside of this focus is that Kerth gives a broad set of tools for structuring retrospectives and discusses the trade-offs of different activities in depth.
The downside is that Kerth takes a pretty strong position on retrospectives: they should last 2-3 days (preferably 3), preferably take place offsite, and be run by someone outside of the project team. While I understand his position that, as a professional facilitator, if those requirements cannot be met, it is not likely to be worth his time to facilitate, as a lead of a team, I would have liked more discussion of how to bridge the gap between those ideal conditions and the conditions I'm likely to encounter where we don't have as much time, offsite is possible but hard, and getting an external facilitator is challenging. I suspect that even under those challenging situations, having some retrospective-like process is valuable, even if it's not as valuable as what you can do under better conditions.
Overall though, this was a valuable read for anyone interested in how to structure effective retrospectives, even if you are unlikely to have them under ideal conditions. (