---
id: productivity-standup-retro-patterns
title: Standup / Retro / 1-on-1 patterns
category: Coding
status: draft
source_trust_level: B
verification_status: conceptual
created_at: 2026-05-09
updated_at: 2026-05-09
tags: [productivity, meeting, agile, vibe-coding]
tech_stack: { language: "process", applicable_to: ["Engineering"] }
applied_in: []
aliases: [standup, daily standup, retro, retrospective, 1-on-1, async standup, lean coffee]
---

# Standup / Retro / 1-on-1

> 작은 sync 가 큰 가치. **Async standup, retro template, 1-on-1 frequent**. 잘 못 하면 시간 낭비. 잘 하면 trust + alignment.

## 📖 핵심 개념
- Standup: 매일 (15 min).
- Retro: cycle 끝 (30-60 min).
- 1-on-1: 매주 (30 min, manager + report).
- Async > sync (multi-timezone).

## 💻 코드 패턴

### Daily standup (sync)
```
매일 9:30 AM, 15 min.
매 사람:
1. Yesterday: 한 거
2. Today: 할 거
3. Blocker: 막힌 거

→ Status update 만. 토의 X.
```

### 함정
```
- 30 min 길어짐 = 토의 빠짐
- 매 사람 가 detail 너무
- "아무도 안 들어"

→ Async 가 답.
```

### Async standup (Slack)
```
매 사람 매일:
@daily-standup
yesterday: PR #123 review, ENG-456 in progress.
today: finish ENG-456, start ENG-789.
blocker: waiting on design from @bob.
```

→ Geekbot / Slackbot 가 매일 prompt.

### Standup bot (Geekbot, Standuply)
```
매 9 AM Slack DM:
"yesterday?"
"today?"
"blocker?"

→ 답 가 channel post.
@team 가 검색 가능.
```

### Standup 안 함 (work)
```
Daily commit 가 standup.
PR description 가 status.
GitHub Projects 가 visible.

→ "왜 standup?" 다시 검토.
```

### Retro 표준 format (Start / Stop / Continue)
```
Start: 안 했지만 해야 하는 거.
Stop: 그만 해야 하는 거.
Continue: 잘 하는 거 — 계속.

→ 30 min:
- 5 min: silent write
- 15 min: share + discuss
- 10 min: action items
```

### "What went well / What didn't / Try next"
```
What went well: 칭찬 / win.
What didn't: 문제.
Try next: action.

→ Start with 좋은 것 — psychological safety.
```

### Lean coffee
```
- 매 사람 가 topic 제출 (sticky note)
- Vote (3 dot)
- 8 min 토의 / topic
- Vote: continue 8 min 또는 다음

→ Self-organize. 작은 팀 친화.
```

### Sailboat
```
Wind (도와준 거): tail wind.
Anchor (느리게 한 거): drag.
Rocks (위험): obstacle.
Island (목표): destination.

→ Visual. New 팀.
```

### Retro 함정
```
- 매번 같은 issue (action 없음)
- Solution 없는 complaint
- Manager 만 talk
- Anonymous 없음 = 침묵
- Action item 가 다음 cycle 잊음

→ 매 retro 시작 = "지난 action items?"
```

### Action items
```
매 retro 끝 = 1-3 명시적 action.
- Owner (1 명)
- Due (다음 cycle)
- Specific (vague X)

❌ "Better testing"
✅ "Alice writes 5 integration tests for auth by 2026-05-23"
```

### Anonymous retro
```
Retro tool: Miro / FunRetro / Parabol / Reflectly.
- Anonymous 작성
- Vote
- Group similar

→ 솔직 의견.
```

### 1-on-1
```
매주 30 min.
Manager + report.

Format:
1. Personal (5 min)
2. Project (10 min)
3. Career / growth (10 min)
4. Feedback 양방향 (5 min)

→ Cancel 안 하기. 의무.
```

### 1-on-1 agenda (shared doc)
```markdown
# Alice + Bob 1-on-1

## 2026-05-09
### Topics (Alice)
- Promotion timeline
- Question about XYZ project

### Topics (Bob)
- Feedback on PR style
- Q2 goal alignment

### Action items (last week)
- [x] Bob: send refactoring guide
- [ ] Alice: complete training

### Notes
...
```

→ Persistent. Trend 가 visible.

