Quarterly Agile Health Check

Template Overview

High-performing engineering teams require periodic honest reflections on their working culture, autonomy, and operational friction. The Quarterly Agile Health Check template provides an established framework to measure team health across 8 core dimensions, converting subjective team sentiment into actionable systemic improvements.

Markdown Template Structure

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

---
title: "Agile Health Check: [Team Name] - [Quarter / Year]"
date: [YYYY-MM-DD]
team: "[[Core Engineering Team]]"
facilitator: "[[Agile Coach Name]]"
participants_count: 8
composite_health: "Strong / Stable / At Risk"
tags: [agile, health-check, culture, team-dynamics, retrospective]
---

# Quarterly Agile Health Check — [Team Name]

## 1. Multidimensional Team Health Scorecard
| Dimension | Rating (Green / Amber / Red) | Trend vs Last Quarter | Primary Qualitative Driver |
|---|---|---|---|
| **Delivery Autonomy** | 🟢 Green | Improving | Team decides architecture without micromanagement |
| **Psychological Safety** | 🟢 Green | Stable | Blameless culture during outages is widely trusted |
| **Mission & Purpose** | 🟢 Green | Improving | Clear excitement about sovereign local-first mission |
| **Codebase Health** | 🟡 Amber | Declining | Technical debt accumulating in legacy test harnesses |
| **Meeting Load** | 🔴 Red | Declining | Context switching has risen from secondary committee syncs |
| **Release Confidence** | 🟢 Green | Stable | Zero-downtime release automation is highly dependable |
| **Peer Support & Pairing** | 🟢 Green | Stable | Strong cross-timezone mentorship and pairing habits |
| **Sustainable Pace** | 🟡 Amber | Declining | Occasional late-night Slack messaging creeping back |

## 2. Deep-Dive Discussion Themes
- **Theme 1: Meeting Overload (🔴 Red):**
  - *Observation:* Engineers report an average of 4.2 hours of fragmented meetings per day, leaving insufficient blocks for deep systems programming.
  - *Remediation Consensus:* Establish "Focus Wednesdays" — an absolute company-wide freeze on internal recurring meetings.
- **Theme 2: Codebase Technical Debt (🟡 Amber):**
  - *Observation:* The legacy end-to-end test harness has high flakiness, causing developer frustration.
  - *Remediation Consensus:* Dedicate 20% of every sprint over the next quarter strictly to test suite modernization.

## 3. Team Improvement Action Commitments
- [ ] [[Engineering Lead]] Institute Focus Wednesdays and cancel 3 redundant weekly status calls.
- [ ] [[Test Architect]] Rewrite the flaky audio stream test harness in native Swift/TypeScript.
- [ ] Re-assess health indicators in 90 days at the next quarterly health check.

Filled Real-World Example

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

---
title: "Agile Health Check: Systems Core - Q4 2026"
date: 2026-10-09
team: "[[Systems Core]]"
facilitator: "[[Sarah Sterling]]"
participants_count: 7
composite_health: "Strong"
tags: [agile, health-check, culture, retrospective]
---

# Quarterly Agile Health Check — Systems Core

## 1. Summary
Sarah Sterling facilitated the Q4 health check. Psychological safety and mission alignment scored uniformly Green. The team expressed great pride in delivering on-device transcription without external bots.

## 2. Action Items
To address the Amber rating on Codebase Health, the team committed to dedicating the entire first sprint of November to technical debt reduction and refactoring the SQLite wrapper.

When to Use and When to Avoid

When to Use

• Use once per quarter to assess holistic team health, culture, and sustainable pace.
• Use to identify systemic friction before it causes developer burnout or attrition.
• Use to empower engineering teams to adjust their own operational processes autonomously.

When to Avoid

• Avoid using as an individual performance evaluation metric.
• Avoid conducting during active production incidents (wait for operational calm).

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the agile health check audio recording:
1. Extract ratings (Green / Amber / Red) across all evaluated team dimensions and note trends.
2. Summarize key discussion themes regarding meeting load, technical debt, and team autonomy.
3. Itemize agreed systemic team improvement commitments and assigned owners.
Output in clean, structured Markdown.

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