wwas
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseWhy-What-Acceptance (WWA)
Why-What-Acceptance (WWA)
Create product backlog items in Why-What-Acceptance format. Produces independent, valuable, testable items with strategic context.
Use when: Writing backlog items, creating product increments, breaking features into work items, or communicating strategic intent to teams.
Arguments:
- : The product or system name
$PRODUCT - : The new feature or capability
$FEATURE - : Link to design files (Figma, Miro, etc.)
$DESIGN - : Key assumptions and strategic context
$ASSUMPTIONS
采用Why-What-Acceptance（WWA）格式创建产品待办事项，生成具备战略背景的独立、有价值、可测试的事项。
适用场景： 编写待办事项、创建产品增量、将功能拆分为工作项，或向团队传达战略意图时。
参数：
- ：产品或系统名称
$PRODUCT - ：新功能或能力
$FEATURE - ：设计文件链接（Figma、Miro等）
$DESIGN - ：关键假设和战略背景
$ASSUMPTIONS
Step-by-Step Process
分步流程
- Define the strategic Why - Connect work to business and team objectives
- Describe the What - Keep descriptions concise, reference designs
- Write Acceptance Criteria - High-level, not detailed specifications
- Ensure independence - Items can be developed in any order
- Keep items negotiable - Invite team conversation, not constraints
- Make items valuable - Each delivers measurable user or business value
- Ensure testability - Outcomes are observable and verifiable
- Size appropriately - Small enough for one sprint estimate
- 定义战略层面的Why - 将工作与业务及团队目标关联
- 描述具体的What - 描述简洁，参考设计文件
- 编写验收标准 - 仅需高层级内容，无需详细规格
- 确保独立性 - 事项可按任意顺序开发
- 保持协商空间 - 鼓励团队讨论，而非强加约束
- 确保价值性 - 每个事项都能为用户或业务带来可衡量的价值
- 确保可测试性 - 成果可观察、可验证
- 合理估算规模 - 规模足够小，可在一个冲刺周期内完成估算
Item Template
事项模板
Title: [What will be delivered]
Why: [1-2 sentences connecting to strategic context and team objectives]
What: [Short description and design link. 1-2 paragraphs maximum. A reminder of discussion, not detailed specification.]
Acceptance Criteria:
- [Observable outcome 1]
- [Observable outcome 2]
- [Observable outcome 3]
- [Observable outcome 4]
标题： [交付内容]
Why： [1-2句话，关联战略背景与团队目标]
What： [简短描述及设计链接，最多1-2段。仅作为讨论的提示，而非详细规格。]
验收标准：
- [可观察成果1]
- [可观察成果2]
- [可观察成果3]
- [可观察成果4]
Example WWA Item
WWA事项示例
Title: Implement Real-Time Spending Tracker
Why: Users need immediate feedback on spending to make conscious budget decisions. This directly supports our goal to improve financial awareness and reduce overspending.
What: Add a real-time spending tracker that updates as users log expenses. The tracker displays their current week's spending against their set budget. Designs available in [Figma link]. This is a reminder of our discussions - detailed specifications will emerge during development conversations with the team.
Acceptance Criteria:
- Spending totals update within 2 seconds of logging an expense
- Budget progress is visually indicated with a progress bar
- Users can see remaining budget amount at a glance
- System handles multiple expense categories correctly
标题： 实现实时支出追踪器
Why： 用户需要支出的即时反馈，以便做出理性的预算决策。这直接支持我们提升用户财务意识、减少超支的目标。
What： 添加实时支出追踪器，用户记录支出后立即更新。该追踪器显示用户当前周的支出与设定预算的对比。设计文件可查看[Figma链接]。此内容仅作为我们讨论的提示——详细规格将在与团队的开发沟通中逐步明确。
验收标准：
- 记录支出后，支出总额在2秒内更新
- 预算进度通过进度条可视化展示
- 用户可快速查看剩余预算金额
- 系统可正确处理多种支出类别
Output Deliverables
输出交付物
- Complete set of backlog items for the feature
- Each item includes Why, What, and Acceptance Criteria sections
- Items are independent and deliverable in any order
- Items are sized for estimation and completion in one sprint
- Strategic context is clear for team decision-making
- Design references are included for implementation guidance
- 该功能的完整待办事项集
- 每个事项包含Why、What和验收标准部分
- 事项具备独立性，可按任意顺序交付
- 事项规模适合估算，可在一个冲刺周期内完成
- 战略背景清晰，便于团队决策
- 包含设计参考，为实施提供指导