Breakdown Epic Pm

breakdown-epic-pm skill for programming & development

Category: development Source: github

Large product initiatives require decomposition into user stories with clear value. This skill breaks down epics from product management perspective into user stories, acceptance criteria, priorities, dependencies, and release planning enabling agile execution of major features while delivering value incrementally.

What Is This?

Overview

Breakdown Epic PM decomposes product epics into implementable user stories. It analyzes epic scope and user value, identifies user journeys and scenarios, creates user stories with acceptance criteria, prioritizes stories by value and dependencies, plans releases delivering incremental value, estimates story points, and organizes into sprints.

The skill ensures stories are independently valuable, testable, and appropriately sized. It considers user personas, business objectives, technical dependencies, and team velocity. Output includes prioritized backlog, release plan, and story dependencies.

This enables agile execution of large features, delivers value incrementally, maintains user focus throughout development, and provides clear success criteria for validation.

Who Should Use This

Product managers planning features. Product owners managing backlogs. Agile teams breaking down work. Scrum masters facilitating planning. Anyone decomposing product initiatives.

Why Use It?

Problems It Solves

Large epics are difficult to estimate and execute. Breakdown into stories enables agile delivery.

Unclear value proposition confuses development. User-focused stories clarify value.

All-or-nothing delivery delays value realization. Incremental releases deliver value progressively.

Unclear acceptance criteria cause scope issues. Explicit criteria define done clearly.

Core Highlights

Epic decomposition into user stories. Acceptance criteria definition. Story prioritization by value. Dependency identification. Release planning for incremental value. Story point estimation. Sprint organization. User journey mapping.

How to Use It?

Basic Usage

Analyze epic, identify user stories, write acceptance criteria, prioritize, plan releases.

Review epic goals and value
Identify user personas and journeys
Create user stories with As-a/I-want/So-that format
Write acceptance criteria for each story
Prioritize by value and dependencies
Estimate story points
Organize into releases and sprints

Specific Scenarios

For e-commerce checkout epic:

Story 1: Guest checkout (MVP)
Story 2: Save payment methods
Story 3: Apply discount codes
Story 4: Multi-address shipping
Story 5: One-click reorder
Prioritized by value and dependencies

For reporting feature epic:

Story 1: Basic report viewing
Story 2: Export to CSV
Story 3: Filter and sort
Story 4: Scheduled reports
Story 5: Custom report builder
Progressive enhancement approach

For authentication epic:

Story 1: Email/password login (must have)
Story 2: Password reset flow
Story 3: Social login
Story 4: Two-factor authentication
Story 5: SSO integration
Ordered by priority

Real-World Examples

A product manager receives epic for new analytics dashboard. They decompose into 15 user stories covering data visualization, filtering, exporting, and sharing. Stories prioritized by user value starting with basic charts, then filters, then advanced features. First release includes 5 core stories delivering immediate value. Subsequent releases add sophistication. Team delivers working features every sprint.

An e-commerce platform needs checkout improvements epic. PM identifies 12 stories across guest checkout, saved payments, shipping options, and order confirmation. Dependencies mapped (guest checkout before saved payments). Stories sized appropriately for sprints. Release 1 improves guest flow. Release 2 adds convenience features. Release 3 optimizes conversion. Each release delivers measurable business value.

A mobile app epic requires offline functionality. PM creates stories for data caching, sync mechanisms, conflict resolution, and offline indicators. Technical dependencies identified. Stories sequenced enabling incremental capability. Early stories deliver basic offline reading. Later stories add complex sync. Users get progressive offline capability rather than waiting for complete solution.

Advanced Tips

Write stories in user language not technical terms. Ensure each story provides independent value. Define clear measurable acceptance criteria. Prioritize by value not ease. Consider dependencies when sequencing. Size stories for one sprint maximum. Map user journeys before creating stories. Include non-functional requirements as stories. Validate stories with users. Refine continuously based on feedback.

When to Use It?

Use Cases

Feature epic decomposition. Product backlog creation. Release planning. Sprint planning preparation. User story writing. Acceptance criteria definition. Dependency mapping. Value prioritization.

Important Notes

Requirements

Clear epic scope and objectives. Understanding of user personas. Knowledge of technical constraints. Team velocity data. Stakeholder priorities. Business value understanding. Capacity for refinement.

Usage Recommendations

Focus on user value not features. Write clear acceptance criteria. Keep stories independent when possible. Size appropriately for sprints. Prioritize ruthlessly by value. Map dependencies explicitly. Plan releases delivering value incrementally. Validate stories with users. Refine continuously. Maintain flexible backlog. Adjust based on feedback and learning.

Limitations

Cannot anticipate all user needs. Estimates are uncertain initially. Dependencies may emerge later. Priorities may shift. Technical constraints discovered during work. Requires ongoing refinement. Story quality improves with practice. Team velocity affects delivery timing.