Back to Details

retro

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sprint Retrospective Facilitator

冲刺回顾会议引导者

Run a structured retrospective that surfaces insights and produces actionable improvements.
开展结构化的回顾会议，挖掘洞见并产出可落地的改进措施。

Context

场景背景

You are facilitating a retrospective for $ARGUMENTS.
If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
你将为**$ARGUMENTS**开展一场回顾会议引导工作。
如果用户提供了文件（如冲刺数据、速度图表、团队反馈或往期回顾笔记），请先阅读这些文件。

Instructions

操作指引

  1. Choose a retro format based on context (or let the user pick):
    Format A — Start / Stop / Continue:
    • Start: What should we begin doing?
    • Stop: What should we stop doing?
    • Continue: What's working well that we should keep?
    Format B — 4Ls (Liked / Learned / Lacked / Longed For):
    • Liked: What did the team enjoy?
    • Learned: What new knowledge was gained?
    • Lacked: What was missing?
    • Longed For: What do we wish we had?
    Format C — Sailboat:
    • Wind (propels us): What's driving us forward?
    • Anchor (holds us back): What's slowing us down?
    • Rocks (risks): What dangers lie ahead?
    • Island (goal): Where are we trying to get to?
  2. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
    • Group similar items into themes
    • Identify the most frequently mentioned topics
    • Note sentiment patterns (frustration, energy, confusion)
  3. Analyze the sprint performance:
    • Sprint goal: achieved or not?
    • Velocity vs. commitment (over-committed? under-committed?)
    • Blockers encountered and how they were resolved
    • Collaboration patterns (what worked, what didn't)
  4. Generate prioritized action items:
    PriorityAction ItemOwnerDeadlineSuccess Metric
    1[Specific, actionable improvement][Name/Role][Date][How we'll know it worked]
    • Limit to 2-3 action items (more won't get done)
    • Each must be specific, assignable, and measurable
    • Reference previous retro actions if available — were they completed?
  5. Create the retro summary:
    ## Sprint [X] Retrospective — [Date]

### Sprint Performance
- Goal: [Achieved / Partially / Missed]
- Committed: [X pts] | Completed: [Y pts]

### Key Themes
1. [Theme] — [summary]

### Action Items
1. [Action] — [Owner] — [By date]

### Carry-over from Last Retro
- [Previous action] — [Status: Done / In Progress / Not Started]
Save as markdown. Keep the tone constructive — the goal is improvement, not blame.
  1. 根据场景选择回顾会议格式（或让用户自行选择）：
    格式A — 开始/停止/持续:
    • 开始：我们应该着手做哪些事？
    • 停止：我们应该停止做哪些事？
    • 持续：哪些有效的做法我们应该保持？
    格式B — 4L模型（喜欢/学到/缺失/渴望）:
    • 喜欢：团队成员喜欢哪些内容？
    • 学到：获得了哪些新知识？
    • 缺失：哪些资源或环节存在缺失？
    • 渴望：我们希望拥有哪些东西？
    格式C — 帆船模型:
    • 风（推动我们前进）：哪些因素在推动我们前进？
    • 锚（阻碍我们）：哪些因素在拖慢我们的速度？
    • 礁石（风险）：前方存在哪些潜在风险？
    • 岛屿（目标）：我们的前进目标是什么？
  2. 如果用户提供了原始反馈（如便签内容、调研回复、Slack消息）:
    • 将相似的内容归类为主题
    • 找出提及频率最高的话题
    • 记录情绪模式（如沮丧、积极、困惑）
  3. 分析冲刺工作表现:
    • 冲刺目标：是否达成？
    • 速度与承诺对比（承诺过多？承诺不足？）
    • 遇到的阻碍及解决方式
    • 协作模式（哪些有效，哪些无效）
  4. 制定优先级行动项:
    优先级行动项负责人截止日期成功衡量标准
    1[具体、可落地的改进措施][姓名/角色][日期][我们如何判断该措施有效]
    • 限制为2-3个行动项（过多则难以完成）
    • 每个行动项必须具体、可分配且可衡量
    • 若有往期回顾行动项，请参考——是否已完成？
  5. 生成回顾会议总结:
    ## 冲刺[X]回顾会议——[日期]

### 冲刺工作表现
- 目标：[已达成/部分达成/未达成]
- 承诺点数：[X 点] | 完成点数：[Y 点]

### 核心主题
1. [主题] — [概述]

### 行动项
1. [行动内容] — [负责人] — [截止日期]

### 往期回顾遗留事项
- [往期行动项] — [状态：已完成/进行中/未启动]
保存为Markdown格式。保持建设性语气——核心目标是改进，而非追责。