Scrum of Scrums Meeting Log

Template Overview

As engineering organizations scale beyond a single squad, cross-team dependencies become the primary source of sprint delivery delays. The Scrum of Scrums Meeting Log provides team ambassadors with a structured framework to map dependencies, resolve shared repository merge conflicts, and protect the release train.

Markdown Template Structure

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

---
title: "Scrum of Scrums: [Sprint Number / Milestone]"
date: [YYYY-MM-DD]
release_train_engineer: "[[Program Lead]]"
participating_squads: ["Squad Core UI", "Squad Systems Engine", "Squad Developer Platform"]
release_target: "v1.5 Release Candidate"
tags: [scrum-of-scrums, agile, scaled-agile, dependencies, coordination]
---

# Scrum of Scrums — [Sprint Number / Milestone]

## 1. Squad Status & Cross-Team Impact
### Squad 1: Core UI Applications (Ambassador: [[Julian]])
- **What we shipped:** Completed live-preview table navigation refactor and accessibility focus indicators.
- **What we are doing next:** Integrating the on-device AI Ask context drawer into the main note window.
- **What is blocking us from other teams:** Awaiting final IPC method from Systems Engine to stream LLM tokens.

### Squad 2: Systems Engine (Ambassador: [[Devin]])
- **What we shipped:** Upgraded Whisper CoreML inference engine; reduced p99 transcription latency by 18%.
- **What we are doing next:** Finalizing the streaming IPC channel for Core UI's Ask drawer.
- **Dependency for Core UI:** PR #182 delivers the streaming IPC method; unblocked by Wednesday.

## 2. Inter-Squad Dependency Matrix
| Producer Squad | Consumer Squad | Shared Artifact / API | Target Date | Status |
|---|---|---|---|---|
| **Systems Engine** | Core UI | Streaming IPC RPC Endpoint | Wednesday | On Track |
| **Developer Platform** | Core UI | Pre-compiled WebAssembly test runner | Friday | At Risk |

## 3. Global Release Train Impediments
- Shared CI test pipeline queues are experiencing 8-minute delays due to overlapping nightlies.
- Re-verified zero branch conflicts between staging and main release candidate branches.

## 4. Next Synchronization Cadence
Next Scrum of Scrums check-in scheduled for **Thursday at 14:00 UTC**.

Filled Real-World Example

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

---
title: "Scrum of Scrums: Sprint 44"
date: 2026-10-07
release_train_engineer: "[[Priya Patel]]"
participating_squads: ["Core UI", "Systems", "Docs"]
tags: [scrum-of-scrums, agile]
---

# Scrum of Scrums: Sprint 44

## 1. Dependency Resolution
Priya confirmed that the Documentation squad's 60 technical guides were successfully integrated into the desktop build without increasing binary footprint. Systems squad unblocked Core UI on the audio loopback driver.

When to Use and When to Avoid

When to Use

• Use during twice-weekly scaled agile coordination sessions between multiple engineering squads.
• Use when tracking cross-sprint dependencies and shared codebase integrations.
• Use to protect release train delivery dates from hidden architectural bottlenecks.

When to Avoid

• Avoid using for single-team daily standups.
• Avoid using for high-level company strategy planning (use quarterly offsites).

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the Scrum of Scrums coordination recording:
1. Summarize the progress, upcoming deliverables, and cross-team blockers for each participating squad.
2. Outline the dependency matrix commitments, noting which squads are producers and consumers.
3. List release train risks and scheduled unblocker dates into clean Markdown.

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