Engineering retro

Sprint-by-sprint retros that produce real change.

Sprint [N]

What worked

Keep doing.

What didn't

Change next sprint.

Lessons

Long-term takeaways. Promote to the team wiki if relevant.

Action items

Use the Action items surface. Columns: action, owner, due, status (open / in progress / done / dropped).

Every retro produces 2-5. The next retro reviews what's still open.

Carryover

Use the Carryover surface. Auto-populated from prior retro action items still open. The honest mirror — if the same action keeps carrying over, change the action.

Cadence

• End of every sprint: 30 min retro.
• Argus drafts the doc the night before from sprint outcomes.
• Action items reviewed first at the next retro.