{"id":1769,"date":"2026-02-25T10:45:59","date_gmt":"2026-02-25T10:45:59","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/"},"modified":"2026-03-02T09:07:25","modified_gmt":"2026-03-02T09:07:25","slug":"epics-features-user-stories-agile-hierarchy","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/","title":{"rendered":"Epics, Features, and Stories: Understanding the Hierarchy"},"content":{"rendered":"<p>Most teams start by writing user stories in isolation\u2014often treating each as a standalone task. But when scaling beyond a single team, this approach quickly becomes brittle. Without a structured hierarchy, alignment breaks down, dependencies multiply, and tracking value becomes nearly impossible.<\/p>\n<p>My first decade in enterprise Agile taught me this: the real challenge isn\u2019t writing stories\u2014it\u2019s organizing them so they reflect real business outcomes, connect across teams, and scale with clarity.<\/p>\n<p>Here, you\u2019ll learn how to use the epics-features-stories hierarchy not just as a classification system, but as a strategic tool for flow, traceability, and shared understanding. You\u2019ll see how the <strong>agile hierarchy<\/strong> enables transparency, avoids requirement bloat, and ensures even complex systems deliver value incrementally.<\/p>\n<p>By the end, you\u2019ll know exactly how to break down large work, distinguish between an epic and a story, and build a backlog that scales with your organization\u2014without adding bureaucracy.<\/p>\n<h2>The Foundation: Understanding the Agile Hierarchy<\/h2>\n<p>The epics-features-stories structure isn\u2019t arbitrary. It reflects a natural progression from strategic vision to tactical execution.<\/p>\n<p>Each level serves a distinct purpose:<\/p>\n<ul>\n<li><strong>Epics<\/strong> represent large bodies of work that deliver significant business value but can\u2019t be completed in a single iteration.<\/li>\n<li><strong>Features<\/strong> are sub-components of epics\u2014deliverable chunks that often span multiple teams or require integration.<\/li>\n<li><strong>User stories<\/strong> are the smallest unit of work, written from the user\u2019s perspective and sized for delivery in a sprint.<\/li>\n<\/ul>\n<p>It\u2019s not just about size. It\u2019s about intent. An epic isn\u2019t just a \u201cbig story\u201d\u2014it\u2019s a strategic initiative that may involve multiple teams, long-term planning, and cross-functional delivery.<\/p>\n<p>Consider this: a single epic like \u201cEnable 2FA across all customer-facing services\u201d may include features such as \u201cImplement 2FA login flow,\u201d \u201cIntegrate with MFA provider API,\u201d and \u201cUpdate user onboarding guides.\u201d Each feature is then broken into stories like \u201cAs a user, I want to receive a TOTP code via SMS so I can verify my identity.\u201d<\/p>\n<h3>Why the Hierarchy Matters<\/h3>\n<p>Without a clear hierarchy, teams drift into siloed story writing. One team thinks they\u2019re working on \u201clogin improvements,\u201d another on \u201csecurity enhancements,\u201d and no one knows how these connect\u2014until delivery fails.<\/p>\n<p>The hierarchy acts as a shared map. It ensures that every story contributes to a feature, every feature to an epic, and every epic to a strategic goal. This is what enables <strong>traceability<\/strong>\u2014the ability to answer: \u201cWhat business value is being delivered, and how does this story support it?\u201d<\/p>\n<p>When teams align to this structure, planning becomes less about task completion and more about value delivery.<\/p>\n<h2>Breaking Down the Levels: Real-World Examples<\/h2>\n<p>Let\u2019s take a concrete example from a banking application trying to modernize account access.<\/p>\n<h3>High-Level Epic<\/h3>\n<p><strong>Epic:<\/strong> Upgrade to Multi-Factor Authentication (MFA) for all customer accounts<\/p>\n<p>Value: Enhance security, reduce fraud, meet compliance requirements.<\/p>\n<h3>Feature-Level Breakdown<\/h3>\n<ul>\n<li>Feature: Implement SMS-based MFA for login<\/li>\n<li>Feature: Integrate with third-party MFA provider (e.g., Twilio)<\/li>\n<li>Feature: Add fallback authentication via recovery codes<\/li>\n<li>Feature: Update user onboarding flow to include MFA setup<\/li>\n<\/ul>\n<p>Each feature is independently testable, deliverable in a sprint, and owned by a specific team or pair of teams.<\/p>\n<h3>User Story Examples<\/h3>\n<p>For the feature \u201cImplement SMS-based MFA for login\u201d:<\/p>\n<ul>\n<li>As a customer, I want to receive a 6-digit code via SMS when I log in, so I can verify my identity.<\/li>\n<li>As a customer, I want to re-request the code if I don\u2019t receive it within 60 seconds, so I\u2019m not locked out.<\/li>\n<li>As a customer, I want to see a countdown timer before I can re-send the code, so I don\u2019t spam the system.<\/li>\n<\/ul>\n<p>Notice how each story focuses on a single user action and outcome. No technical jargon. No assumptions.<\/p>\n<h2>Agile Hierarchy vs. Agile Bloat: Avoiding the Epic Trap<\/h2>\n<p>I\u2019ve seen teams write 500+ epics in a single backlog. Not because they were large, but because they didn\u2019t understand what an epic truly is.<\/p>\n<p>A common mistake: treating every large story as an epic. That\u2019s not how it works.<\/p>\n<p><strong>Key rule:<\/strong> An epic should represent a strategic initiative, not just a big story. If you&#8217;re breaking down a story into 20 smaller ones, you might need a feature\u2014or even an epic\u2014between the two.<\/p>\n<p>Ask yourself: \u201cCan this be delivered in a single sprint or release?\u201d If not, it likely belongs in a higher category.<\/p>\n<p>Here\u2019s a simple decision tree:<\/p>\n<ol>\n<li>Does it deliver significant business value? \u2192 Yes \u2192 Consider an epic.<\/li>\n<li>Can it be completed in one sprint? \u2192 Yes \u2192 Write as a feature.<\/li>\n<li>Is it a single user action with a clear outcome? \u2192 Yes \u2192 Write as a story.<\/li>\n<\/ol>\n<p>Use this to avoid the <strong>epic vs story difference<\/strong> confusion.<\/p>\n<h2>Practical Guidelines for Maintaining the Hierarchy<\/h2>\n<p>Structure alone isn\u2019t enough. The hierarchy must be maintained with discipline.<\/p>\n<h3>1. Use Consistent Naming Conventions<\/h3>\n<p>Standardize prefixes to signal category:<\/p>\n<ul>\n<li><code>Epic:<\/code> Enable secure login for all customers<\/li>\n<li><code>Feature:<\/code> Add SMS-based 2FA<\/li>\n<li><code>Story:<\/code> As a user, I want to receive a code via SMS so I can verify my identity<\/li>\n<\/ul>\n<p>Teams that use this approach report 30% faster backlog refinement and fewer alignment meetings.<\/p>\n<h3>2. Link Stories to Features, Features to Epics<\/h3>\n<p>Every story must reference its parent feature. Every feature must link to its epic.<\/p>\n<h3>3. Reassess at PI Planning<\/h3>\n<p>At each Program Increment (PI), review your epics. Are they still valid? Are dependencies resolved? Should any be split or merged?<\/p>\n<p>Some epics become obsolete. Others may need to be broken into smaller initiatives. Regular reassessment prevents stagnation.<\/p>\n<h3>4. Avoid Over-Granularity<\/h3>\n<p>Don\u2019t create stories like \u201cAdd a button to the screen.\u201d It\u2019s not a story\u2014it\u2019s a task.<\/p>\n<p>Every story must deliver user value. Ask: \u201cWho benefits? What do they gain?\u201d If you can\u2019t answer clearly, it\u2019s likely not a story.<\/p>\n<h2>Common Mistakes and How to Avoid Them<\/h2>\n<p>Even experienced teams struggle with this hierarchy. Here are the most frequent issues:<\/p>\n<ul>\n<li><strong>Epics too small:<\/strong> A \u201cBuild login page\u201d epic doesn\u2019t deliver business value. Break it into features like \u201cDesign login flow\u201d and \u201cIntegrate with auth service.\u201d<\/li>\n<li><strong>Stories too large:<\/strong> \u201cAs a user, I want to log in securely\u201d is too broad. Split into specific interactions: code receipt, retry logic, etc.<\/li>\n<li><strong>Missing traceability:<\/strong> Without links between epics, features, and stories, it\u2019s impossible to report on value delivery.<\/li>\n<li><strong>Ownership confusion:<\/strong> Features often involve multiple teams. Clarify which team owns which aspect of the feature.<\/li>\n<\/ul>\n<p>Fix these through peer reviews, sprint retrospectives, and regular backlog health checks.<\/p>\n<h2>Summary: The Three-Part Framework for Scaled Agility<\/h2>\n<p>Use this model to structure any large-scale backlog:<\/p>\n<table border=\"1\" cellspacing=\"0\" cellpadding=\"4\">\n<tbody>\n<tr>\n<th>Level<\/th>\n<th>Size<\/th>\n<th>Owner<\/th>\n<th>Delivery Time<\/th>\n<th>Focus<\/th>\n<\/tr>\n<tr>\n<td>Epic<\/td>\n<td>Large<\/td>\n<td>Product Management \/ Enterprise<\/td>\n<td>Several PI (6\u201312 weeks)<\/td>\n<td>Strategic Value<\/td>\n<\/tr>\n<tr>\n<td>Feature<\/td>\n<td>Medium<\/td>\n<td>Feature Team \/ Squad<\/td>\n<td>1\u20132 Sprints<\/td>\n<td>Integrated Functionality<\/td>\n<\/tr>\n<tr>\n<td>User Story<\/td>\n<td>Small<\/td>\n<td>Development Team<\/td>\n<td>1 Sprint<\/td>\n<td>User-Centric Value<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>When teams use this, they stop chasing work and start delivering outcomes.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between an epic and a user story?<\/h3>\n<p>An epic is a large body of work that delivers significant business value and typically spans multiple sprints or PI. A user story is a small, testable unit of work from the user\u2019s perspective, designed to be completed within a single sprint. The epic vs story difference lies in scale, scope, and delivery timeframe.<\/p>\n<h3>Can a user story be an epic?<\/h3>\n<p>No. A user story is the smallest unit of work and should represent a single, deliverable user action. If a story is too large to be completed in a sprint, it should be split or elevated into a feature or epic.<\/p>\n<h3>How do I know when to create a new feature instead of a story?<\/h3>\n<p>Create a feature when you have a group of related user stories that collectively deliver a cohesive capability. Features are often owned by a single team and require integration testing. If the stories can be delivered independently and serve a single user role, they can remain as stories.<\/p>\n<h3>Can an epic include multiple features?<\/h3>\n<p>Absolutely. Epics are composed of features. Think of an epic as a container for multiple features that together deliver a strategic outcome.<\/p>\n<h3>Should every story be linked to an epic?<\/h3>\n<p>Yes, in a scaled environment. Every story should trace back to a feature, and every feature to an epic. This ensures alignment with strategy and enables value reporting.<\/p>\n<h3>How do I manage dependencies between stories in different epics?<\/h3>\n<p>Visualize dependencies using dependency maps or story mapping. Flag high-risk dependencies early. Use cross-team sync meetings or PI planning to negotiate timelines and coordination.<\/p>\n<p>Mastering the epics-features-stories hierarchy isn\u2019t about documentation. It\u2019s about creating a shared mental model that keeps teams aligned, focused, and delivering real value\u2014no matter how large the organization.<\/p>\n<p>Start small. Use the structure. Refine it. Let it grow with your teams.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Most teams start by writing user stories in isolation\u2014often treating each as a standalone task. But when scaling beyond a single team, this approach quickly becomes brittle. Without a structured hierarchy, alignment breaks down, dependencies multiply, and tracking value becomes nearly impossible. My first decade in enterprise Agile taught me this: the real challenge isn\u2019t [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1768,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1769","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Epics, Features, and Stories: Agile Hierarchy Explained<\/title>\n<meta name=\"description\" content=\"Learn how epics, features, and user stories form the core of scalable agile backlogs. Understand the agile hierarchy, epic vs story difference, and how to decompose complex work into manageable, value-driven stories.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Epics, Features, and Stories: Agile Hierarchy Explained\" \/>\n<meta property=\"og:description\" content=\"Learn how epics, features, and user stories form the core of scalable agile backlogs. Understand the agile hierarchy, epic vs story difference, and how to decompose complex work into manageable, value-driven stories.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:07:25+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/\",\"name\":\"Epics, Features, and Stories: Agile Hierarchy Explained\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:45:59+00:00\",\"dateModified\":\"2026-03-02T09:07:25+00:00\",\"description\":\"Learn how epics, features, and user stories form the core of scalable agile backlogs. Understand the agile hierarchy, epic vs story difference, and how to decompose complex work into manageable, value-driven stories.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structuring Large-Scale Backlogs\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Epics, Features, and Stories: Understanding the Hierarchy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Epics, Features, and Stories: Agile Hierarchy Explained","description":"Learn how epics, features, and user stories form the core of scalable agile backlogs. Understand the agile hierarchy, epic vs story difference, and how to decompose complex work into manageable, value-driven stories.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/","og_locale":"es_ES","og_type":"article","og_title":"Epics, Features, and Stories: Agile Hierarchy Explained","og_description":"Learn how epics, features, and user stories form the core of scalable agile backlogs. Understand the agile hierarchy, epic vs story difference, and how to decompose complex work into manageable, value-driven stories.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","article_modified_time":"2026-03-02T09:07:25+00:00","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/","name":"Epics, Features, and Stories: Agile Hierarchy Explained","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:45:59+00:00","dateModified":"2026-03-02T09:07:25+00:00","description":"Learn how epics, features, and user stories form the core of scalable agile backlogs. Understand the agile hierarchy, epic vs story difference, and how to decompose complex work into manageable, value-driven stories.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/epics-features-user-stories-agile-hierarchy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Structuring Large-Scale Backlogs","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/"},{"@type":"ListItem","position":4,"name":"Epics, Features, and Stories: Understanding the Hierarchy"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1769","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1769\/revisions"}],"predecessor-version":[{"id":2394,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1769\/revisions\/2394"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1768"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=1769"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=1769"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}