Epic Breakdown Advisor

What Is This?

Overview

The Epic Breakdown Advisor is a structured methodology tool that guides product managers and agile teams through the process of splitting large backlog items into smaller, deliverable user stories. It applies Richard Lawrence's Humanizing Work splitting patterns, a systematic flowchart-driven approach that sequences nine distinct patterns to identify the most appropriate way to break down any given epic. The result is a set of stories that are independently valuable, estimable, and safe to deliver incrementally.

Large epics create friction at every stage of product development. They are difficult to estimate accurately, hard to sequence within a sprint, and carry significant delivery risk when treated as single units of work. The Epic Breakdown Advisor removes the guesswork from this process by providing a repeatable framework that preserves user value while reducing story size to a manageable scope.

The methodology is rooted in the principle that every split should produce stories that still deliver meaningful outcomes to users, not just technical tasks or implementation fragments. This distinction is critical: a poorly split epic produces stories that are only valuable when all pieces are complete, which defeats the purpose of iterative delivery.

Who Should Use This

• Product managers who regularly encounter epics that are too large to fit within a single sprint or release cycle
• Scrum masters and agile coaches who facilitate backlog refinement sessions and need a consistent splitting framework
• Development team leads who struggle to estimate stories accurately because the scope is undefined or too broad
• Business analysts responsible for translating high-level requirements into actionable, sprint-ready work items
• Delivery managers who need to reduce risk by sequencing smaller, independently deployable increments
• Teams adopting agile practices for the first time and looking for a structured approach to story decomposition

Why Use It?

Problems It Solves

• Epics that cannot be estimated because the scope is too broad or contains too many unknowns
• Sprint planning failures caused by stories that are too large to complete within a single iteration
• Delivery risk accumulation when large features are built entirely before any user feedback is gathered
• Backlog refinement sessions that stall because the team cannot agree on how to split a complex item
• Wasted development effort on features that could have been validated earlier with a smaller, targeted increment

Core Highlights

• Applies nine sequential Humanizing Work splitting patterns in a flowchart-driven order
• Preserves user value in every resulting story, avoiding purely technical task decomposition
• Provides a repeatable, consistent framework for any team size or domain
• Reduces estimation uncertainty by narrowing story scope before refinement begins
• Supports incremental delivery by producing stories that can be released independently
• Integrates naturally into existing backlog refinement and sprint planning ceremonies
• Applicable to both feature epics and technical improvement work items

How to Use It?

Basic Usage

Begin by stating the epic in standard user story format before applying any splitting pattern.

Epic: As a customer, I want to manage my account settings
so that I can control my preferences and personal information.

Then apply the first applicable pattern from the Humanizing Work sequence. The most common starting point is splitting by workflow steps.

Story 1: As a customer, I can update my email address
         so that my account reflects my current contact information.

Story 2: As a customer, I can change my password
         so that I can maintain the security of my account.

Story 3: As a customer, I can set my notification preferences
         so that I only receive communications I find relevant.

Specific Scenarios

Scenario 1: Splitting by data variation. When an epic handles multiple data types or input formats, isolate each variant into its own story. A file upload epic might split into separate stories for PDF, image, and CSV formats, each delivered and validated independently.

Scenario 2: Splitting by business rule complexity. When an epic contains simple and complex rule paths, deliver the happy path first. A pricing calculation epic might split into standard pricing in the first story and discount or exception logic in subsequent stories.

Real-World Examples

A checkout flow epic can be split by workflow steps: address entry, payment method selection, order review, and confirmation. Each step becomes an independently testable story.

A reporting epic can be split by data variation: summary reports first, then detailed drill-down views, then scheduled export functionality.