Why-What-Acceptance Backlog Expert

Overview

Create backlog items using the Why-What-Acceptance (WWAS) format. This format ensures every piece of work connects to strategic context, includes a concise description that serves as a "reminder of the discussion" rather than a detailed specification, and defines high-level acceptance criteria focused on observable outcomes.

When to Use

• Backlog creation -- When building a product backlog where strategic alignment is critical.
• Sprint planning -- When refining items for upcoming sprints and the team needs to understand why each item matters.
• Stakeholder communication -- When executives or cross-functional partners need to see how individual work items connect to business objectives.
• Roadmap decomposition -- When breaking down roadmap themes into actionable backlog items.

When NOT to Use

• When you need situation-driven requirements -- use job-stories/ instead.
• When the work is a pure technical task with no strategic context (use a simple task description).
• When the team prefers traditional user story format and the strategic context is well-understood.

The WWAS Format