{"id":1782,"date":"2026-02-25T10:46:04","date_gmt":"2026-02-25T10:46:04","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/"},"modified":"2026-03-02T09:21:07","modified_gmt":"2026-03-02T09:21:07","slug":"communication-protocols-for-agile-at-scale","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/","title":{"rendered":"Communication Protocols for Agile at Scale"},"content":{"rendered":"<p>Every time a new feature request arrives at the enterprise level, it\u2019s not the stakeholder\u2019s need that matters most\u2014but how that need gets translated into actionable work across teams. The real bottleneck isn\u2019t complexity, but misalignment. Teams start building in isolation, only to discover too late that their work doesn\u2019t connect. That\u2019s the moment when communication in scaled agile fails.<\/p>\n<p>Most beginners focus on tools or ceremonies\u2014sprints, PI planning, daily stand-ups\u2014believing that structure alone ensures flow. But I\u2019ve seen countless programs stall not from lack of meetings, but from poor signal clarity. The real value lies in how teams share understanding, not just how often they meet.<\/p>\n<p>Over two decades, I\u2019ve worked with organizations across banking, healthcare, and SaaS\u2014each facing the same challenge: how to sustain agility when teams are scattered across time zones, domains, and technical stacks. The answer isn\u2019t more meetings. It\u2019s smarter communication protocols. This chapter will guide you through the rhythms, signals, and structures that keep large-scale Agile moving forward\u2014not just running.<\/p>\n<h2>Designing Effective Communication Rhythms<\/h2>\n<p>Not every interaction needs a meeting. The goal is to create a reliable, lightweight flow of insight across teams. Think of it like a nervous system: signals should travel quickly, remain clear, and not require constant reprocessing.<\/p>\n<p>At scale, communication can\u2019t rely on ad hoc conversations or email chains. Instead, adopt structured touchpoints that serve distinct purposes and align with the flow of work.<\/p>\n<h3>Core Synchronized Cadences<\/h3>\n<p>These are the foundational rhythms that keep all teams moving in the same direction. They\u2019re not about control\u2014they\u2019re about predictability.<\/p>\n<ul>\n<li><strong>Weekly Syncs (15\u201330 min):<\/strong> Small teams meet to align on dependencies, blockers, and upcoming work. Focus: transparency, not status reporting.<\/li>\n<li><strong>Biweekly Story Refinement (45\u201360 min):<\/strong> Cross-team sessions to break down epics, clarify acceptance criteria, and ensure shared understanding. Not for tasking\u2014only for clarity.<\/li>\n<li><strong>Program Increment (PI) Planning (2 days):<\/strong> The central event where all teams align on goals, features, and dependencies. It\u2019s not a scheduling exercise\u2014it\u2019s a collective understanding session.<\/li>\n<li><strong>Retrospective Sync (15 min):<\/strong> A brief, consistent check-in across teams to surface systemic issues and share improvements. No ownership needed\u2014just observation.<\/li>\n<\/ul>\n<p>These aren\u2019t rigid rules. They\u2019re guidelines. A software platform team in Sydney might run refinement every Monday and Thursday, while a compliance team in Frankfurt aligns every Tuesday and Friday. The key is consistency, not uniformity.<\/p>\n<h2>Scaling Ceremonies with Purpose<\/h2>\n<p>When we talk about scaled ceremonies, we\u2019re not just copying the Daily Scrum or Sprint Review. We\u2019re adapting them to serve cross-team coordination, not team-level status updates.<\/p>\n<p>Here\u2019s how to make scaled ceremonies work:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Ceremony<\/th>\n<th>Goal<\/th>\n<th>Duration<\/th>\n<th>Participants<\/th>\n<\/tr>\n<tr>\n<td>Refinement Sync<\/td>\n<td>Ensure shared understanding of stories across teams<\/td>\n<td>45\u201360 min<\/td>\n<td>Product Owners, Tech Leads, UX, QA<\/td>\n<\/tr>\n<tr>\n<td>Dependency Board Review<\/td>\n<td>Visualize and resolve inter-team blockers<\/td>\n<td>30\u201345 min<\/td>\n<td>Architecture, Delivery Leads<\/td>\n<\/tr>\n<tr>\n<td>PI Planning (Day 1 &amp; 2)<\/td>\n<td>Align features, epics, and team commitments<\/td>\n<td>2 days<\/td>\n<td>All Agile Teams, Scrum Masters, Product Management<\/td>\n<\/tr>\n<tr>\n<td>Retrospective Sync<\/td>\n<td>Share improvements, identify systemic risks<\/td>\n<td>15\u201320 min<\/td>\n<td>All Team Leads<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Each ceremony must answer one question: What do we need to understand *together*? If the answer isn\u2019t clear, the meeting is redundant.<\/p>\n<h3>Why Most Scaled Ceremonies Fail<\/h3>\n<p>Too many teams treat PI planning as a commitment race. They rush through story breakdowns and accept feature estimates without true alignment. The result? Unplanned work, rework, and frustration.<\/p>\n<p>I once worked with a fintech team that spent two weeks in a PI planning session only to discover that two core services were incompatible. The root cause? No one had reviewed the technical interface during refinement. Not a single person had asked, &#8222;How do we connect?&#8220;<\/p>\n<p>Here\u2019s the fix: <strong>Make dependency visibility a pre-requisite to commitment.<\/strong> Before any team signs up for a story, they must confirm it doesn\u2019t violate any known technical or organizational constraints.<\/p>\n<h2>Enabling Cross Team Communication Agile<\/h2>\n<p>Communication in scaled agile is not about more messages. It\u2019s about shared meaning. When everyone speaks the same language\u2014both verbally and visually\u2014misunderstandings drop.<\/p>\n<p>Here\u2019s how to build that shared language:<\/p>\n<ol>\n<li><strong>Define a common story format.<\/strong> Use \u201cAs a [role], I want [feature] so that [value]\u201d across all teams. Even if the role is a system or a process, keep it consistent.<\/li>\n<li><strong>Standardize acceptance criteria.<\/strong> Use Given-When-Then format. This creates a shared way to test and validate work.<\/li>\n<li><strong>Map dependency types.<\/strong> Label risks as: technical, business, resource, or process. This helps teams triage and respond faster.<\/li>\n<li><strong>Use shared visual artifacts.<\/strong> Story maps, dependency boards, value streams\u2014these aren\u2019t optional. They\u2019re how teams see the big picture.<\/li>\n<\/ol>\n<p>One client standardized their acceptance criteria across 12 teams. Within six months, story rework dropped by 40%. Not because of stricter control\u2014but because teams finally agreed on what \u201cdone\u201d meant.<\/p>\n<h3>Real-Time Feedback Loops<\/h3>\n<p>Feedback isn\u2019t just for retrospectives. It should happen during work.<\/p>\n<p>Use embedded feedback loops:<\/p>\n<ul>\n<li><strong>Pair programming across teams<\/strong> for shared features. Even for 30 minutes, it builds mutual understanding.<\/li>\n<li><strong>Designated \u201cconnectors\u201d<\/strong> between teams. Not managers\u2014just individuals with technical and domain fluency who can bridge gaps.<\/li>\n<\/ul>\n<p>One team in a logistics platform used a \u201cstory ambassador\u201d role. Every two weeks, the ambassador from each team met to review new stories and clarify any ambiguity. This reduced clarification cycles from 3\u20135 days to under 24 hours.<\/p>\n<h2>Decision-Making in Multi-Team Contexts<\/h2>\n<p>When multiple teams share ownership of a feature, decisions must be clear and fast. But too often, decisions get stuck in \u201cconsensus paralysis\u201d or delegated to distant managers.<\/p>\n<p>Here\u2019s how to handle it:<\/p>\n<p>Use the <strong>Three-Part Decision Rule<\/strong>:<\/p>\n<ol>\n<li><strong>Who owns the decision?<\/strong> Identify the team or role responsible for the final call.<\/li>\n<li><strong>Who must be consulted?<\/strong> List the teams affected by the outcome.<\/li>\n<li><strong>Who must be informed?<\/strong> List teams that need to know the outcome but aren\u2019t involved in the decision.<\/li>\n<\/ol>\n<p>This model prevents over-communication and ensures clarity. It\u2019s not a hierarchy\u2014it\u2019s a map of influence.<\/p>\n<p>When a team in a healthcare platform wanted to change a patient data access pattern, they used this model. Four teams were consulted, two were informed. The decision was made in 48 hours\u2014no meetings, just a documented agreement.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between scaled ceremonies and regular Agile meetings?<\/h3>\n<p>Scaled ceremonies are not just larger versions of team-level events. They\u2019re designed for coordination, not execution. A scaled refinement session isn\u2019t about estimating tasks\u2014it\u2019s about ensuring shared understanding of how work connects across teams. Regular Agile ceremonies are for team alignment; scaled ones are for program alignment.<\/p>\n<h3>How do I handle cross team communication agile when teams are in different time zones?<\/h3>\n<p>Use asynchronous collaboration tools: shared story boards, video summaries, and decision logs. Establish a \u201ccommon time window\u201d for real-time collaboration\u2014e.g., 2 hours per day where all teams are available. Rotate this window so no team is always burdened. Use recorded updates and visual dashboards for transparency.<\/p>\n<h3>Can we reduce the number of meetings in scaled Agile?<\/h3>\n<p>Yes, but only if you replace meetings with reliable signals. If a team doesn\u2019t need a weekly sync, don\u2019t hold one. But ensure that information flows through other means\u2014like shared dashboards, dependency boards, or lightweight daily updates. The goal is not fewer meetings, but better flow.<\/p>\n<h3>How do we ensure cross team communication agile during PI planning?<\/h3>\n<p>Start with a clear, shared vision. Break down epics into features only after all affected teams confirm they can deliver. Use a \u201cdependency impact matrix\u201d to flag high-risk connections. Assign a facilitator from each team to co-own the refinement process, not just the delivery.<\/p>\n<h3>What if teams disagree on story acceptance criteria?<\/h3>\n<p>Disagreements are normal. Use a \u201cshared criteria workshop\u201d to align. Bring in a neutral facilitator. Use real user scenarios. The goal isn\u2019t agreement\u2014it\u2019s consensus on what \u201cworks\u201d from the user\u2019s perspective. Document it. Reuse it.<\/p>\n<h3>How often should we review our communication protocols?<\/h3>\n<p>At a minimum, review them during every PI retrospective. Ask: What communication broke down? What helped? Use this to refine your protocols. But don\u2019t over-engineer. The best protocols are simple, visible, and lived.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every time a new feature request arrives at the enterprise level, it\u2019s not the stakeholder\u2019s need that matters most\u2014but how that need gets translated into actionable work across teams. The real bottleneck isn\u2019t complexity, but misalignment. Teams start building in isolation, only to discover too late that their work doesn\u2019t connect. That\u2019s the moment when [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1776,"menu_order":5,"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-1782","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>Communication in Scaled Agile: Protocols for Cross-Team Flow<\/title>\n<meta name=\"description\" content=\"Master cross team communication agile with proven protocols, scaled ceremonies, and feedback loops to maintain alignment and flow in large-scale Agile environments.\" \/>\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\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Communication in Scaled Agile: Protocols for Cross-Team Flow\" \/>\n<meta property=\"og:description\" content=\"Master cross team communication agile with proven protocols, scaled ceremonies, and feedback loops to maintain alignment and flow in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:21:07+00:00\" \/>\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=\"6\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\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/\",\"name\":\"Communication in Scaled Agile: Protocols for Cross-Team Flow\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:46:04+00:00\",\"dateModified\":\"2026-03-02T09:21:07+00:00\",\"description\":\"Master cross team communication agile with proven protocols, scaled ceremonies, and feedback loops to maintain alignment and flow in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/#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\":\"Cross-Team Collaboration and Flow\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Communication Protocols for Agile at Scale\"}]},{\"@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":"Communication in Scaled Agile: Protocols for Cross-Team Flow","description":"Master cross team communication agile with proven protocols, scaled ceremonies, and feedback loops to maintain alignment and flow in large-scale Agile environments.","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\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/","og_locale":"de_DE","og_type":"article","og_title":"Communication in Scaled Agile: Protocols for Cross-Team Flow","og_description":"Master cross team communication agile with proven protocols, scaled ceremonies, and feedback loops to maintain alignment and flow in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/","og_site_name":"Visual Paradigm Skills Deutsch","article_modified_time":"2026-03-02T09:21:07+00:00","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/","name":"Communication in Scaled Agile: Protocols for Cross-Team Flow","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:46:04+00:00","dateModified":"2026-03-02T09:21:07+00:00","description":"Master cross team communication agile with proven protocols, scaled ceremonies, and feedback loops to maintain alignment and flow in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/communication-protocols-for-agile-at-scale\/#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":"Cross-Team Collaboration and Flow","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/cross-team-agile-collaboration\/"},{"@type":"ListItem","position":4,"name":"Communication Protocols for Agile at Scale"}]},{"@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\/1782","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":2,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1782\/revisions"}],"predecessor-version":[{"id":2462,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1782\/revisions\/2462"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1776"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1782"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}