{"id":1799,"date":"2026-02-25T10:46:10","date_gmt":"2026-02-25T10:46:10","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/"},"modified":"2026-02-25T10:46:10","modified_gmt":"2026-02-25T10:46:10","slug":"cross-team-validation-agile","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/","title":{"rendered":"Cross-Team Story Validation Through End-to-End Scenarios"},"content":{"rendered":"<p>At a major financial services platform, a new customer onboarding journey required integration between three independent teams: identity verification, account setup, and credit risk scoring. Each team had committed to delivering their part. But when it came time to test, the end-to-end flow failed\u2014partly because no one had validated how their service interacted with the others.<\/p>\n<p>That\u2019s the core challenge: delivering independently does not mean delivering correctly together. The mistake? Assuming that individual team acceptance criteria equate to system-level correctness. The fix? Validating stories through end-to-end agile scenarios that span teams.<\/p>\n<p>This chapter dives into how to build and execute cross-team validation flows that ensure alignment without over-documentation. You\u2019ll learn how to design, track, and verify integrated user journeys across multiple teams\u2014using real-world techniques that work in practice, not just theory.<\/p>\n<h2>Why End-to-End Agile Scenarios Are Non-Negotiable<\/h2>\n<p>Agile teams often focus on their own stories. But customer value isn\u2019t delivered in isolation. A feature like \u201csecure onboarding\u201d isn\u2019t complete until the identity check, account creation, and risk assessment all work in sequence.<\/p>\n<p>Without end-to-end validation, we risk delivering a system that meets all internal criteria but fails the real user test.<\/p>\n<p>End-to-end agile scenarios are not just acceptance tests. They are shared narratives that capture the flow of a customer journey across multiple teams and systems. They serve as a common language for business, product, and engineering.<\/p>\n<p>For example, a single scenario like \u201cCustomer submits ID, gets account created, and receives risk score in under 2 minutes\u201d becomes a shared goal. It forces teams to coordinate, define interfaces, and test integration\u2014before the first line of code is deployed.<\/p>\n<h2>Building Integrated Release Planning Around Scenarios<\/h2>\n<p>Integrated release planning isn\u2019t just about scheduling features. It\u2019s about sequencing validation. Each story must be part of a narrative that leads to a business outcome.<\/p>\n<p>When planning, ask: \u201cWhat happens when all teams deliver their stories in sequence?\u201d This isn\u2019t hypothetical. It\u2019s where the real risk lies\u2014especially when teams are distributed across time zones or business units.<\/p>\n<p>Start by mapping your high-level customer journey. Break it into steps that represent handoffs between teams. Each step should be tied to a specific story or group of stories.<\/p>\n<p>Use this checklist to guide your planning:<\/p>\n<ul>\n<li>Identify the top 3\u20135 customer journeys that matter most to the business.<\/li>\n<li>For each journey, define the sequence of team-owned stories that contribute.<\/li>\n<li>Assign a single shared scenario that ties the steps together.<\/li>\n<li>Ensure each team understands their role in the narrative.<\/li>\n<li>Designate one team to own the end-to-end validation\u2014temporary ownership, not responsibility.<\/li>\n<\/ul>\n<p>That last point is critical. The team with the narrative ownership isn\u2019t necessarily the one that writes the most code. It\u2019s the one that ensures the story flows correctly across boundaries.<\/p>\n<h2>Designing Scenarios That Work Across Teams<\/h2>\n<p>Not all scenarios are created equal. The best ones are:<\/p>\n<ul>\n<li>**User-centered:** Written from the customer\u2019s point of view.<\/li>\n<li>**Testable:** Each step can be verified through automated or manual checks.<\/li>\n<li>**Independent of implementation:** They don\u2019t assume which technology or framework is used.<\/li>\n<li>**Shared across teams:** All involved parties can understand and contribute.<\/li>\n<\/ul>\n<p>Here\u2019s how to structure one:<\/p>\n<pre><code>Feature: Onboarding Workflow\n  As a new customer,\n  I want the system to verify my identity and set up my account in one flow,\n  So that I can start using the platform within minutes.\n\n  Scenario: Successful onboarding with verified ID and risk check\n    Given I am a new user\n    And I\u2019ve uploaded a valid government ID\n    When the identity verification team confirms the ID\n    Then the account creation team triggers account setup\n    And the risk scoring team begins evaluation\n    And all teams report success\n    Then I should receive a confirmation message with my account details\n<\/code><\/pre>\n<p>This scenario is written in Gherkin syntax but can be adapted to plain English. The key is that it\u2019s the same for all teams\u2014no ambiguity.<\/p>\n<h3>Assigning Roles in Scenario Execution<\/h3>\n<p>Who runs the test? Not always the team that owns the first story. In practice, one team takes the lead\u2014often the one that owns the final step or has the best integration visibility.<\/p>\n<p>Here\u2019s how to manage it:<\/p>\n<ol>\n<li>During backlog refinement, identify which scenarios are cross-team.<\/li>\n<li>Tag each scenario with the owning team (e.g., \u201cRisk Team: Scenario Owner\u201d)<\/li>\n<li>Set a shared deadline for validation, tied to the release date<\/li>\n<li>Use a shared test environment to run the full flow<\/li>\n<li>Automate the scenario using Cucumber, SpecFlow, or a custom test harness<\/li>\n<\/ol>\n<p>Make it a rule: no team can mark a story as \u201cDone\u201d until the end-to-end scenario passes.<\/p>\n<h2>Managing Dependencies Through Shared Scenarios<\/h2>\n<p>Dependencies are inevitable. But they don\u2019t have to be blockers. When teams use shared scenarios, dependencies become visible and manageable.<\/p>\n<p>Instead of waiting for a dependency to be \u201cready,\u201d use the scenario to define the interface. For example:<\/p>\n<ul>\n<li>\u201cWhen the identity team sends a verified ID signal, the account team must respond within 5 seconds.\u201d<\/li>\n<li>\u201cIf the risk team fails to return a score in under 60 seconds, the system should notify support.\u201d<\/li>\n<\/ul>\n<p>These aren\u2019t just acceptance criteria\u2014they\u2019re operational agreements.<\/p>\n<p>Use a dependency matrix to map each scenario to the teams involved:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Scenario<\/th>\n<th>Team 1<\/th>\n<th>Team 2<\/th>\n<th>Team 3<\/th>\n<th>Validation Owner<\/th>\n<\/tr>\n<tr>\n<td>Successful onboarding with verified ID<\/td>\n<td>Identity Verification<\/td>\n<td>Account Setup<\/td>\n<td>Risk Scoring<\/td>\n<td>Risk Scoring Team<\/td>\n<\/tr>\n<tr>\n<td>Onboarding with invalid ID<\/td>\n<td>Identity Verification<\/td>\n<td>Account Setup<\/td>\n<td>\u2014<\/td>\n<td>Identity Verification<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This matrix ensures clarity on responsibility and reduces rework.<\/p>\n<h2>Overcoming Common Pitfalls<\/h2>\n<p>Even with the best intentions, challenges arise. Here are the most common:<\/p>\n<h3>1. Scenario Overload<\/h3>\n<p>Don\u2019t try to validate every possible path. Start with the top 3\u20135 high-impact journeys. Add others only when needed.<\/p>\n<h3>2. Misaligned Timelines<\/h3>\n<p>Teams may deliver at different rates. Use a \u201cvalidation buffer\u201d of 2\u20133 days after the last team\u2019s delivery to ensure integration is tested.<\/p>\n<h3>3. \u201cDone\u201d Without Integration<\/h3>\n<p>Just because a team says \u201cDone\u201d doesn\u2019t mean the story is usable in context. Enforce the rule: no integration without end-to-end validation.<\/p>\n<h3>4. Poor Scenario Clarity<\/h3>\n<p>Scenarios must be written in plain language. Avoid technical jargon. If a business analyst and a developer can\u2019t agree on the meaning, rewrite it.<\/p>\n<h2>Why This Works in Practice<\/h2>\n<p>I\u2019ve seen teams reduce integration defects by 60% after introducing cross-team validation agile with end-to-end agile scenarios. The key isn\u2019t automation\u2014it\u2019s alignment.<\/p>\n<p>When teams agree on what \u201cworking\u201d means for a customer journey, they stop competing for technical perfection and start collaborating for real value.<\/p>\n<p>Integrated release planning becomes not a scheduling chore, but a rhythm of shared understanding. The system\u2019s reliability grows not from more testing, but from better coordination.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I start validating across teams when no one owns the end-to-end flow?<\/h3>\n<p>Choose a team with visibility into the full process\u2014often the one that owns the final outcome. Assign them temporary ownership of the scenario. Rotate ownership across sprints to avoid bottlenecks.<\/p>\n<h3>Can end-to-end agile scenarios replace traditional integration testing?<\/h3>\n<p>No. They complement it. Scenarios provide the narrative and business validation. Integration tests provide the technical verification. Use both.<\/p>\n<h3>What if teams use different testing frameworks?<\/h3>\n<p>Use a common format like Gherkin. The scenario is the contract. Tools can be different, but the meaning must be shared. Use a shared repository for all scenarios.<\/p>\n<h3>How often should cross-team scenarios be re-evaluated?<\/h3>\n<p>At least once per sprint. Revisit them during PI planning, backlog refinement, or when a major change occurs in a team\u2019s deliverables.<\/p>\n<h3>Do I need a central team to manage all scenarios?<\/h3>\n<p>No. Each product group or domain can manage its own set. The goal is local ownership with shared language. A central registry helps visibility but not control.<\/p>\n<h3>What if a team can\u2019t meet the scenario deadline?<\/h3>\n<p>Treat it as a risk. Flag it in the program board. Work with the team to adjust the release plan or add buffer time. The scenario must pass\u2014no exceptions.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At a major financial services platform, a new customer onboarding journey required integration between three independent teams: identity verification, account setup, and credit risk scoring. Each team had committed to delivering their part. But when it came time to test, the end-to-end flow failed\u2014partly because no one had validated how their service interacted with the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1792,"menu_order":6,"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-1799","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>Cross Team Validation Agile<\/title>\n<meta name=\"description\" content=\"Ensure integrated customer journeys with cross-team validation agile through end-to-end agile scenarios and integrated release planning. Optimize flow and alignment across teams.\" \/>\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\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cross Team Validation Agile\" \/>\n<meta property=\"og:description\" content=\"Ensure integrated customer journeys with cross-team validation agile through end-to-end agile scenarios and integrated release planning. Optimize flow and alignment across teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"7\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/\",\"name\":\"Cross Team Validation Agile\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:46:10+00:00\",\"description\":\"Ensure integrated customer journeys with cross-team validation agile through end-to-end agile scenarios and integrated release planning. Optimize flow and alignment across teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Advanced Story Patterns for Enterprises\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Cross-Team Story Validation Through End-to-End Scenarios\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Cross Team Validation Agile","description":"Ensure integrated customer journeys with cross-team validation agile through end-to-end agile scenarios and integrated release planning. Optimize flow and alignment across teams.","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\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/","og_locale":"de_DE","og_type":"article","og_title":"Cross Team Validation Agile","og_description":"Ensure integrated customer journeys with cross-team validation agile through end-to-end agile scenarios and integrated release planning. Optimize flow and alignment across teams.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/","name":"Cross Team Validation Agile","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:46:10+00:00","description":"Ensure integrated customer journeys with cross-team validation agile through end-to-end agile scenarios and integrated release planning. Optimize flow and alignment across teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/cross-team-validation-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Advanced Story Patterns for Enterprises","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/advanced-enterprise-story-patterns\/"},{"@type":"ListItem","position":4,"name":"Cross-Team Story Validation Through End-to-End Scenarios"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1799","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1799\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1792"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1799"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1799"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}