### 1-on-1 함정
```
- Status update 만: standup 식 = 가치 X.
- Manager 만 talk: report 가 의제.
- Cancel 자주: trust ↓.
- Career 안 토의: short-term 만.
- 침묵: weekly 는 너무 자주? bi-weekly OK.
```

### Skip-level 1-on-1
```
Manager 의 manager + IC.
- 매 quarter 1회
- 직접 보고 채널
- Manager 우회 X (manager 도 알고)

→ 큰 조직 의 transparency.
```

### Cross-functional sync
```
Engineering + Design + PM:
- 매 주 30 min
- Roadmap alignment
- Blocker
- Cross-team dependency
```

→ 작은 팀 = 안 필요. 큰 = 필수.

### Project kickoff
```
새 큰 project:
- Goal
- Scope (in / out)
- Timeline
- Owner / RACI
- Risks
- Success metric

→ 1 hour. Doc 보존.
```

### Project closeout / postmortem
```
Project 끝:
- 무엇 만들었나?
- Goal 달성?
- Blocker?
- Learning?

→ 다음 project 의 input.
```

### Async meeting
```
"meeting 가 doc 가 있어 안 모이면 안 되나?" 검토.

→ Status / share = doc.
Decision = 짧은 sync.
Brainstorm = sync (더 좋음).
```

### No-meeting day
```
"화요일 / 금요일 = no meeting."

→ Deep work 시간.
Manager 도 metric 가 다른 day.
```

### Standup vs PR review
```
PR review 가 standup 보다 informative.
- 코드 의 진짜 진행
- Async
- Search 가능

→ PR review 활발 = standup 작아져도 OK.
```

### Pair programming 가 sync
```
Daily standup ≠ pair.
Pair = work, standup = status.

→ 둘 다 가능.
```

### Demo day
```
매 cycle 끝, 30 min.
매 사람 가 작업 demo.
- Visual
- Customer-facing 강조
- 5 min / 사람

→ Cross-team awareness.
```

### Quarterly all-hands
```
매 분기 1회, 1 hour.
- Company update (CEO)
- Engineering update (CTO)
- Customer voice (CS)
- Q&A

→ 큰 회사. Async = video record.
```

### 비동기 가능 vs 안 됨
```
비동기 OK:
- Status update
- 결정 share
- FYI

비동기 어려움:
- Brainstorm (high bandwidth)
- Conflict resolution
- 1-on-1 (relationship)
- 새 사람 onboarding (early)
```

### Tools
```
- Geekbot (async standup)
- Donut (random pairing)
- Lattice / Bonusly (1-on-1)
- Miro / Parabol (retro)
- Loom (async video)
```

### Remote-first
```
- Video on (default)
- Equal participation (모든 사람 in person 또는 모두 remote)
- Recording + transcript
- Doc 가 source of truth (chat 가 ephemeral)
```

### 매 meeting 가 의제
```
- Goal: "decide X"
- Pre-read
- Time-boxed
- Action items

→ "그냥 sync" 가 가짜 의제.
```

### Decision doc
```markdown
# Decision: Use Postgres

Date: 2026-05-09
Attendees: @alice, @bob
Status: Decided

## Context
...

## Options
1. Postgres
2. MySQL

## Decision
Postgres because ...

## Action
- @alice: setup
- @bob: migration plan
```

→ ADR 식. 미래 의 "왜 X?" 답.

## 🤔 의사결정 기준
| 상황 | 추천 |
|---|---|
| Daily sync | Async standup (Slack bot) |
| Cycle reflection | Retro (Start/Stop/Continue) |
| Manager + report | Weekly 1-on-1 (shared doc) |
| Big project | Kickoff + closeout |
| Cross-team | Bi-weekly sync |
| Distributed | Doc + async |
| 결정 | Decision doc / ADR |

## ❌ 안티패턴
- **Standup 30+ min**: 가치 X.
- **Retro 같은 문제**: action 없음.
- **1-on-1 cancel**: trust ↓.
- **All sync**: timezone 죽음.
- **No agenda**: time waste.
- **No action item**: meeting 끝 = forget.
- **Skip-level X**: hierarchical 단방향.

## 🤖 LLM 활용 힌트
- Async standup 가 modern default.
- Retro 는 action item 가 없으면 가짜.
- 1-on-1 = career + feedback (status X).
- Doc 가 meeting 보다 좋을 때 많음.

## 🔗 관련 문서
- [[Productivity_Code_Review]]
- [[Quality_Mentoring]]
- [[Productivity_Knowledge_Sharing]]
