Agile Center of Excellence Retrospective

Agile Center of Excellence retrospective format

Value We're Delivering

What impact is the center having on teams?

This topic captures the tangible and intangible value the Agile Center of Excellence is providing to the teams and the broader organization. Encourage participants to think about coaching outcomes, capability uplift, and adoption wins rather than just activity counts. Prompt the group with 'How do we know we made a difference?' and ask for concrete examples or signals of impact.

Practices to Refine

Which agile practices need more consistency or rethinking?

Use this topic to surface standards, frameworks, or coaching approaches that aren't landing as intended or are being applied inconsistently across teams. Frame it constructively — the goal is to refine, not to assign blame. Ask 'Where are we seeing drift, confusion, or copy-paste agile?' and look for patterns that appear in more than one team.

Organizational Impediments

What systemic blockers sit beyond any single team?

This topic focuses on the cross-cutting impediments that individual teams cannot resolve on their own — funding models, dependencies, tooling, or leadership behaviours. Capture these clearly so they can be escalated with evidence. Encourage participants to name the impediment and who needs to be involved to remove it, rather than just venting.

Improvement Experiments

What should we try next to grow agile maturity?

This is the forward-looking, action-oriented topic. Steer the group toward concrete, testable experiments with an owner and a way to measure success rather than vague intentions. Ask 'What's the smallest change we could try next cycle, and how will we know it worked?' Prioritize a focused few so the center doesn't overcommit.

When to use this retrospective

• Quarterly or after a major program increment, when your agile community wants to assess its collective impact and reset priorities.
• When agile practices have started to drift or feel inconsistent across multiple teams and you need to realign on standards.
• When recurring impediments span several teams and require systemic, organization-level solutions rather than local fixes.
• As a regular cadence for a community of practice or center of excellence to stay relevant and demonstrate value to leadership.
• During an agile transformation, to track maturity, capture lessons, and plan the next wave of enablement.

Suggested icebreaker questions

• If our Agile Center of Excellence were a superhero, what would its superpower be?
• What's one agile myth you wish you could permanently retire across the organization?

Ideas and tips for your retrospective meeting

• Keep the focus on systemic, cross-team patterns rather than diving into the details of any single team's sprint — that's what makes this retrospective valuable at the center level.
• Invite a mix of voices: coaches, Scrum Masters, agile leaders, and a few practitioners from the teams you support, so insights aren't filtered only through the community's own perspective.
• Back impediments and value claims with evidence or examples where possible; data on adoption or maturity makes escalations far more persuasive to leadership.
• Limit the number of improvement experiments you commit to so the center can actually deliver them and measure the outcomes next cycle.
• Watch for the echo chamber effect — agile enthusiasts can over-celebrate practices that teams quietly find burdensome, so actively seek dissenting views.
• Assign a clear owner and a success signal to every action so the next retrospective can review real progress rather than reopening the same discussions.

Frequently asked questions