{"id":1816,"date":"2026-02-25T10:46:16","date_gmt":"2026-02-25T10:46:16","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/"},"modified":"2026-02-25T10:46:16","modified_gmt":"2026-02-25T10:46:16","slug":"multi-vendor-agile-story-integration","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/","title":{"rendered":"Agile in Vendor and Multi-Partner Ecosystems"},"content":{"rendered":"<p>When an enterprise product relies on external vendors, each contributing distinct capabilities, the challenge isn\u2019t just technical integration\u2014it\u2019s aligning story ownership, delivery rhythm, and shared understanding across organizational boundaries.<\/p>\n<p>Too often, teams treat vendor work as a black box, handing off artifacts without clear story traceability or joint acceptance. That\u2019s where agility breaks down. The real issue isn\u2019t complexity\u2014it\u2019s a lack of shared process ownership.<\/p>\n<p>I\u2019ve guided over 30 large-scale integrations where vendor teams were on equal footing with internal squads. What consistently failed? Assumptions. What worked? A documented, collaborative story model grounded in <strong>partner collaboration agile<\/strong> principles.<\/p>\n<p>Here, you\u2019ll learn how to define joint story ownership, model cross-ecosystem dependencies, and embed <strong>vendor integration agile<\/strong> practices into your sprint cycles\u2014without sacrificing speed, quality, or accountability.<\/p>\n<h2>Establishing Shared Story Ownership Across Organizations<\/h2>\n<p>Ownership isn\u2019t a binary state. In multi-vendor agile, it\u2019s a spectrum.<\/p>\n<p>When two teams\u2014one internal, one vendor\u2014develop a shared interface, the user story must reflect joint accountability. Ownership isn\u2019t about who writes the story, but who ensures it delivers value.<\/p>\n<p>Use this three-part ownership model:<\/p>\n<ul>\n<li><strong>Primary Owner<\/strong> \u2013 The team responsible for sprint execution and daily progress.<\/li>\n<li><strong>Shared Owner<\/strong> \u2013 The partner (vendor or internal) who co-defines acceptance criteria and reviews outcomes.<\/li>\n<li><strong>Business Owner<\/strong> \u2013 The stakeholder who signs off on value delivery and prioritization.<\/li>\n<\/ul>\n<p>Each role is tied to a specific accountability. The business owner ensures alignment with strategy. The shared owner enables real-time feedback. The primary owner delivers the work.<\/p>\n<p>Never assign ownership to a single team when the story spans systems. If a payment gateway integration depends on both your backend and a third-party API, both teams must co-own the story.<\/p>\n<h3>Key Practice: Joint Story Refinement<\/h3>\n<p>Hold cross-organizational refinement sessions at least weekly. Invite both primary and shared owners from each team.<\/p>\n<p>Use a shared digital workspace. All stories must include:<\/p>\n<ul>\n<li>Clear user role and value statement<\/li>\n<li>Joint acceptance criteria (with vendor sign-off)<\/li>\n<li>Defined interface contract (OpenAPI or equivalent)<\/li>\n<li>Shared definition of &#171;Done&#187; (DoD)<\/li>\n<\/ul>\n<p>These aren\u2019t formalities. They are alignment checkpoints. Without them, you\u2019re building to different specs\u2014no matter how similar the intent.<\/p>\n<h2>Modeling Dependencies Across Vendor Boundaries<\/h2>\n<p>Dependencies in multi-vendor agile aren\u2019t just technical\u2014they\u2019re operational, contractual, and cultural.<\/p>\n<p>When a story depends on a vendor&#8217;s deliverable, it&#8217;s not just a &#171;wait for X.&#187; It&#8217;s a dependency with risk, timing, and accountability.<\/p>\n<p>Use a decision table to model the risk and ownership of cross-vendor dependencies:<\/p>\n<table>\n<thead>\n<tr>\n<th>Dependency Type<\/th>\n<th>Risk Level<\/th>\n<th>Owner<\/th>\n<th>Response Action<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>API Contract Finalized<\/td>\n<td>High<\/td>\n<td>Shared Owner<\/td>\n<td>Joint validation sprint<\/td>\n<\/tr>\n<tr>\n<td>Vendor Milestone Delay<\/td>\n<td>High<\/td>\n<td>Business Owner<\/td>\n<td>Re-prioritize story or adjust timeline<\/td>\n<\/tr>\n<tr>\n<td>Interface Changes Required<\/td>\n<td>Medium<\/td>\n<td>Primary Owner (Internal)<\/td>\n<td>Notify vendor 72h in advance<\/td>\n<\/tr>\n<tr>\n<td>Security Review Pending<\/td>\n<td>High<\/td>\n<td>Shared Owner<\/td>\n<td>Block integration until cleared<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table isn\u2019t for documentation\u2014it\u2019s for decision-making. It forces clarity on risk ownership and response protocols.<\/p>\n<p>Never treat a vendor\u2019s delivery as a \u201ctrusted\u201d handoff. Assume variability. Plan for buffer cycles. And use the decision table to communicate expectations.<\/p>\n<h3>Pro Tip: Use Interface Contracts as Acceptance Criteria<\/h3>\n<p>Instead of vague acceptance criteria like &#171;API works as expected,&#187; define them using OpenAPI or JSON Schema.<\/p>\n<p><code>Given the user is logged in<\/code><br \/>\n    <code>When they submit a payment request<\/code><br \/>\n    <code>Then the vendor API must return a 202 Accepted with { \"transactionId\": \"string\", \"status\": \"pending\" }<\/code><\/p>\n<p>This is not just technical precision. It\u2019s a shared language. It eliminates ambiguity, prevents rework, and enables automated validation.<\/p>\n<h2>Embedding Vendor Integration Agile into Your Workflow<\/h2>\n<p>Agile isn\u2019t a process\u2014it\u2019s a mindset. But in multi-vendor ecosystems, the mindset must include <strong>vendor integration agile<\/strong> practices.<\/p>\n<p>Here\u2019s how to integrate them into your sprint rhythm:<\/p>\n<ol>\n<li><strong>Pre-Sprint Sync (Tuesday)<\/strong> \u2013 Joint refinement and dependency mapping. All teams present story blockers.<\/li>\n<li><strong>Mid-Sprint Checkpoint (Thursday)<\/strong> \u2013 Review progress, confirm interface stability, validate API contracts.<\/li>\n<li><strong>Post-Sprint Review (Friday)<\/strong> \u2013 Demo using real vendor data. Include both teams in acceptance.<\/li>\n<\/ol>\n<p>These aren\u2019t extra meetings. They\u2019re part of the flow. If your vendor isn\u2019t in the room, they\u2019re not in the sprint.<\/p>\n<p>Use a shared Kanban board across teams. Visualize all stories, including vendor-dependent ones. Color-code by dependency risk. Tag each card with its owner and expected handoff date.<\/p>\n<p>When you see a story stuck in \u201cWaiting for Vendor,\u201d don\u2019t just wait. Flag it. Escalate. And ask: What\u2019s blocking the handoff? Is it design? Code? Testing?<\/p>\n<h3>Key Practice: Shared Definition of Done<\/h3>\n<p>At scale, \u201cDone\u201d means different things for different teams. But for cross-vendor stories, it must be the same.<\/p>\n<p>Define a shared DoD with vendor teams:<\/p>\n<ul>\n<li>Code committed and peer-reviewed<\/li>\n<li>API contract approved and versioned<\/li>\n<li>Unit and integration tests passing<\/li>\n<li>Security scan passed (SAST\/DAST)<\/li>\n<li>Documentation updated<\/li>\n<li>Deploys to shared integration environment<\/li>\n<li>Validated via joint user acceptance test (UAT)<\/li>\n<\/ul>\n<p>Without this, \u201cDone\u201d is a myth. You\u2019re just moving stories around.<\/p>\n<h2>Managing Conflict and Alignment Across Partners<\/h2>\n<p>Disagreements aren\u2019t failures. They\u2019re signals.<\/p>\n<p>In one project, a vendor\u2019s implementation didn\u2019t match the agreed interface. The internal team wanted to reject it. The vendor insisted it was \u201cfunctionally equivalent.\u201d<\/p>\n<p>Instead of escalating, we held a joint story review. We mocked the interface in real time. The gap wasn\u2019t in code\u2014it was in assumptions. The vendor didn\u2019t understand the user context.<\/p>\n<p>We redefined the story with clearer scenarios. The new acceptance criteria included user journey mapping. The vendor delivered correctly the next sprint.<\/p>\n<p>Conflict is inevitable. But with transparency, shared ownership, and a focus on value, it becomes a force for alignment.<\/p>\n<h3>Conflict Resolution Framework<\/h3>\n<p>When disagreements arise:<\/p>\n<ol>\n<li>Revisit the user story and acceptance criteria.<\/li>\n<li>Ask: \u201cWhat does the user actually need?\u201d<\/li>\n<li>Recreate the scenario in a shared sandbox.<\/li>\n<li>Confirm the outcome with the business owner.<\/li>\n<li>Update the story together. No blame.<\/li>\n<\/ol>\n<p>This is <strong>partner collaboration agile<\/strong> in action. It\u2019s not about winning\u2014it\u2019s about delivering value, together.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do we handle vendor teams that don\u2019t follow our Agile process?<\/h3>\n<p>Start by understanding their constraints. Then co-create a lightweight process that respects both sides. Use shared backlogs, joint ceremonies, and common DoD. Treat it as a partnership, not a command.<\/p>\n<h3>What if the vendor is on a different sprint schedule?<\/h3>\n<p>Synchronize through dependency planning. Use buffer sprints or overlapping planning cycles. Mark dependencies clearly in your board. The goal is flow, not strict alignment.<\/p>\n<h3>How do we ensure quality when the vendor\u2019s code is not in our CI\/CD pipeline?<\/h3>\n<p>Integrate vendor builds into your pipeline. Use API gateways or shared artifact repositories. Run automated checks on every handoff. Quality is a shared responsibility.<\/p>\n<h3>Can we use story points when working with external vendors?<\/h3>\n<p>Yes\u2014but only if both teams agree on the scale. Or better: use flow metrics (lead time, cycle time) instead. They\u2019re objective, measurable, and easier to compare across organizations.<\/p>\n<h3>What if a vendor doesn\u2019t respond during refinement?<\/h3>\n<p>Flag it early. Escalate to business owners. If still unresponsive, mark the story as \u201cBlocked\u201d and plan for alternative paths. Never assume silence means agreement.<\/p>\n<h3>How do we handle intellectual property when stories are co-developed?<\/h3>\n<p>Define IP terms in your contract. Use shared repositories with role-based access. Clarify who owns what parts of the story, code, and deliverables. When in doubt, document it.<\/p>\n<p>Successful multi-vendor agile isn\u2019t about control. It\u2019s about trust, transparency, and shared purpose. When you treat each partner as a co-owner of the story, you unlock true agility at scale.<\/p>\n<p>Remember: alignment starts not with documentation, but with joint understanding. Build that first, and everything else follows.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When an enterprise product relies on external vendors, each contributing distinct capabilities, the challenge isn\u2019t just technical integration\u2014it\u2019s aligning story ownership, delivery rhythm, and shared understanding across organizational boundaries. Too often, teams treat vendor work as a black box, handing off artifacts without clear story traceability or joint acceptance. That\u2019s where agility breaks down. The [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1813,"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":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","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-1816","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>Multi Vendor Agile: Seamless Story Integration Across Partners<\/title>\n<meta name=\"description\" content=\"Master multi-vendor agile story integration with proven techniques for partner collaboration agile and vendor integration agile. Build aligned, high-flowing delivery across enterprises and third-party ecosystems.\" \/>\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\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Multi Vendor Agile: Seamless Story Integration Across Partners\" \/>\n<meta property=\"og:description\" content=\"Master multi-vendor agile story integration with proven techniques for partner collaboration agile and vendor integration agile. Build aligned, high-flowing delivery across enterprises and third-party ecosystems.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/\",\"name\":\"Multi Vendor Agile: Seamless Story Integration Across Partners\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:46:16+00:00\",\"description\":\"Master multi-vendor agile story integration with proven techniques for partner collaboration agile and vendor integration agile. Build aligned, high-flowing delivery across enterprises and third-party ecosystems.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Lessons and Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Agile in Vendor and Multi-Partner Ecosystems\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Multi Vendor Agile: Seamless Story Integration Across Partners","description":"Master multi-vendor agile story integration with proven techniques for partner collaboration agile and vendor integration agile. Build aligned, high-flowing delivery across enterprises and third-party ecosystems.","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\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/","og_locale":"ru_RU","og_type":"article","og_title":"Multi Vendor Agile: Seamless Story Integration Across Partners","og_description":"Master multi-vendor agile story integration with proven techniques for partner collaboration agile and vendor integration agile. Build aligned, high-flowing delivery across enterprises and third-party ecosystems.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"6 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/","name":"Multi Vendor Agile: Seamless Story Integration Across Partners","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:46:16+00:00","description":"Master multi-vendor agile story integration with proven techniques for partner collaboration agile and vendor integration agile. Build aligned, high-flowing delivery across enterprises and third-party ecosystems.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/multi-vendor-agile-story-integration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Real-World Lessons and Case Studies","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/"},{"@type":"ListItem","position":4,"name":"Agile in Vendor and Multi-Partner Ecosystems"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1816","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1816\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1813"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=1816"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=1816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}