• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Retrospectives are used to guide systemic and team-level improvements

Purpose and Strategic Importance

This standard ensures retrospectives are consistently leveraged to drive meaningful improvements both at the team and systemic levels. Retrospectives provide structured opportunities to reflect on delivery, identify sources of friction or waste, and experiment with targeted improvements. When performed effectively, they foster a culture of ownership, trust, psychological safety, and relentless learning.

It supports our policies to “Reflect, Learn, and Improve Relentlessly” and “Make Continuous Improvement a Delivery Habit” by embedding deliberate improvement as a natural part of delivery flow. Without this, teams risk repeating mistakes, missing systemic patterns, and disengaging from continuous improvement.

Strategic Impact

  • Enables regular, data-informed continuous improvement
  • Strengthens team cohesion and psychological safety to raise issues openly
  • Surfaces and addresses systemic challenges beyond individual teams
  • Facilitates small, frequent improvements that compound to significant impact
  • Amplifies organisational learning through cross-team insight sharing

Risks of Not Having This Standard

  • Teams repeatedly encounter the same issues without resolution
  • Retrospectives degrade into perfunctory exercises with little follow-up
  • Improvement actions lack clarity, prioritisation, or accountability
  • Learning opportunities from failures are lost or ignored
  • Systemic impediments remain unchallenged due to siloed focus

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture - Retrospectives are sporadic, optional, or omitted.
- Feedback is informal and rarely results in change.
Process & Governance - No consistent format or cadence.
- Improvement ideas are undocumented and unmanaged.
Technology & Tools - Notes and outcomes are lost or poorly retained.
- Limited or no tooling support.
Measurement & Metrics - No tracking or visibility of improvement outcomes or trends.

Level 2 – Managed

Category Description
People & Culture - Retrospectives occur at iteration end.
- Teams identify issues but struggle to act on them consistently.
Process & Governance - Action items captured but infrequently reviewed or completed.
- Focus mostly on local, surface-level issues.
Technology & Tools - Basic collaborative tools (e.g., whiteboards, templates) are occasionally used.
Measurement & Metrics - Informal monitoring of action completion rates.
- Limited insight into recurring problems.

Level 3 – Defined

Category Description
People & Culture - Retrospectives valued as integral to delivery success.
- Psychological safety allows open issue discussion.
Process & Governance - Improvement actions prioritised, tracked, and systematically closed.
- Insights shared occasionally across teams.
Technology & Tools - Tools support collaboration, follow-up, and reporting of retrospective outcomes.
Measurement & Metrics - Metrics on improvement throughput, team satisfaction, and cycle trends reviewed regularly.

Level 4 – Quantitatively Managed

Category Description
People & Culture - Retrospectives explore systemic and cross-team patterns.
- Teams reflect on past action effectiveness.
Process & Governance - Outcomes influence delivery strategy and iterative planning.
- Cross-team retrospectives highlight systemic issues.
Technology & Tools - Platforms integrate retrospective data with backlog and delivery metrics.
Measurement & Metrics - Impact of improvements measured across time and teams, enabling data-driven decision making.

Level 5 – Optimising

Category Description
People & Culture - Retrospective practices evolve continuously to address team and organisational needs.
- Teams proactively experiment with new learning methods.
Process & Governance - Insights feed into governance, portfolio, and organisational learning cycles.
- Culture fosters transparent, shared learning.
Technology & Tools - Data analytics reveal organisational patterns and continuous improvement opportunities.
Measurement & Metrics - Continuous monitoring of action success rates, team resilience, and ROI of improvement initiatives.

Key Measures

  • Percentage of retrospective actions completed within the following iteration or cycle
  • Rate of recurring versus resolved issues over time
  • Frequency and consistency of retrospectives conducted per team
  • Cross-team identification and resolution rate of systemic issues
  • Team satisfaction scores reflecting perceived effectiveness of improvements
Associated Policies
Associated Practices
  • Safe-to-Fail Experiments
  • Iterative Learning Cycles
  • Actionable Retrospectives
  • Improvement Experiments as Work

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering