Agile Backlog Workshop with Epics, Features, and User Stories

Backlog Basics

Product Backlog

A prioritized, living list of everything that might be needed in the product — features, enhancements, fixes, and enablers — ordered by value.

Backlog Hierarchy

A structure that organizes work by size and scope: epics contain features, and features are delivered through user stories.

Single Prioritized List

Regardless of hierarchy, the team pulls from one ordered list so it always works on the highest-value ready item.

Living Backlog

The backlog is continuously refined and reordered as understanding, priorities, and market conditions evolve.

Epics

Epic

A large body of work or significant initiative that is too big to deliver in one iteration and is broken down into features and stories.

Epic Hypothesis

A concise statement of the expected outcome and value of an epic, framing it as something to validate rather than assume.

When to Use Epics

Epics capture big ideas early at low detail, deferring decomposition until they rise in priority.

Features

Feature

A service or capability that delivers value to a stakeholder, sized to be completed within a release or program increment, with a benefit and acceptance criteria.

Benefit Hypothesis

The expected measurable business outcome of a feature, used to justify and prioritize it.

Feature vs. Story

A feature is a larger capability delivered across multiple stories; a story is a small, user-focused slice completed in an iteration.

User Stories

User Story

A short description of functionality from the user's perspective: 'As a <role>, I want <goal> so that <benefit>.'

The 3 Cs

Card (the written story), Conversation (the discussion that clarifies it), and Confirmation (the acceptance criteria that prove it's done).

INVEST

Good stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.

Acceptance Criteria

Conditions a story must meet to be accepted, removing ambiguity and guiding development and testing.

Definition of Ready

A shared checklist that a backlog item must meet before the team commits to it in an iteration.

Definition of Done

A shared checklist of quality criteria that work must satisfy to be considered complete.

Splitting

Story Splitting

Breaking a large story into smaller, independently valuable, testable slices that each fit in an iteration.

Splitting Patterns

Common ways to split: by workflow steps, business-rule variations, data variations, operations (CRUD), or simple/complex paths.

Vertical Slicing

Slicing work so each story delivers a thin, end-to-end piece of usable value rather than a horizontal technical layer.

Decomposing Epics to Features to Stories

Progressively breaking big items down as they near delivery, adding detail just in time.

Refinement

Backlog Refinement

The ongoing activity of detailing, estimating, and ordering items so the top of the backlog is always ready.

Story Mapping

Arranging stories along the user's journey to visualize the whole experience, find gaps, and plan releases.

Relative Estimation

Sizing items against each other using story points, often with planning poker, rather than absolute time.

Prioritization

Prioritization

Ordering the backlog by value, risk, and cost so the most important work is done first.

WSJF

Weighted Shortest Job First — Cost of Delay divided by job size — used to sequence work for maximum economic benefit.

MoSCoW

Grouping items as Must, Should, Could, and Won't have to guide scope and release decisions.

Value vs. Effort

A simple prioritization lens that favors high-value, low-effort items to maximize early return.

Workshop

Collaborative Backlog Building

Building the backlog together with the team and stakeholders so it is shared, understood, and owned.