liveBook · Manning

Retrospective

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A retrospective is a recurring team meeting for examining recent work and agreeing on improvements to future collaboration or delivery.

A retrospective is a deliberate review after a collaborative modeling session. The people who organized or facilitated the meeting examine what happened, what participants learned, and what should change next time. section 4.1.2 section 4.6

A useful retrospective asks:

  • What went well, and what could have gone better? section 4.6.1
  • What did participants learn, and what concerns require follow-up? section 4.6.1
  • Can people execute and follow up on the decisions that were made? section 4.6.1
  • What should be communicated, documented, or changed before another session? section 4.6.1

A practical sequence

After participants leave, the organizers clean up, preserve photographs of physical visuals, compare their observations and feedback, and discuss follow-up. Each facilitator first records immediate observations and feelings, then waits at least a day before evaluating them with others. This preserves early insights while allowing time to notice bias. The group can then decide whether to document outcomes, communicate concerns, address unspoken tensions, or adapt the next collaborative modeling session. section 4.6 section 4.6.1

Skipping the retrospective may produce a short-term gain while allowing the organization to return to its previous behavior. Later, participants may doubt whether the session changed anything. Early feedback instead reveals resistance, social dynamics, or an unsafe environment for failure, allowing the group to adjust. section 4.6.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Explains timing, participants, reflection questions, bias control, follow-up, and consequences of omission.
Examples
Uses session observations, participant feedback, photographs of physical visuals, a canvas, follow-up concerns, and premortem outcomes.
What it assumes
Assumes a completed collaborative modeling session and people responsible for facilitating, organizing, or following up its outcomes.
What you can do after
Diagnose collaboration problems, validate follow-up responsibilities, and adjust future sessions or organizational behavior.
How it connects
Connects collaborative modeling with facilitation, feedback, decision-making, documentation, communication, and social dynamics.

Also explained in

Compare how 5 books explain retrospective →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.