{"id":1804,"date":"2026-02-25T10:46:12","date_gmt":"2026-02-25T10:46:12","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/"},"modified":"2026-03-02T09:11:19","modified_gmt":"2026-03-02T09:11:19","slug":"incremental-planning-agile-multi-team-releases","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/","title":{"rendered":"Coordinating Incremental Releases Through Story Planning"},"content":{"rendered":"<p>Imagine a product launch where three teams ship independently\u2014each convinced they\u2019re on track. Then, integration fails. The app crashes under load. The business value stalls. It\u2019s not a rare incident. It\u2019s the default when teams operate in isolation, even with Agile practices in place.<\/p>\n<p>The real challenge isn\u2019t writing good stories. It\u2019s ensuring they converge in a way that delivers a working, tested increment at the end of each cycle. This is where incremental planning agile becomes essential\u2014not as a process, but as a mindset.<\/p>\n<p>Over two decades of coaching enterprise teams has taught me this: alignment isn\u2019t achieved through more meetings, more documents, or more tools. It\u2019s achieved through shared understanding, deliberate synchronization, and a focus on flow.<\/p>\n<p>This chapter walks you through how to coordinate story delivery across multiple teams toward cohesive, integrated, and valuable increments. You\u2019ll learn how to avoid dependency traps, align refinements, and apply lightweight coordination patterns that scale without slowing down.<\/p>\n<h2>Why Incremental Planning Agile Is Non-Negotiable at Scale<\/h2>\n<p>At scale, \u201cworking software\u201d is not just a sum of team outputs. It\u2019s the result of interlocking deliveries that must be tested, validated, and released as a unified whole.<\/p>\n<p>Most teams start with a shared sprint goal. But in large programs, sprint goals are rarely enough. A shared vision of what \u201cdone\u201d means across teams\u2014especially when they use different tools, workflows, or definitions of done\u2014must be established early.<\/p>\n<p>Consider this: one team ships a payment processing feature. Another updates the user profile service. The third adds logging. All are \u201cdone\u201d in their own sprint\u2014but the combined system fails integration because the new logs aren\u2019t compatible with the existing monitoring stack.<\/p>\n<p>This isn\u2019t a failure of individual teams. It\u2019s a failure of coordination. Incremental planning agile solves this by ensuring every story contributes to a shared, testable, deployable increment\u2014not just a team-level completion.<\/p>\n<h3>What Gets Lost Without Incremental Planning<\/h3>\n<p>Without alignment, you end up with:<\/p>\n<ul>\n<li>Integration chaos<\/li>\n<li>Re-works due to misaligned assumptions<\/li>\n<li>Hidden dependencies<\/li>\n<li>Delayed value delivery<\/li>\n<li>Distrust between teams<\/li>\n<\/ul>\n<p>These aren\u2019t just operational headaches. They erode trust in Agile itself.<\/p>\n<h2>Core Principles of Incremental Planning Agile<\/h2>\n<p>Successful coordination isn\u2019t about control. It\u2019s about clarity, visibility, and shared ownership.<\/p>\n<h3>1. Define the Increment Upfront<\/h3>\n<p>Before any team starts, define what a \u201cdone\u201d increment looks like at the program level. It\u2019s not just \u201cworking code.\u201d It\u2019s:<\/p>\n<ul>\n<li>Tested across all services<\/li>\n<li>Deployable in staging without manual rework<\/li>\n<li>Validated against end-to-end scenarios<\/li>\n<li>Documentation and monitoring updated<\/li>\n<\/ul>\n<p>This shared definition becomes the North Star. It ensures that every team knows what \u201cdone\u201d means\u2014not just \u201cdone in their backlog,\u201d but \u201cdone in the product.\u201d<\/p>\n<h3>2. Sync Refinement Across Teams<\/h3>\n<p>Story refinement shouldn\u2019t happen in silos. If Team A breaks down a story and Team B proceeds with their own, misalignment is inevitable.<\/p>\n<p>Use synchronized refinement sessions\u2014either in real time or as a cadence. For example:<\/p>\n<ol>\n<li>Host a weekly cross-team refinement session.<\/li>\n<li>Use a shared backlog in a tool like Visual Paradigm.<\/li>\n<li>Focus on stories that span teams or depend on shared components.<\/li>\n<\/ol>\n<p>This prevents \u201clocal optimization\u201d and ensures dependencies are visible and managed early.<\/p>\n<h3>3. Use a Shared Planning Cadence<\/h3>\n<p>Align sprint lengths across teams. If one team works 2-week sprints and another does 3, coordination becomes messy.<\/p>\n<p>Even better: use a fixed planning cycle\u2014like a PI (Program Increment) in SAFe\u2014but break it down into smaller, synchronized increments.<\/p>\n<p>For example:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Team<\/th>\n<th>Sprint<\/th>\n<th>Increment Target<\/th>\n<\/tr>\n<tr>\n<td>Payments<\/td>\n<td>1<\/td>\n<td>Refund logic ready for testing<\/td>\n<\/tr>\n<tr>\n<td>User Profile<\/td>\n<td>1<\/td>\n<td>Updated schema and API contract<\/td>\n<\/tr>\n<tr>\n<td>Analytics<\/td>\n<td>1<\/td>\n<td>Data pipeline updated to handle new event<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>All teams commit to delivering toward a shared increment. The result? A testable, deployable product at the end of the cycle.<\/p>\n<h3>4. Visualize Dependencies Early<\/h3>\n<p>Dependencies block flow. But too many teams treat them as \u201cunknowns\u201d until sprint planning.<\/p>\n<p>Use dependency maps\u2014simple visual models showing:<\/p>\n<ul>\n<li>Which stories depend on others<\/li>\n<li>Who owns which component<\/li>\n<li>Who needs to sign off on integration<\/li>\n<\/ul>\n<p>Update this map weekly. Share it in sprint planning and refinement meetings.<\/p>\n<h2>Leveraging Decision Tables to Manage Multi-Team Increments<\/h2>\n<p>When multiple teams deliver stories toward a shared increment, decisions must be consistent. Use decision tables to model complex conditions and ensure alignment.<\/p>\n<p>For example, when does a feature qualify as \u201cready for release\u201d? Consider this decision table:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Condition<\/th>\n<th>Yes<\/th>\n<th>No<\/th>\n<\/tr>\n<tr>\n<td>All dependent stories completed?<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Integration testing passed?<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Documentation updated?<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Monitoring hooks in place?<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<td>Team sign-off confirmed?<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<\/tr>\n<tr>\n<th>Action<\/th>\n<td>Proceed to release<\/td>\n<td>Block release. Resolve open items.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This isn\u2019t bureaucracy. It\u2019s a shared standard that prevents \u201cwe thought it was ready\u201d moments.<\/p>\n<h3>When to Use Decision Tables<\/h3>\n<ul>\n<li>When multiple teams share a feature<\/li>\n<li>When integration risk is high<\/li>\n<li>When compliance or audit trails are needed<\/li>\n<li>When stakeholders demand predictability<\/li>\n<\/ul>\n<p>They\u2019re not for every story. But for high-impact, cross-team work, they\u2019re invaluable.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with the best intentions, things go wrong. Here are the most frequent issues and how to fix them:<\/p>\n<h3>1. Over-Reliance on Sprint Goals<\/h3>\n<p>Sprint goals are important\u2014but they\u2019re not sufficient. A sprint goal like \u201cImprove checkout\u201d doesn\u2019t tell you what \u201cimproved\u201d means across teams.<\/p>\n<p><strong>Solution:<\/strong> Pair sprint goals with a shared increment definition. Example: \u201cAll checkout steps are tested in integration, with error tracing and fallback enabled.\u201d<\/p>\n<h3>2. Hidden Dependencies<\/h3>\n<p>Teams often don\u2019t know about shared components until it\u2019s too late. One team updates a library. The next team breaks.<\/p>\n<p><strong>Solution:<\/strong> Use a dependency log. Tag every story that affects or depends on shared components. Review it in every refinement.<\/p>\n<h3>3. Inconsistent Definitions of \u201cDone\u201d<\/h3>\n<p>One team considers deployment to staging \u201cdone.\u201d Another requires acceptance testing. This causes integration chaos.<\/p>\n<p><strong>Solution:<\/strong> Define a \u201cprogram-level\u201d Definition of Done. Make it visible, shared, and auditable. Use it as a checklist in release planning.<\/p>\n<h3>4. Lack of Feedback Loops<\/h3>\n<p>Integration failures only surface at the end of a cycle. By then, rework is expensive.<\/p>\n<p><strong>Solution:<\/strong> Run weekly integration tests. Use CI\/CD pipelines to validate every story that\u2019s part of a shared increment.<\/p>\n<h2>Real-World Example: Coordinating a Payment Gateway Release<\/h2>\n<p>At a financial services platform, three teams worked on a new payment gateway:<\/p>\n<ul>\n<li><strong>Team A:<\/strong> Handles payment processing (API, error handling)<\/li>\n<li><strong>Team B:<\/strong> Manages transaction logging and auditing<\/li>\n<li><strong>Team C:<\/strong> Powers the UI and user notifications<\/li>\n<\/ul>\n<p>They followed these steps:<\/p>\n<ol>\n<li>Defined the shared increment: <em>\u201cA fully tested, deployable payment gateway that processes transactions, logs them, and notifies users.\u201d<\/em><\/li>\n<li>Created a dependency map showing that Team C must wait for Team A\u2019s API contract.<\/li>\n<li>Agreed on a shared Definition of Done: includes integration tests, logging hooks, and UI validation.<\/li>\n<li>Used a decision table to approve the release.<\/li>\n<li>Conducted weekly integration tests.<\/li>\n<\/ol>\n<p>The result? A working increment in 3 weeks\u2014without a single integration failure.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How often should teams synchronize for incremental planning agile?<\/h3>\n<p>At minimum, conduct a joint refinement session once per sprint. If dependencies are high, do it bi-weekly. The goal is to keep alignment visible and dynamic.<\/p>\n<h3>Can teams with different sprint lengths still coordinate increments?<\/h3>\n<p>Yes\u2014but sync their delivery cycles. Use a common release calendar. Align the end of each increment to a fixed date, regardless of sprint length. This avoids \u201csprint drift.\u201d<\/p>\n<h3>What if a dependency blocks a story from being completed?<\/h3>\n<p>Use dependency flags in your backlog. Flag it as \u201cblocked.\u201d Document who owns the resolution. Escalate to the Agile Release Train (ART) or Scrum of Scrums if unresolved after 3 days.<\/p>\n<h3>How do we ensure all teams follow the same Definition of Done?<\/h3>\n<p>Establish a shared DoD at the program level. Have a cross-team working group review and update it quarterly. Make it visible via dashboards and information radiators.<\/p>\n<h3>How do decision tables improve release coordination agile?<\/h3>\n<p>They turn subjective judgment into objective, repeatable decisions. They prevent \u201cwe thought it was ready\u201d moments and ensure that all teams agree on what \u201cready\u201d means.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Imagine a product launch where three teams ship independently\u2014each convinced they\u2019re on track. Then, integration fails. The app crashes under load. The business value stalls. It\u2019s not a rare incident. It\u2019s the default when teams operate in isolation, even with Agile practices in place. The real challenge isn\u2019t writing good stories. It\u2019s ensuring they converge [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1801,"menu_order":2,"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-1804","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>Incremental Planning Agile: Synchronizing Multi-Team Releases<\/title>\n<meta name=\"description\" content=\"Master incremental planning agile to align multi-team increments and ensure predictable, value-driven releases. Learn proven coordination techniques for large-scale agile projects.\" \/>\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\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Incremental Planning Agile: Synchronizing Multi-Team Releases\" \/>\n<meta property=\"og:description\" content=\"Master incremental planning agile to align multi-team increments and ensure predictable, value-driven releases. Learn proven coordination techniques for large-scale agile projects.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:11:19+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/\",\"name\":\"Incremental Planning Agile: Synchronizing Multi-Team Releases\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:46:12+00:00\",\"dateModified\":\"2026-03-02T09:11:19+00:00\",\"description\":\"Master incremental planning agile to align multi-team increments and ensure predictable, value-driven releases. Learn proven coordination techniques for large-scale agile projects.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Supporting Practices and Scaled Facilitation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Coordinating Incremental Releases Through Story Planning\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Incremental Planning Agile: Synchronizing Multi-Team Releases","description":"Master incremental planning agile to align multi-team increments and ensure predictable, value-driven releases. Learn proven coordination techniques for large-scale agile projects.","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\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/","og_locale":"id_ID","og_type":"article","og_title":"Incremental Planning Agile: Synchronizing Multi-Team Releases","og_description":"Master incremental planning agile to align multi-team increments and ensure predictable, value-driven releases. Learn proven coordination techniques for large-scale agile projects.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/","og_site_name":"Visual Paradigm Skills Indonesia","article_modified_time":"2026-03-02T09:11:19+00:00","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"6 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/","name":"Incremental Planning Agile: Synchronizing Multi-Team Releases","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:46:12+00:00","dateModified":"2026-03-02T09:11:19+00:00","description":"Master incremental planning agile to align multi-team increments and ensure predictable, value-driven releases. Learn proven coordination techniques for large-scale agile projects.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/incremental-planning-agile-multi-team-releases\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Supporting Practices and Scaled Facilitation","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/"},{"@type":"ListItem","position":4,"name":"Coordinating Incremental Releases Through Story Planning"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1804","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1804\/revisions"}],"predecessor-version":[{"id":2413,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1804\/revisions\/2413"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1801"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1804"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1804"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}