46 lines
2.2 KiB
Markdown
46 lines
2.2 KiB
Markdown
---
|
||
title: "Product Sprint Prioritizer"
|
||
type: source
|
||
tags: [agent, the-agency, product-management, agile]
|
||
sources: [raw/Agent/agency-agents/product/product-sprint-prioritizer.md]
|
||
last_updated: 2026-04-20
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Agent/agency-agents/product/product-sprint-prioritizer.md]]
|
||
|
||
## Summary
|
||
- 核心主题：产品冲刺优先级智能体，专注于敏捷冲刺规划、功能优先排序和资源分配
|
||
- 问题域：团队velocity最大化、业务价值交付、数据驱动决策
|
||
- 方法/机制：RICE、MoSCoW、Kano Model、Value vs. Effort Matrix 等优先排序框架；Scrum、Kanban、SAFe 等敏捷方法论；团队容量规划与依赖管理
|
||
- 结论/价值：提供 90%+ 故事点交付率、4.5/5 干系人满意度、±10% 时间线偏差等可衡量指标
|
||
|
||
## Key Claims
|
||
- RICE 框架通过 (Reach × Impact × Confidence) ÷ Effort 计算优先级分数，实现数据驱动排序
|
||
- 团队 Velocity 应保持 <15% 的 sprint 间变化，并呈现上升趋势
|
||
- 技术债务应维持在 20% 以下 sprint 容量，并通过常规监控保持
|
||
- 依赖项应在 sprint 开始前 95% 解决，通过主动规划实现
|
||
|
||
## Key Quotes
|
||
> "Use this agent when you need sprint planning and backlog prioritization with data-driven decision making" — 核心使用场景定义
|
||
|
||
## Key Concepts
|
||
- [[RICE Framework]]：优先排序框架 Reach × Impact × Confidence ÷ Effort
|
||
- [[MoSCoW Method]]：Must-Have、Should-Have、Could-Have、Won't-Have 优先级分类
|
||
- [[Kano Model]]：Must-Be、Performance、Delighter 分类模型
|
||
- [[Team Velocity]]：团队在单个 sprint 中完成的故事点数量
|
||
- [[Sprint Planning]]：冲刺规划过程，定义 sprint 目标和故事选择
|
||
- [[Capacity Planning]]：容量规划，评估团队可用性和资源分配
|
||
- [[Risk Management]]：风险管理，识别、评估和缓解项目风险
|
||
|
||
## Key Entities
|
||
- [[The Agency]]：开源 AI 智能体集合项目，本智能体所属项目
|
||
|
||
## Connections
|
||
- [[Product Manager]] ← extends ← [[Product Sprint Prioritizer]]
|
||
- [[Product Trend Researcher]] ← related_to ← [[Product Sprint Prioritizer]]
|
||
- [[Studio Producer]] ← coordinates_with ← [[Product Sprint Prioritizer]]
|
||
|
||
## Contradictions
|
||
- 暂无已知冲突
|