Retrospective
The term is also used in software engineering, where a retrospective is a meeting held by a project team at the end of a project or process (often after an iteration) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects. Retrospective can be done in many different ways. The Agile Retrospective Resource Wiki is a resource for sharing retrospective plans, tips & tricks, tools and ideas to help us get the most out of our retrospectives. http://en.wikipedia.org/wiki/Retrospective#Software_development (cf Incident Analysis, Learning Organization, post-mortem)
goal: blame-less
Norm Kerth: Project Retrospectives: A Handbook for Team Reviews ISBN:0932633447
Esther Derby: Agile Retrospectives: Making Good Teams Great ISBN:0977616649
http://www.infoq.com/articles/agile-retrospectives-davies
http://www.methodsandtools.com/archive/archive.php?id=63
cf Five Whys
- I like a diagram of effects in a shared whiteboard to connect issues
Edited: | Tweet this! | Search Twitter for discussion