Blog (EN)
2022-11-06 16:33

Retrospective as a way of synchronising and bringing team or family members closer, or a team and its goal

A retrospective is a look at the past. An agile team uses it in its routine work. The strength and agility of such teams lies in drawing conclusions quickly and “reassembling” in line with current realities.
A retrospective is wonderful before New Year! Such a festive analysis lets you enjoy the year’s successes and note the points of growth for the next.
A retrospective can cover DECADES. In that case only those events are recalled, and only by those who were direct participants. This very format allows old-timers to immerse newcomers and pass on to them the DNA of their activity.
A weekly retrospective is the shortest span I know of. It is a great way to keep track of the state of colleagues and of the project. This session can be held by a department or a small group. It can also suit family discussions at the end of the week — what worked and what did not, what was pleasing and what upsetting.
There are many templates for retrospective sessions. The most obvious are any variants of timelines. They can be decorated with various artistic drawings and storylines.
Retrospective sessions have every right to be short — about 45 minutes for the whole cycle, from individual recollection to team or family discussion.
A retrospective can become food for thought for a leader or a parent, and if you allow a little more time, you can immediately work out steps for resolving difficult situations that arose in the period under review. Then you can go through the full ORID cycle. What ORID is was described in one of the previous posts.
The technique for running a retrospective session is a “from the particular to the general” format, where everyone reflects individually on the question posed, and then the group assembles a shared vision or assessment of the period that has passed.