---
title: "Quarterly Cross-SDK Retro"
url: https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro/
---

# Quarterly Cross-SDK Retro

This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in

<!-- -->

[RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.

Statusdraft

Version`1.0.0`[(changelog)](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#changelog)

## [Overview](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#overview)

This playbook guides SDK teams through conducting a quarterly retrospective to identify and address cross-SDK process issues. It covers async question gathering, compilation, sync discussion, and actionable outcomes. By following these steps, teams continuously improve standards, playbooks, and collaboration patterns based on real experience.

Related resources:

* [Cross-SDK Coordination standard](https://develop.sentry.dev/sdk/getting-started/standards/coordination-maintenance.md#cross-sdk-coordination) — coordination process this retro evaluates
* [Aligning Cross-SDK Changes](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/aligning-cross-sdk-changes.md) — references this retro in step 8

***

## [Steps](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#steps)

#### [1. Each SDK team answers questions asynchronously](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#1-each-sdk-team-answers-questions-asynchronously)

Each SDK team **SHOULD** answer these questions in writing:

* What's the most common low-quality PR pattern we're seeing?
* What's the most annoying friction in our process?
* What standard or playbook is working well?
* What standard or playbook needs updating?
* Any regressions or incidents worth discussing?

This async format allows teams to provide thoughtful input on their own schedule.

#### [2. Compile answers into a shared document](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#2-compile-answers-into-a-shared-document)

You **MUST** consolidate all team responses into a single shared document for review before the sync meeting.

#### [3. Hold a focused sync meeting](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#3-hold-a-focused-sync-meeting)

You **SHOULD** hold a 30-minute sync meeting to discuss cross-cutting themes. This meeting **MUST** focus on patterns that affect multiple teams, not status updates.

The goal is to identify systemic issues and shared pain points, not to review every individual response.

#### [4. Create actionable outcomes](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#4-create-actionable-outcomes)

Based on the discussion, you **SHOULD** update:

* Standards that need revision
* Playbooks that need clarification or new content
* AGENTS.md files with improved instructions
* Saved replies for common scenarios

Document what will change and who owns each action.

#### [5. Track patterns across retros](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#5-track-patterns-across-retros)

You **SHOULD** review whether the same problems are recurring. If the same issue appears in multiple retros, the previous fix didn't work — try a different approach.

This meta-analysis helps identify deeper systemic issues versus one-time problems.

## [Referenced Standards](https://develop.sentry.dev/sdk/getting-started/playbooks/coordination/quarterly-cross-sdk-retro.md#referenced-standards)

* [Cross-SDK Coordination standard](https://develop.sentry.dev/sdk/getting-started/standards/coordination-maintenance.md#cross-sdk-coordination) — coordination process evaluated by this retro
* All standards and playbooks — this retro is the feedback loop for continuous improvement

***

| Version | Date       | Summary                                                                       |
| ------- | ---------- | ----------------------------------------------------------------------------- |
| `1.0.0` | 2026-02-23 | Initial playbook — quarterly retrospective for cross-SDK process improvements |