Skip to content
Try an example
Early preview Nothing here is released yet. Pages marked Garden are drafts that no person has reviewed. How review works

Turn a retrospective into assigned improvements

← Explore patterns and cases

Reference eligibility: eligible — Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.

This is a retained audit record, not an eligible reference example. Inspect source eligibility.

administration/project coordination / svc-19

Turn a retrospective into assigned improvements

A facilitated retrospective elicits team experience and assigns fixes before the next cycle.

documented-procedure · · Source account, not a validated implementation

What goes in

  • Recent work experience
  • Team observations

What comes out

  • Assigned improvement list

Documented sequence

Order described in the source account; not a sequence between pattern families.

  1. Choose broad discussion questions.
  2. Each person records responses.
  3. Discuss issues together.
  4. Choose improvement actions.
  5. Assign actions to team members.
  6. Aim to complete them before the next retrospective.

Checks described

  • Open atmosphere lets all participants contribute.

What changes with context

  • Regular iteration-based meetings
  • End-of-phase reviews may include external disciplines.

Shared patterns · provisional interpretation

  • Investigate needs through inquiry

    Uncertain needs or situation → questions, responses, and a progressively clarified account

  • Coordinate commitments to closure

    An objective involving people or teams → accountable next actions, handoffs, tracking, and agreed closure

Fit: mapped. Exploratory analyst coding of collected source summaries; not independently tested

Could this transfer?

Hypothetical: A sales team could review a campaign and assign process changes.

Limit: An action list without follow-through is not evidence of improvement.

Evidence limits and unknowns

  • Action completion rate
  • Specific facilitation conflicts

Source eligibility and effectiveness

Allowed use: process reference with explicit limits . Source eligibility is not proof of effectiveness, safety or transferability.

Review attribution: AI-assisted source review · 2026-10-18T03:26:44.526806+00:00.

  • Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.
  • No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.
  • Action completion rate
  • Specific facilitation conflicts
  • An action list without follow-through is not evidence of improvement.

Source and dates

Agile tools and techniques ↗ · Government service manual

Published
2016-02-16
Updated
2026-03-31
Checked (UTC)
2026-10-18T03:00:27Z

conflicting_first_publication_history_entry: 2016-01-05

Original GOV.UK Updates to this page labels Published: 16 February 2016 and Last updated: 31 March 2026. The same history lists 5 January 2016 as Guidance first published. Both indicators are preserved; original publication conflict remains unresolved.

verified dates with publication conflict · Date evidence ↗

Permanent case link · Download source records