Quarterly Retrospective Radar

Template Overview

While two-week sprint retrospectives address tactical frictions, quarterly retrospectives provide macro perspective on engineering health, architectural debt, and team sustainable pace. The Quarterly Retrospective Radar template evaluates five core dimensions of developer satisfaction and operational velocity.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Quarterly Retrospective Radar: [Quarter YYYY]"
date: [YYYY-MM-DD]
facilitator: "[[Agile Coach / Lead]]"
team: "Full Engineering Organization"
review_period: "Q3 2026 Macro Retrospective"
tags: [retrospective, agile, radar, engineering-health, kaizen]
---

# Quarterly Retrospective Radar — [Quarter YYYY]

## 1. Radar Dimension Scoring (Scale 1–5)
| Dimension | Q2 Score | Q3 Score | Trend | Primary Qualitative Driver |
|---|---|---|---|---|
| **Codebase Health & Craft** | 3.4 | 4.2 | 🔼 +0.8 | Monorepo consolidation and brand-free code linting |
| **Release Confidence** | 2.8 | 4.6 | 🔼 +1.8 | Automated 24-gate SEO check and negative test suite |
| **Team Autonomy & Agency** | 3.8 | 4.0 | 🔼 +0.2 | Clear architecture decision boundaries |
| **Developer Ergonomics (CI)** | 2.5 | 3.0 | 🔼 +0.5 | Caching improvements helped, but CI queue times lag |
| **Sustainable Pace & Well-Being**| 4.1 | 3.9 | 🔽 -0.2 | Context switching during multi-milestone sprints |

## 2. What Went Exceptionally Well
- Shipped 115 competitor pairwise comparison guides and expanded help center to 60 technical articles.
- Maintained 100% automated SEO gate pass rate with zero regression outages.
- On-device Whisper transcription proved rock-solid across varied Apple Silicon hardware.

## 3. What Created Friction & Fatigue
- Juggling simultaneous content generation milestones with deep CoreAudio driver bug-fixing.
- Flaky macOS virtualized CI runners causing spurious build reruns.

## 4. Continuous Improvement Experiments for Next Quarter
### Experiment 1: Dedicated Hardware CI Runners
- **Hypothesis:** Migrating test suites to dedicated Mac Studio runners will cut CI times from 11m to sub-3m.
- **Owner:** [[Devin Zhao]]
- **Review Date:** Mid-quarter checkpoint.

### Experiment 2: Protected Deep Work Fridays
- **Hypothesis:** Designating Fridays as zero-meeting focus days will restore sustainable pace metrics above 4.5.
- **Owner:** [[Elena Rostova]]
- **Review Date:** End of quarter.

## 5. Team Commitments
- [ ] Adopt dedicated Mac hardware CI runner pilot next week.
- [ ] Enforce zero scheduled meetings on Fridays starting this cycle.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Quarterly Radar: Q3 2026"
date: 2026-10-06
facilitator: "[[Marcus Vance]]"
tags: [retrospective, agile, radar]
---

# Quarterly Radar: Q3 2026

## 1. Retrospective Outcome
Marcus Vance led the team through the Q3 Radar scoring. Release confidence showed the highest improvement (jumping from 2.8 to 4.6) due to automated verification scripts and pre-commit gate checking.

When to Use and When to Avoid

When to Use

• Use at the end of each quarterly engineering cycle to reflect on macro operational trends.
• Use to benchmark developer satisfaction, code quality, and release confidence over time.
• Use to establish structured organizational experiments with explicit success metrics.

When to Avoid

• Avoid using for rapid two-week tactical sprint retrospectives.
• Avoid using for individual employee compensation appraisals.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the quarterly retrospective recording:
1. Extract numerical ratings and qualitative commentary across all discussed radar dimensions.
2. Summarize top accomplishments and systemic operational frustrations raised by engineers.
3. Outline proposed continuous improvement experiments, assigned champions, and review dates into Markdown.

Your data remains securely on your Mac with zero cloud exposure.