Standard : Retrospective Action Completion Rate

Description

Retrospective Action Completion Rate measures the proportion of improvement actions identified in retrospectives that are completed within an agreed timeframe. It reflects how effectively teams convert reflection into action and how much priority is given to continuous improvement.

Tracking this metric helps teams close the loop on feedback, build trust in the value of retrospectives, and embed a culture of experimentation and accountability.

How to Use

What to Measure

  • Count the number of improvement actions raised in retrospectives.
  • Track how many are completed within a defined review period (e.g. next sprint, 30 days).
  • Optionally, include resolution status (done, partially done, deferred, dropped).

Formula

Completion Rate = (Number of Actions Completed on Time / Total Actions Raised) × 100

Segment by:

  • Team or delivery group
  • Sprint or iteration
  • Action type (technical, process, team, tooling)

Instrumentation Tips

  • Use team boards, issue trackers, or retro tools to capture and track actions.
  • Assign owners and review progress regularly in stand-ups or ceremonies.
  • Tag improvement actions consistently to distinguish them from delivery tasks.

Why It Matters

  • Builds trust: Teams are more engaged when they see their feedback leads to change.
  • Drives improvement: Continuous learning becomes operationalised and visible.
  • Supports focus: Reinforces retrospectives as more than reflection exercises.
  • Signals psychological safety: Teams feel safe to raise and address problems.

Best Practices

  • Treat improvement actions as first-class backlog items with clear acceptance criteria.
  • Keep actions small, scoped, and measurable to avoid stalling.
  • Use “show and tell” in retrospectives to reflect on completed improvements.
  • Review outstanding actions before planning to keep momentum.

Common Pitfalls

  • No follow-up on agreed actions, eroding belief in the process.
  • Overloading the team with too many actions at once.
  • Vague or unscoped actions that are hard to complete.
  • No visible tracking or ownership assigned.

Signals of Success

  • Most retrospective actions are completed promptly and visibly.
  • Teams report improvements in the same areas raised in prior retrospectives.
  • Improvement actions are celebrated and linked to outcomes.
  • Retrospectives are energising, focused, and data-informed.
  • [[Number of Learning Experiments per Quarter]]
  • [[Experiment-to-Adoption Ratio]]
  • [[CoE/Lean/Measures/Continuous Learning & Experimentation/Time Allocated to Improvement Work]]
  • [[Engineering Learning Hours per Person]]
  • [[Flow Efficiency]]