Back to Details

sprint-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sprint Planning

Sprint规划

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.
通过估算团队容量、选择并排序需求故事、识别风险来规划一个Sprint。

Context

背景信息

You are helping plan a sprint for $ARGUMENTS.
If the user provides files (backlogs, velocity data, team rosters, or previous sprint reports), read them first.
你正在为**$ARGUMENTS**规划一个Sprint。
如果用户提供了文件（待办事项列表、交付速度数据、团队人员名单或过往冲刺报告），请先阅读这些文件。

Instructions

操作步骤

  1. Estimate team capacity:
    • Number of team members and their availability (PTO, meetings, on-call)
    • Historical velocity (average story points per sprint from last 3 sprints)
    • Capacity buffer: reserve 15-20% for unexpected work, bugs, and tech debt
    • Calculate available capacity in story points or ideal hours
  2. Review and select stories:
    • Pull from the prioritized backlog (highest priority first)
    • Verify each story meets the Definition of Ready (clear AC, estimated, no blockers)
    • Flag stories that need refinement before committing
    • Stop adding stories when capacity is reached
  3. Map dependencies:
    • Identify stories that depend on other stories or external teams
    • Sequence dependent stories appropriately
    • Flag external dependencies and owners
    • Identify the critical path
  4. Identify risks and mitigations:
    • Stories with high uncertainty or complexity
    • External dependencies that could slip
    • Knowledge concentration (only one person can do it)
    • Suggest mitigations for each risk
  5. Create the sprint plan summary:
    Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]

Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...

Risks:
- [Risk] → [Mitigation]
  6. Define the sprint goal: A single, clear sentence that captures the sprint's primary value delivery.
Think step by step. Save as markdown.
  1. 估算团队容量:
    • 团队成员数量及其可用时间（带薪休假、会议、值班）
    • 历史交付速度（过去3个Sprint的平均故事点数）
    • 容量缓冲：预留15-20%的时间用于突发工作、bug修复和技术债务
    • 以故事点数或理想工时计算可用容量
  2. 评审并选择需求故事:
    • 从优先级排序的待办事项列表中选取（优先选择最高优先级的需求）
    • 验证每个故事是否符合Definition of Ready（清晰的验收标准、已估算、无阻塞）
    • 标记需要在提交前细化的故事
    • 达到容量上限后停止添加故事
  3. 映射依赖关系:
    • 识别依赖于其他故事或外部团队的需求故事
    • 合理排序有依赖关系的故事
    • 标记外部依赖项及其负责人
    • 识别关键路径
  4. 识别风险与缓解措施:
    • 具有高度不确定性或复杂性的故事
    • 可能延迟的外部依赖项
    • 知识集中（只有一人能完成该工作）
    • 为每个风险建议缓解措施
  5. 创建冲刺规划摘要:
    Sprint Goal: [One sentence describing what success looks like]
Duration: [2 weeks / 1 week / etc.]
Team Capacity: [X story points]
Committed Stories: [Y story points across Z stories]
Buffer: [remaining capacity]

Stories:
1. [Story title] — [points] — [owner] — [dependencies]
...

Risks:
- [Risk] → [Mitigation]
  6. 定义Sprint目标: 一句清晰的单句，概括该Sprint的主要价值交付内容。
逐步思考。保存为Markdown格式。

Further Reading

扩展阅读