{"id":1104,"date":"2026-02-25T10:35:57","date_gmt":"2026-02-25T10:35:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/"},"modified":"2026-03-02T09:10:23","modified_gmt":"2026-03-02T09:10:23","slug":"splitting-user-stories-without-losing-value","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/","title":{"rendered":"How to Split Epic Stories Without Losing Value"},"content":{"rendered":"<p>Large epics often become the bottleneck between vision and delivery. They feel complete on paper but stall progress when teams can&#8217;t move forward without further breakdown. The real challenge isn&#8217;t complexity\u2014it\u2019s preserving value while making stories small enough to deliver in a sprint.<\/p>\n<p>Splitting user stories isn\u2019t about arbitrary division. It\u2019s about redefining a large piece of work into smaller, independent, value-delivering units that still reflect the original user intent.<\/p>\n<p>My experience working with product teams across fintech, SaaS, and healthcare sectors taught me one thing: the best splits are not just smaller\u2014they\u2019re better aligned with user journeys, business outcomes, and technical feasibility.<\/p>\n<p>What you\u2019ll learn here is how to apply proven <strong>epic breakdown techniques<\/strong> that don\u2019t sacrifice clarity or purpose. You\u2019ll walk away with actionable <strong>story slicing patterns<\/strong> used by mature Agile teams to keep backlog flow smooth and sprint goals achievable.<\/p>\n<h2>Why Simple Splitting Often Fails<\/h2>\n<p>Many teams try to split epics by simply cutting text in half. \u201cUser wants to log in\u201d becomes \u201cUser wants to enter email\u201d and \u201cUser wants to enter password.\u201d But this breaks context and creates dependency ghosts.<\/p>\n<p>Instead of splitting by action, split by value. A story isn\u2019t small because it\u2019s short. It\u2019s small when it delivers a measurable outcome.<\/p>\n<p>Consider this: the goal isn\u2019t to create more stories. It\u2019s to create stories that can be tested, shipped, and validated independently.<\/p>\n<h3>Common Pitfalls in Story Slicing<\/h3>\n<ul>\n<li>Splitting by technical layer (e.g., frontend vs backend) instead of user value.<\/li>\n<li>Creating stories that only make sense in sequence, limiting flexibility.<\/li>\n<li>Over-attributing functionality to a single story, making it hard to test.<\/li>\n<li>Using vague verbs like \u201cmanage\u201d or \u201chandle\u201d without clear outcomes.<\/li>\n<\/ul>\n<p>These mistakes stem from treating stories as tasks, not conversations about user value. The solution lies in recognizing what drives user behavior\u2014and slicing along those lines.<\/p>\n<h2>6 Proven Story Slicing Patterns<\/h2>\n<p>Not all epics break the same way. Some call for chronological flow, others require conditional logic. Here are the most effective <strong>story slicing patterns<\/strong> grounded in real team experience.<\/p>\n<h3>1. Slice by User Journey (Step-by-Step Flow)<\/h3>\n<p>Break the epic into stages of a user\u2019s experience. This works best for onboarding, checkout, or account setup flows.<\/p>\n<p><strong>Example:<\/strong> \u201cAs a new user, I want to verify my email so I can access my account.\u201d<\/p>\n<p>Break this into:<\/p>\n<ul>\n<li>As a new user, I want to receive a verification email after signing up so I can confirm my identity.<\/li>\n<li>As a new user, I want to click the verification link in my email so I can activate my account.<\/li>\n<li>As a new user, I want to see a success message after verification so I know I can log in.<\/li>\n<\/ul>\n<p>Each story delivers a visible, testable outcome\u2014no dependency on the others.<\/p>\n<h3>2. Slice by Conditional Logic (If-Then Scenarios)<\/h3>\n<p>When a feature depends on different user paths or data states, split by decision points.<\/p>\n<p><strong>Example:<\/strong> \u201cAs a customer, I want to apply a discount code so I can reduce my order total.\u201d<\/p>\n<p>Break down by conditions:<\/p>\n<ul>\n<li>As a customer, I want to enter a valid discount code so I can see my updated total.<\/li>\n<li>As a customer, I want to know if my discount code is expired so I can try another.<\/li>\n<li>As a customer, I want to know if my code doesn\u2019t apply to my current items so I can adjust my cart.<\/li>\n<\/ul>\n<p>This approach ensures every possible user path is covered without bloating a single story.<\/p>\n<h3>3. Slice by Data or Object Type<\/h3>\n<p>When a feature applies across multiple entities (e.g., users, orders, products), split by the object.<\/p>\n<p><strong>Example:<\/strong> \u201cAs a manager, I want to report on team performance.\u201d<\/p>\n<p>Split by data type:<\/p>\n<ul>\n<li>As a manager, I want to see the number of tasks completed per team member so I can assess productivity.<\/li>\n<li>As a manager, I want to see average time to complete tasks per team member so I can identify bottlenecks.<\/li>\n<li>As a manager, I want to filter performance reports by date range so I can analyze trends.<\/li>\n<\/ul>\n<p>Each story focuses on one data dimension, making it easier to verify and track.<\/p>\n<h3>4. Slice by Integration Layer (High-Level vs. Deep)<\/h3>\n<p>Split based on depth of interaction. Start with a high-level view, then add layers of detail.<\/p>\n<p><strong>Example:<\/strong> \u201cAs a user, I want to upload and manage files.\u201d<\/p>\n<p>Slice by depth:<\/p>\n<ul>\n<li>As a user, I want to upload a file so I can share it with others.<\/li>\n<li>As a user, I want to rename my uploaded file so I can identify it later.<\/li>\n<li>As a user, I want to delete a file I no longer need so I can reduce clutter.<\/li>\n<\/ul>\n<p>Start with the core functionality, then enhance. This builds trust in delivery and allows early feedback.<\/p>\n<h3>5. Slice by Business Rule or Validation<\/h3>\n<p>When a feature involves validation logic (e.g., eligibility, limits, permissions), break it into rule-based stories.<\/p>\n<p><strong>Example:<\/strong> \u201cAs a user, I want to book a session so I can schedule a meeting.\u201d<\/p>\n<p>Split by rule:<\/p>\n<ul>\n<li>As a user, I want to book a session if I have a valid profile and available time.<\/li>\n<li>As a user, I want to be blocked from booking if I have an active session within 24 hours.<\/li>\n<li>As a user, I want to be informed if the session is outside my availability window.<\/li>\n<\/ul>\n<p>Each story tests one rule\u2014no ambiguity, no overlap.<\/p>\n<h3>6. Slice by Minimum Viable Functionality (MVF)<\/h3>\n<p>Start with the smallest piece of functionality that still delivers value\u2014then expand.<\/p>\n<p><strong>Example:<\/strong> \u201cAs a customer, I want to filter search results by price.\u201d<\/p>\n<p>MVF slice:<\/p>\n<ul>\n<li>As a customer, I want to see a price filter on the search page so I can narrow results by budget.<\/li>\n<\/ul>\n<p>Later add:<\/p>\n<ul>\n<li>As a customer, I want to select a minimum and maximum price so I can define a custom range.<\/li>\n<li>As a customer, I want to see how many results match my filter so I can assess relevance.<\/li>\n<\/ul>\n<p>Start small. Validate. Iterate. This avoids over-engineering and keeps teams focused.<\/p>\n<h2>Decision Framework: Which Slicing Pattern to Use?<\/h2>\n<p>Choosing the right pattern depends on context. Use this quick guide to decide:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Use Case<\/th>\n<th>Best Slicing Pattern<\/th>\n<\/tr>\n<tr>\n<td>Onboarding, checkout, account setup<\/td>\n<td>User Journey<\/td>\n<\/tr>\n<tr>\n<td>Conditional logic (e.g., eligibility, rules)<\/td>\n<td>Conditional Logic<\/td>\n<\/tr>\n<tr>\n<td>Multiple data types (users, orders, products)<\/td>\n<td>Data\/Type Slice<\/td>\n<\/tr>\n<tr>\n<td>Deep feature with multiple features<\/td>\n<td>Integration Layer (High-Level \u2192 Deep)<\/td>\n<\/tr>\n<tr>\n<td>Validation rules (e.g., limits, eligibility)<\/td>\n<td>Business Rule Slice<\/td>\n<\/tr>\n<tr>\n<td>Need to deliver fast, validate early<\/td>\n<td>Minimum Viable Functionality<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Don\u2019t force a pattern. Let the user\u2019s path and business need lead you.<\/p>\n<h2>When You Shouldn\u2019t Split<\/h2>\n<p>Sometimes, splitting isn\u2019t the answer. Ask:<\/p>\n<ul>\n<li>Would splitting reduce clarity or increase dependencies?<\/li>\n<li>Is the story already small enough to deliver in one sprint?<\/li>\n<li>Would splitting make it harder to test or verify?<\/li>\n<\/ul>\n<p>Some epics\u2014like launching a new system or migrating data\u2014require full delivery. Splitting isn\u2019t always beneficial.<\/p>\n<p>My rule: if the story can\u2019t be tested independently, it\u2019s not ready for slicing. If splitting creates more than two stories that still depend on each other, reconsider.<\/p>\n<h2>Expert Tips for Safe and Sustainable Slicing<\/h2>\n<ul>\n<li><strong>Use the \u201cSo That\u201d clause as a litmus test.<\/strong> If the \u201cso that\u201d part isn\u2019t testable or meaningful, the story is too broad.<\/li>\n<li><strong>Review with both users and developers.<\/strong> A story that seems small from the product side might require complex data work. Collaborate.<\/li>\n<li><strong>Always link back to the original epic.<\/strong> Every split should trace to the original user need. Use visual story mapping to maintain alignment.<\/li>\n<li><strong>Test your splits.<\/strong> Can the story be delivered in one sprint? Can it be tested in isolation? If not, it\u2019s too big.<\/li>\n<li><strong>Track value delivery.<\/strong> Use acceptance criteria to show how the story improves user experience or business outcome.<\/li>\n<\/ul>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if a story is too big to split?<\/h3>\n<p>A story is too big if it requires multiple sprints to deliver, involves more than two teams, or lacks a clear definition of done. If you can\u2019t test it independently, it\u2019s not small enough. Apply the INVEST criteria: if it\u2019s not estimable or testable, it\u2019s not ready.<\/p>\n<h3>Can I split an epic by technical component (frontend, backend, API)?<\/h3>\n<p>Not recommended. Splitting by technical layer often creates stories that aren\u2019t user-focused. A story like \u201cDevelop login API endpoint\u201d is a task, not a story. Instead, focus on user value, even when it involves multiple layers.<\/p>\n<h3>Do I need to split every epic before sprint planning?<\/h3>\n<p>No. Not all epics require splitting. Some are naturally small. But if an epic is too large to fit in a sprint, it should be broken down during backlog refinement. Prioritize splitting high-impact or high-risk epics.<\/p>\n<h3>What if my team disagrees on how to split a story?<\/h3>\n<p>Use collaboration\u2014run a refinement workshop. Bring together product, dev, QA, and UX. Ask: \u201cWhat value does this story deliver?\u201d \u201cWho benefits?\u201d \u201cCan we test this independently?\u201d Focus on user impact, not technical convenience.<\/p>\n<h3>How can I ensure I\u2019m not losing user intent when splitting?<\/h3>\n<p>Always return to the original \u201cas a\u2026 I want\u2026 so that\u2026\u201d structure. Ask: \u201cDoes this split still reflect the user\u2019s goal?\u201d If not, go back. Use story mapping to visualize the whole journey and ensure no step is missing.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Large epics often be [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1102,"menu_order":1,"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-1104","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>Splitting User Stories Without Losing Value<\/title>\n<meta name=\"description\" content=\"Learn proven epic breakdown techniques and story slicing patterns to split large user stories into smaller, valuable, and testable chunks while preserving user intent. Improve Agile delivery with expert-driven guidance.\" \/>\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\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Splitting User Stories Without Losing Value\" \/>\n<meta property=\"og:description\" content=\"Learn proven epic breakdown techniques and story slicing patterns to split large user stories into smaller, valuable, and testable chunks while preserving user intent. Improve Agile delivery with expert-driven guidance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:10:23+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/\",\"name\":\"Splitting User Stories Without Losing Value\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:35:57+00:00\",\"dateModified\":\"2026-03-02T09:10:23+00:00\",\"description\":\"Learn proven epic breakdown techniques and story slicing patterns to split large user stories into smaller, valuable, and testable chunks while preserving user intent. Improve Agile delivery with expert-driven guidance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Refinement, Slicing, and Collaboration\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"How to Split Epic Stories Without Losing Value\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-TW\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Splitting User Stories Without Losing Value","description":"Learn proven epic breakdown techniques and story slicing patterns to split large user stories into smaller, valuable, and testable chunks while preserving user intent. Improve Agile delivery with expert-driven guidance.","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\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/","og_locale":"zh_TW","og_type":"article","og_title":"Splitting User Stories Without Losing Value","og_description":"Learn proven epic breakdown techniques and story slicing patterns to split large user stories into smaller, valuable, and testable chunks while preserving user intent. Improve Agile delivery with expert-driven guidance.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","article_modified_time":"2026-03-02T09:10:23+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"7 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/","name":"Splitting User Stories Without Losing Value","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:35:57+00:00","dateModified":"2026-03-02T09:10:23+00:00","description":"Learn proven epic breakdown techniques and story slicing patterns to split large user stories into smaller, valuable, and testable chunks while preserving user intent. Improve Agile delivery with expert-driven guidance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/splitting-user-stories-without-losing-value\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Refinement, Slicing, and Collaboration","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/"},{"@type":"ListItem","position":4,"name":"How to Split Epic Stories Without Losing Value"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website","url":"https:\/\/skills.visual-paradigm.com\/tw\/","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/tw\/","logo":{"@type":"ImageObject","inLanguage":"zh-TW","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1104\/revisions"}],"predecessor-version":[{"id":2408,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1104\/revisions\/2408"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1102"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=1104"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=1104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}