Retrospectives

Summary

Retrospectives are presented as a way for software engineering teams to review operational incidents, investigate root causes, create remediation tasks, and improve teamwork. Beyond technical review, the process can focus on emotional and human aspects of projects, including interactions and ways to work better together. The suggested timing includes post-incident or post-project sessions, mid-project course corrections, and weekly meetings; a 90-minute Friday session one week after a project ends is described as effective, while next-day and three-week delays are discouraged. An active, neutral facilitator should prepare an agenda and guest list, state a clear purpose, involve everyone, and use one or two activities such as a timeline, five whys, or Start Doing / Stop Doing / Keep Doing brainstorming.

Takeaways

1. 1

   Retrospectives can be held after incidents or projects, during a project to course-correct, or weekly; higher frequency also provides practice improving the retrospective process.

2. 2

   A 90-minute session on Friday afternoon, one week after a project ends, is described as effective; the post advises against holding it the next day or waiting three weeks.

3. 3

   Facilitators should remain neutral, ask questions of everyone, and use one or two structured activities to keep participants engaged and produce new insights.