Refinement Notes

梳理笔记

Refinement notes capture the outcomes of backlog refinement (grooming) sessions.what was discussed, what was estimated, and what decisions were made. They serve as a quick reference for team members who missed the session and a historical record of how stories evolved from idea to ready-for-sprint.

梳理笔记用于记录backlog refinement（又称grooming）会议的成果，包括讨论内容、估算结果以及做出的决策。它们可为未参会的团队成员提供快速参考，同时也是用户故事从想法演进到 Sprint 就绪状态的历史记录。

When to Use

使用场景

During refinement sessions to capture decisions in real-time
After refinement to share outcomes with absent team members
When onboarding new team members to explain backlog context
Before sprint planning to review what's been refined
When stories need re-refinement due to time elapsed

在梳理会议期间实时记录决策
梳理结束后向未参会的团队成员分享成果
新团队成员入职时，用于解释backlog背景
Sprint规划前，回顾已梳理的内容
因时间推移需要重新梳理用户故事时

Instructions

使用说明

When asked to document refinement notes, follow these steps:

Record Session Metadata Note the date, attendees, and duration. This helps track who was part of decisions and when discussions happened.
List Stories Discussed For each story, capture the outcome: estimated points, refined status, key discussion points, and any modifications made to the original scope.
Document Questions Raised Questions that couldn't be answered in the session need owners and due dates. Don't let them disappear.they often block sprint planning.
Capture Decisions Made Record any scope decisions, technical approaches agreed upon, or priority changes. These decisions are valuable context that gets lost without documentation.
Note Action Items Any follow-up work needed before stories are sprint-ready: mockups to create, technical spikes to run, stakeholders to consult.
Flag Blocked Stories Clearly identify stories that can't proceed until blockers are resolved. Include what the blocker is and who owns resolution.
Plan Next Session Note what should be refined next and any preparation needed.

当需要记录梳理笔记时，请遵循以下步骤：

记录会议元数据 记录日期、参会人员和时长。这有助于跟踪决策参与人员及讨论时间。
列出讨论的用户故事 针对每个用户故事，记录成果：估算点数、梳理状态、关键讨论点以及对原始范围的任何修改。
记录提出的问题 会议中无法解答的问题需指定负责人和截止日期。不要让这些问题不了了之，它们往往会阻碍Sprint规划。
记录做出的决策 记录所有范围决策、商定的技术方案或优先级变更。这些决策是重要的背景信息，若不记录则容易丢失。
记录行动项 用户故事达到Sprint就绪状态前所需的后续工作：制作原型图、开展技术调研、咨询相关利益干系人。
标记受阻的用户故事 明确标记需解决阻碍后才能推进的用户故事，记录阻碍内容及解决负责人。
规划下一次会议 记录下次需梳理的内容及所需的准备工作。

Output Format

输出格式

Use the template in

references/TEMPLATE.md

to structure the output.

使用

references/TEMPLATE.md

中的模板来构建输出内容。

Quality Checklist

质量检查清单

Before finalizing, verify:

All discussed stories have outcomes recorded
Open questions have owners assigned
Decisions are captured with enough context
Blocked stories are clearly flagged
Notes are understandable to someone who wasn't there

定稿前，请确认：

所有讨论过的用户故事均已记录成果
未解决的问题已指定负责人
决策记录包含足够的背景信息
受阻的用户故事已明确标记
未参会人员也能理解笔记内容

Examples

示例

See

references/EXAMPLE.md

for a completed example.

可查看

references/EXAMPLE.md

中的完整示例。

iterate-refinement-notes

Original

Translation