wwas
以 Why‑What‑Acceptance（为什么‑什么‑验收）格式创建产品待办事项——使其成为独立、有价值、可测试并具战略背景的条目。适用于编写结构化的待办事项、将功能拆分为工作项或使用 WWA 格式时。
作者
分类
产品设计安装
热度:33
下载并解压到你的 skills 目录
复制命令，发送给智能体自动安装：
下载并安装这个技能 https://openskills.cc/api/download?slug=phuryn-pm-execution-skills-wwas&locale=zh&source=copy
Why-What-Acceptance (WWA) — 创建战略性产品待办事项
技能概述
wwas 帮助产品经理和敏捷团队创建结构化的产品待办事项，采用 Why-What-Acceptance 格式，每个条目都独立、有价值、可测试，并包含清晰的战略背景。
适用场景
核心功能
常见问题
What is Why-What-Acceptance format?
Why-What-Acceptance (WWA) is a structured format for writing product backlog items that includes three sections: "Why" connects to strategic objectives, "What" briefly describes the work with design references, and "Acceptance Criteria" lists observable, verifiable outcomes. Unlike traditional user stories, WWA explicitly includes strategic context and focuses on high-level criteria rather than detailed specifications.
How do I write acceptance criteria for backlog items?
Write acceptance criteria as observable outcomes that can be verified, not as implementation details. Each criterion should be something a user or stakeholder can see or test. For example, "Budget progress is visually indicated with a progress bar" is a good criterion because it describes a visible outcome, whereas "Use React component X" is too technical and belongs in implementation discussions, not acceptance criteria.
What makes a good product backlog item?
A good backlog item is independent (can be developed in any order without dependencies), valuable (delivers measurable user or business value), negotiable (invites team conversation rather than constraining solutions), testable (outcomes are observable and verifiable), and appropriately sized (small enough to estimate and complete in one sprint). WWA format naturally ensures all these qualities through its structure.
Why include strategic context in backlog items?
Including strategic context (the "Why") helps development teams make better decisions when implementation questions arise. When developers understand the business objectives behind a feature, they can propose alternative solutions, identify edge cases, and prioritize trade-offs more effectively. Strategic context also prevents the "telephone game" where original intent gets lost through multiple handoffs.
How do I ensure backlog items are independent?
To ensure independence, avoid splitting by technical layers (e.g., "database" then "API" then "UI") and instead split by vertical slices that deliver end-to-end value. Each item should be completable on its own. If you find items with "blocked by" dependencies, reconsider the splitting strategy. WWA's focus on delivering valuable outcomes naturally guides you toward independent items.
What's the difference between What and Acceptance Criteria?
The "What" section is a short reminder (1-2 paragraphs) of what will be built, often referencing design documents. It's meant to refresh the team's memory about prior discussions. Acceptance Criteria are specific, observable outcomes that must be true for the item to be considered complete. Think of "What" as the conversation summary and "Acceptance Criteria" as the pass/fail test.
How do I size backlog items for a sprint?
Size backlog items by estimating the effort for design, development, testing, and deployment. If an item feels too large to complete in one sprint (typically 2 weeks), split it into smaller vertical slices that each deliver value. WWA helps with sizing because its structure forces you to focus on a single, valuable outcome rather than bundling multiple concerns together.
Can WWA replace traditional user stories?
Yes, WWA can replace traditional user stories. In fact, WWA improves on the classic "As a [user], I want [feature], so that [benefit]" format by making strategic context explicit and focusing on observable outcomes rather than user role narratives. Many teams find WWA more effective at communicating intent and ensuring business alignment.