Understanding Retrospective

Mirror, mirror, on the wall

A Principle of Agile is “how the team reflects, and how it can become more effective, and adjust accordingly“. From Scrum, this reflection and adaption is a meeting called a “retrospective” (or “retro” for short). Kanban and DevOps both require some form of collaborative feedback session. Despite recognition, the retro has the potential to be a driving force of continuous improvement, often these meetings are seen as unnecessary, unproductive and unpleasant.

To re-establish the Retro as an important part of agility Ammeon have produced a short slide deck on Running RetrospectivesThis is a short guide as to what a retro is?, why it is needed?, who needs to attend?, where (in what conditions) to run one?, when (how often) to run one? and how to do it?. It is a distillation of writings from Lyssa Adkins, Esther Derby, Diana Larsen, Norm Kerth and Luís Gonçalves among others. You can download it here.

Don’t look back in anger

Have your existing retros become stale? or descended into negative blame-fests?, use the deck to restate the Prime Directive and use the links on the third last slide to convert the retro aftertaste from bitter lemon to tasty cupcake.

If you are a new scrum master or team lead looking to facilitate retrospectives (as well as planning, review and day-to-day activities), book a place on our Scrum Master training.

 

Picture Reference:

Rearview view by Anna

Tags: , , ,