Agile Center of Excellence Retrospective

Improve how agile works across every team you support.

Try this retrospective live

Value We're Delivering

What impact is the center having on teams?

Our coaching clinics have helped three new teams reach a stable, predictable velocity.
The shared definition of done template is now adopted by most product teams, and consistency is finally improving.
Leadership is starting to ask us for guidance early, instead of after things go wrong.
Practices to Refine

Which agile practices need more consistency or rethinking?

Estimation practices vary wildly between teams, which makes program-level forecasting unreliable.
Some teams treat the retrospective as optional. We need to reinforce why it matters.
Our coaching is too reactive; we jump in to firefight instead of building lasting capability.
Organizational Impediments

What systemic blockers sit beyond any single team?

Annual budgeting cycles clash with our quarterly planning and force teams into fixed scope.
Shared services teams are a constant dependency bottleneck across every program.
Middle management still measures success by utilization, which undermines flow.
Improvement Experiments

What should we try next to grow agile maturity?

Pilot a paired-coaching model where two coaches support one team for a full increment.
Introduce a lightweight, organization-wide agile health check each quarter.
Run a 'dependency mapping' workshop with the three teams most blocked by shared services.

What is the Agile Center of Excellence Retrospective?

An Agile Center of Excellence (ACoE) brings together coaches, Scrum Masters, agile leaders and practitioners to improve how agile is practiced across an organization. This retrospective gives that group time to look at its own work: the standards it sets, the coaching it runs and the support it gives teams. The point is to find out what is actually moving teams forward and what is getting in their way. It runs above the level of a single sprint. The board has four columns: Value We're Delivering, Practices to Refine, Organizational Impediments and Improvement Experiments. Participants look at the impact the center is having, where practices have drifted or vary between teams, which blockers no single team can remove, and what to try next. Looking for patterns across teams, not one-off events, lets the ACoE spend its effort on the changes that help many teams at once. You come out with a short, prioritized improvement backlog the whole community has agreed on. Run it quarterly, after a major program increment or as part of your community-of-practice cadence, and you'll have a regular record of whether the center is making a difference. If you scale with SAFe, it fits alongside SAFe's communities of practice and its Lean-Agile Center of Excellence.

Agile Center of Excellence retrospective format

Value We're Delivering

What impact is the center having on teams?

Capture the value the center is giving teams and the wider organization, including what's hard to measure. Ask for coaching outcomes, new capability and adoption wins, not activity counts. Prompt with "How do we know we made a difference?" and ask for an example or signal behind each claim.

Practices to Refine

Which agile practices need more consistency or rethinking?

Surface the standards, frameworks or coaching approaches that aren't landing, or that teams apply in different ways. Keep it constructive: the aim is to refine, not to blame. Ask "Where are we seeing drift, confusion or copy-paste agile?" and look for patterns that show up in more than one team.

Organizational Impediments

What systemic blockers sit beyond any single team?

This column is for the blockers individual teams can't fix on their own, such as funding models, dependencies, tooling or leadership behavior. Write them down clearly so you can escalate them with evidence. For each one, ask who needs to be involved to remove it, so the column doesn't turn into a list of complaints.

Improvement Experiments

What should we try next to grow agile maturity?

This is where the session turns into action. Steer the group toward concrete, testable experiments, each with an owner and a way to measure success. Ask "What's the smallest change we could try next cycle, and how will we know it worked?" Pick a 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 look at its impact and reset priorities.
  • When agile practices have drifted or vary between teams and you need to agree on standards again.
  • When the same impediments show up in several teams and need fixing at the organization level.
  • As a regular check-in for a community of practice or center of excellence that needs to show leadership what it delivers.
  • During an agile transformation, to track maturity, capture lessons and plan the next round of coaching and training.

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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Stay on cross-team patterns and out of the details of any one team's sprint. That's the level this retro is for.
  • Invite coaches, Scrum Masters and agile leaders, plus a few practitioners from the teams you support, so you hear how the center's work lands from outside it.
  • Back up impediments and value claims with evidence where you can. Adoption or maturity data makes an escalation far more persuasive to leadership.
  • Commit to a small number of experiments so the center can deliver them and measure the results next cycle.
  • Watch for the echo chamber. Agile enthusiasts can celebrate practices that teams quietly find a burden, so ask for dissenting views.
  • Give every action an owner and a success signal, so the next retro reviews progress instead of reopening the same discussions.

Frequently asked questions

What is an Agile Center of Excellence retrospective?
It's a retrospective for the group that leads agile practice across an organization, usually coaches, Scrum Masters and agile leaders. It covers the value the center delivers, how consistent practices are, systemic impediments and the next experiments to try.
How is this different from a regular sprint retrospective?
A sprint retrospective looks at one team's recent work. This format looks at patterns across teams and the organization: agile maturity, coaching and the blockers that sit above any single sprint.
Who should attend an Agile Center of Excellence retrospective?
Invite agile coaches, Scrum Masters, Release Train Engineers, agile leaders and a handful of practitioners from the teams you support. The team-level voices stop the community from only testing its own assumptions.
How often should we run it?
Quarterly suits most centers of excellence, or you can line it up with your program increment boundaries. A steady cadence lets you track maturity over time and check whether past experiments worked.
How long does it take?
Allow 60–90 minutes. With a large group or several pressing impediments, book up to two hours so there's time to prioritize and assign owners.
How do we make the outcomes actionable?
Turn the top improvements into a few experiments, each with an owner and a measurable success signal. TeamRetro tracks them as action items, and you review them at the start of the next retrospective.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live