sprint-planning
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/sprint-planning
/sprint-planning
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Plan a sprint by scoping work, estimating capacity, and setting clear goals.
如果你看到不熟悉的占位符或需要查看已连接的工具,请参阅CONNECTORS.md。
通过确定工作范围、估算产能和设定明确目标来规划冲刺。
Usage
使用方法
/sprint-planning $ARGUMENTS/sprint-planning $ARGUMENTSHow It Works
工作原理
┌─────────────────────────────────────────────────────────────────┐
│ SPRINT PLANNING │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Define sprint goals and success criteria │
│ ✓ Estimate team capacity (accounting for PTO, meetings) │
│ ✓ Scope and prioritize backlog items │
│ ✓ Identify dependencies and risks │
│ ✓ Generate sprint plan document │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Project tracker: Pull backlog, create sprint, assign items │
│ + Calendar: Account for PTO and meetings in capacity │
│ + Chat: Share sprint plan with the team │
└─────────────────────────────────────────────────────────────────┘┌─────────────────────────────────────────────────────────────────┐
│ 冲刺规划 │
├─────────────────────────────────────────────────────────────────┤
│ 独立模式(始终可用) │
│ ✓ 定义冲刺目标和成功标准 │
│ ✓ 估算团队产能(考虑休假和会议) │
│ ✓ 确定待办事项范围并划分优先级 │
│ ✓ 识别依赖关系和风险 │
│ ✓ 生成冲刺计划文档 │
├─────────────────────────────────────────────────────────────────┤
│ 增强模式(连接工具后可用) │
│ + 项目跟踪工具:拉取待办事项、创建冲刺、分配任务 │
│ + 日历:在产能估算中考虑休假和会议 │
│ + 聊天工具:与团队共享冲刺计划 │
└─────────────────────────────────────────────────────────────────┘What I Need From You
我需要你提供以下信息
- Team: Who's on the team and their availability this sprint?
- Sprint length: How many days/weeks?
- Backlog: What's prioritized? (Pull from tracker, paste, or describe)
- Carryover: Anything unfinished from last sprint?
- Dependencies: Anything blocked on other teams?
- 团队: 团队成员有哪些?他们本次冲刺的可用时间是多少?
- 冲刺时长: 持续几天/几周?
- 待办事项: 哪些是优先事项?(可从跟踪工具拉取、粘贴或描述)
- 未完成工作: 上一冲刺有哪些未完成的工作?
- 依赖关系: 是否有依赖其他团队的工作?
Output
输出结果
markdown
undefinedmarkdown
undefinedSprint Plan: [Sprint Name]
冲刺计划: [冲刺名称]
Dates: [Start] — [End] | Team: [X] engineers
Sprint Goal: [One clear sentence about what success looks like]
日期: [开始日期] — [结束日期] | 团队: [X] 名工程师
冲刺目标: [用一句话明确成功的标准]
Capacity
产能
| Person | Available Days | Allocation | Notes |
|---|---|---|---|
| [Name] | [X] of [Y] | [X] points/hours | [PTO, on-call, etc.] |
| Total | [X] | [X] points |
| 人员 | 可用天数 | 分配量 | 备注 |
|---|---|---|---|
| [姓名] | [X]/[Y] | [X] 点数/小时 | [休假、值班等] |
| 总计 | [X] | [X] 点数 |
Sprint Backlog
冲刺待办事项
| Priority | Item | Estimate | Owner | Dependencies |
|---|---|---|---|---|
| P0 | [Must ship] | [X] pts | [Person] | [None / Blocked by X] |
| P1 | [Should ship] | [X] pts | [Person] | [None] |
| P2 | [Stretch] | [X] pts | [Person] | [None] |
| 优先级 | 任务 | 估算值 | 负责人 | 依赖关系 |
|---|---|---|---|---|
| P0 | [必须交付] | [X] 点数 | [人员] | [无 / 依赖X团队] |
| P1 | [应该交付] | [X] 点数 | [人员] | [无] |
| P2 | [延伸任务] | [X] 点数 | [人员] | [无] |
Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)
规划产能: [X] 点数 | 冲刺负载: [X] 点数(占产能的[X]%)
Risks
风险
| Risk | Impact | Mitigation |
|---|---|---|
| [Risk] | [What happens] | [What to do] |
| 风险 | 影响 | 缓解措施 |
|---|---|---|
| [风险内容] | [后果] | [应对措施] |
Definition of Done
完成定义
- Code reviewed and merged
- Tests passing
- Documentation updated (if applicable)
- Product sign-off
- 代码已评审并合并
- 测试通过
- 文档已更新(如适用)
- 产品负责人确认
Key Dates
关键日期
| Date | Event |
|---|---|
| [Date] | Sprint start |
| [Date] | Mid-sprint check-in |
| [Date] | Sprint end / Demo |
| [Date] | Retro |
undefined| 日期 | 事件 |
|---|---|
| [日期] | 冲刺启动 |
| [日期] | 冲刺中期检查 |
| [日期] | 冲刺结束/演示 |
| [日期] | 回顾会议 |
undefinedTips
提示
- Leave buffer — Plan to 70-80% capacity. You will get interrupts.
- One clear sprint goal — If you can't state it in one sentence, the sprint is unfocused.
- Identify stretch items — Know what to cut if things take longer than expected.
- Carry over honestly — If something didn't ship, understand why before re-committing.
- 预留缓冲 — 按产能的70-80%规划,你肯定会遇到突发干扰。
- 一个清晰的冲刺目标 — 如果你无法用一句话说明,说明冲刺的重点不明确。
- 识别延伸任务 — 要知道如果任务耗时超出预期,哪些可以优先砍掉。
- 如实处理未完成工作 — 如果某项工作未交付,在重新承诺之前要先了解原因。