---
title: "Sprint planning"
excerpt: "Backlog, current sprint, retro — all in one workspace. Flint marks what shipped, Scout recaps the sprint at the end."
category: "Template"
---

# Sprint planning

Engineering sprint coordination — backlog, current sprint, retro in one place.

## Current sprint

Use the **Current sprint** surface. Each row: ticket, owner, points, status (todo / in-progress / shipped / cut).

## Backlog

Use the **Backlog** surface. Triage weekly — pull from here into the current sprint. Columns: ticket, priority, estimate, blocker.

## Retro

Use the **Retro** doc. Three sections per sprint:

- **What worked** — keep doing
- **What didn't** — change next sprint
- **Lessons** — long-term takeaways

Argus can draft the retro from the sprint outcomes when you ask.

## Cadence

- Sprint length: 2 weeks
- Planning: Monday morning
- Retro: Friday afternoon
- Demo: end of sprint