http://www.benlinders.com/2013/whats-an-agile-retrospective-and-why-would-you-do-it/
Retrospective a practice used by teams to reflect on their way of working, and to continuously become better in what they do.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Every retrospective meeting starts by looking at the actions from the previous meeting, to see if they are finished (and to take action if not).
It’s crucial to have an open culture in an agile retrospective, where team members speak up. Norm Kerth defined the Prime Directive, it’s purpose is to assure that a retrospective is a positive and effective event. With the Prime Directive, a retrospective becomes a effective team gathering where people learn from each other and find solutions to improve their way of working.
Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
http://www.benlinders.com/2013/which-questions-do-you-ask-in-retrospectives/
When I start with a team that is new to retrospectives, I often use The four key questions. These questions come from the book Project Retrospectives: A Handbook for Team Reviews, by Norm Kerth. he questions are:
- What did we do well, that if we don’t discuss we might forget?
- What did we learn?
- What should we do differently next time?
- What still puzzles us?
http://blog.pivotal.io/labs/labs/retro-best-practices http://blog.pivotal.io/labs/labs/fewest-possible-meetings http://blog.pivotal.io/labs/labs/happy-retro
http://blog.pivotal.io/labs/labs/retro-best-practices