Catalog
method#Delivery#Product#Governance

Retrospectives

Facilitated team meeting for continuous improvement of processes, collaboration, and outcomes.

Retrospectives are facilitated team meetings for continuous improvement of practices, processes, and collaboration.
Established
Low

Classification

  • Low
  • Organizational
  • Organizational
  • Intermediate

Technical context

Issue tracker (e.g. Jira) for follow-upConfluence or wiki for recording resultsRetrospective tools (e.g. Parabol)

Principles & goals

Respect the timeboxSafe environment (psychological safety)Focus on concrete, actionable improvements
Iterate
Team, Domain

Use cases & scenarios

Compromises

  • Retrospectives become ritual without real change
  • Lack of psychological safety prevents honest feedback
  • Actions remain incomplete or unowned
  • Strictly respect timebox and use focused agenda
  • Prefer concrete, small actions over vague wishes
  • Make results visible and follow up

I/O & resources

  • Sprint results and relevant metrics
  • Concrete observations from team members
  • External stakeholder feedback (if needed)
  • Prioritized list of actions with owners
  • Adjustments to team or process agreements
  • Documented insights for follow-up

Description

Retrospectives are facilitated team meetings for continuous improvement of practices, processes, and collaboration. They surface actionable improvements, reflect on past iterations, and foster a learning culture. With structured facilitation, prioritization and action tracking, improvements become tangible and can be shared across teams at the domain level.

✔

  • Continuous improvement of processes and collaboration
  • Transparency about problems and successes
  • Promotion of a learning culture

✖

  • Impact depends on genuine participation and follow-up
  • Can remain superficial without structured facilitation
  • Scaling across many teams requires additional coordination

  • Completed retro actions

    Share of actions implemented within agreed deadlines.

  • Team satisfaction

    Regular mood or satisfaction ratings before/after retros.

  • Reduction of recurring issues

    Number of recurring problem signals across iterations.

Feature team sprint retro

Small team uses timebox and Start/Stop/Continue to improve ways of working.

Incident retrospective

After a major production outage, causes are identified and stabilization actions are defined.

Cross-domain retro

Multiple teams synchronize dependencies and plan coordinated improvements.

1

Introduce: communicate goal and expectations.

2

Facilitation: assign facilitator and agenda.

3

Collect data: gather metrics and observations.

4

Run: analyze, discuss and derive actions.

5

Document: record results and owners.

6

Follow-up: track actions and review in next retro.

⚠️ Technical debt & bottlenecks

  • Untracked actions increase technical debt buildup
  • Recurring issues remain unresolved and accumulate
  • Missing automation for follow-up leads to information loss
Unclear ownershipLack of facilitation skillsMissing action follow-up
  • Using retrospectives as a status update
  • Handling only management topics without team involvement
  • Announcing actions but not following up
  • Planning too many actions at once
  • Not assigning clear ownership
  • Holding retros too infrequently so issues become stale
Facilitation skillsAnalysis and derivation of concrete actionsCommunication and feedback skills
TransparencyFast learning cyclesTeam ownership
  • • Limited meeting time (timebox)
  • • Availability of all relevant participants
  • • Organizational priorities may block actions