LOGIN

REGISTER
Seeker

Logistics of an Effective Retrospective

Select the language:

You must allow Vimeo cookies to view the video.

Unlock the full course and get certified!

You are viewing the free content. Unlock the full course to get your certificate, exams, and downloadable material.

*When you buy the course, we gift you two additional courses of your choice*

*See the best offer on the web*

Transcription Logistics of an Effective Retrospective


For a retrospective to be truly productive and not become a simple complaint session with no results, it is essential to pay attention to its logistics and facilitation.

A clear structure, proper time management, and a focus on generating and following through on concrete actions are key.

As the facilitator (a role often assumed by the Agile Coach or Scrum Master), you must prepare the session, guide the team through the different phases and ensure that actionable conclusions are reached.

The goal is to create a safe and efficient space for reflection and continuous improvement.

Phases: Warm-up, Brainstorming, Grouping/Voting (Optional), Actions.

A common structure for a retrospective (approximately one hour) includes the following phases:

Warm-up (approx. 5 min): start the session by briefly recalling the period to be reviewed (e.g., last Sprint) or conducting a short activity to focus the team. Key events that have occurred can be mentioned.

Brainstorming (approx. 10 min): Team members individually generate ideas (using post-its or virtual tools) based on the chosen format (e.g., What went right/bad, Start/Stop/Continue). It is important to limit the time to focus on what is most relevant.

Grouping / Discussion / Voting (Optional) (approx. 15-20 min): Ideas are shared, similar topics are grouped and discussed to ensure understanding.

Optionally, a vote can be taken to prioritize the topics to be discussed. However, some facilitators prefer to skip voting and discuss each point to derive actions.

Action Generation (approx. 20 min): This is the most crucial phase. For the issues discussed (or those most voted), the team defines concrete, specific and achievable actions to address the problems or implement improvements.

Assigning Responsibility and Action Follow-up

Generating action ideas is not enough; it is vital to ensure their implementation. To do this:

Assign an Owner: Each action item must have a clear responsible person within the team. This person does not necessarily execute the action alone, but is responsible for following it up and ensuring its progress.

Set Deadlines (Optional but Recommended): Defining deadlines or review times for actions helps to maintain momentum.

Review at the Next Retrospective: At the start of the next retrospective, the status of actions agreed upon in the previous session should be reviewed.

Completed actions are celebrated (and symbolically "destroyed" if post-its are used), pending ones are re-evaluated, and those that are no longer relevant are discarded. This follow-up closes the improvement cycle.

Documentation and Tools (Physical or Virtual)

Although the conversation is key, documentation of the retrospective, especially action items, is important for follow-up.

Physical Tools: Post-its, white boards, flip charts. They are tactile and visual for co-located teams. It is useful to take a photo at the end.

Virtual Tools: For


logistics of an effective retrospective

Recent publications by professional agile coach

Are there any errors or improvements?

Where is the error?

What is the error?