Auto-sync: 2026-04-21 00:02
This commit is contained in:
32
wiki/concepts/Product-Requirements-Document.md
Normal file
32
wiki/concepts/Product-Requirements-Document.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: "Product Requirements Document (PRD)"
|
||||
type: concept
|
||||
tags: [product-management, documentation, deliverable]
|
||||
sources: [product-manager.md]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
产品规格文档(PRD)是一份系统性定义产品功能需求的文档,涵盖问题陈述、目标与成功指标、用户故事、解决方案概述、技术考量、发布计划和附录。
|
||||
|
||||
## Structure
|
||||
1. **Problem Statement**:具体用户痛点或商业机会
|
||||
2. **Goals & Success Metrics**:目标、指标、基线、目标值、测量窗口
|
||||
3. **Non-Goals**:明确本迭代不解决的问题
|
||||
4. **User Personas & Stories**:核心用户故事与验收标准
|
||||
5. **Solution Overview**:2-4 段解决方案叙事
|
||||
6. **Technical Considerations**:依赖、已知风险、开放问题
|
||||
7. **Launch Plan**:内部 alpha → 封闭 beta → GA 分阶段发布
|
||||
8. **Appendix**:研究录音、竞品分析、设计稿、仪表盘、支持票据
|
||||
|
||||
## Key Principles
|
||||
- 先问题后方案
|
||||
- 所有功能想法都是假设,用证据验证
|
||||
- PRD 协作编写,工程和设计从一开始就参与
|
||||
- 开发前锁定范围并获得所有利益相关方书面签字
|
||||
- PRFAQ 练习:写发布邮件和怀疑用户会问的 FAQ
|
||||
|
||||
## Connection
|
||||
- [[Product Manager Agent]] ← produces ← [[Product Requirements Document (PRD)]]
|
||||
- [[Discovery Process]] ← feeds_into ← [[Product Requirements Document (PRD)]]
|
||||
- [[Opportunity Assessment]] ← precedes ← [[Product Requirements Document (PRD)]]
|
||||
Reference in New Issue
Block a user