{"id":1764,"date":"2026-02-25T10:45:57","date_gmt":"2026-02-25T10:45:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/"},"modified":"2026-02-25T10:45:57","modified_gmt":"2026-02-25T10:45:57","slug":"large-scale-agile-challenges","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/","title":{"rendered":"Challenges Unique to Large-Scale Agile"},"content":{"rendered":"<p>There\u2019s a quiet benefit in getting story alignment right early: the compound effect of shared understanding. When teams speak the same language from day one, the friction of rework, misinterpretation, and misalignment fades\u2014not through process, but through consistency. This isn\u2019t just about documentation; it\u2019s about building a culture where clarity is a daily habit.<\/p>\n<p>As an Agile transformation coach with over two decades of experience, I\u2019ve seen how even the most well-intentioned large-scale agile initiatives collapse under the weight of unmanaged complexity. The real culprit isn\u2019t lack of effort\u2014it\u2019s the invisible walls that form between teams, fueled by fragmented communication, unclear ownership, and inconsistent story practices.<\/p>\n<p>This chapter focuses on the unique challenges that emerge when Agile scales beyond a single team. You\u2019ll learn how to navigate distributed teams, manage dependencies, and maintain shared understanding across systems and time zones. The goal isn&#8217;t to add bureaucracy, but to create flow, predictability, and trust\u2014without slowing down.<\/p>\n<h2>Why Small-Team Tactics Fail at Scale<\/h2>\n<p>What works in a single Agile team often breaks down when expanded to multiple teams. A story that\u2019s clear in isolation becomes ambiguous when shared across teams with different contexts, technical dialects, and workflows.<\/p>\n<p>One client once had three teams working on the same customer onboarding flow. Each team wrote their own version of \u201cuser can verify identity.\u201d The acceptance criteria varied. The definition of done differed. When integration testing began, the system failed\u2014not due to code, but because the stories weren\u2019t aligned on intent.<\/p>\n<p>This is a symptom of a deeper issue: <strong>the lack of a unified language<\/strong>. Without shared templates, standardized acceptance criteria, and consistent naming, stories become islands. Each team operates with its own version of truth.<\/p>\n<h3>Common Pitfalls in Multi-Team Agile Problems<\/h3>\n<ul>\n<li>Stories that are too broad or too narrow\u2014neither small enough for sprint delivery nor clear enough for shared understanding.<\/li>\n<li>Unclear ownership: a story that spans teams but no one knows who\u2019s accountable for the outcome.<\/li>\n<li>Repetitive or redundant stories across teams, leading to waste and confusion.<\/li>\n<li>Acceptance criteria that vary wildly in structure and specificity, making validation inconsistent.<\/li>\n<li>Stories defined in isolation without considering downstream dependencies.<\/li>\n<\/ul>\n<h2>Managing Dependencies Across Teams<\/h2>\n<p>Dependencies are inevitable in large-scale agile. But unchecked, they become bottlenecks that derail entire programs.<\/p>\n<p>At one financial services company, a feature involving payment processing required a data model change. The backend team delivered their story first. The frontend team, unaware, built functionality on the old schema. They both thought they were aligned. The result? A two-week delay and a costly rework.<\/p>\n<p>This is not a technical failure. It\u2019s a <strong>communication and modeling failure<\/strong>. Dependency management isn&#8217;t about tracking milestones\u2014it\u2019s about visualizing and pre-empting conflicts.<\/p>\n<h3>Proactive Dependency Mapping: A Three-Step Process<\/h3>\n<ol>\n<li><strong>Identify<\/strong> key interfaces and shared components early in the story refinement phase. Use a shared interface model or API contract.<\/li>\n<li><strong>Map<\/strong> dependencies visually using dependency diagrams or story maps. Label each dependency with risk level and owner.<\/li>\n<li><strong>Synchronize<\/strong> refinement sessions across teams. A story that depends on another should be reviewed in both teams\u2019 backlogs.<\/li>\n<\/ol>\n<h2>Establishing a Unified Language Across Teams<\/h2>\n<p>Consistency starts with language. A story written in one team\u2019s style may not be understood by another. This is where <strong>story templates<\/strong> and <strong>shared definitions<\/strong> become critical.<\/p>\n<p>I\u2019ve seen teams adopt a simple format:<\/p>\n<pre><code>As a [user role], I want [goal] so that [value]<\/code><\/pre>\n<p>But the real power comes not in the template itself\u2014but in the discipline of applying it uniformly. When every team uses the same format, the same acceptance criteria structure, and the same naming convention, stories become interoperable.<\/p>\n<h3>Shared Language: The Foundation of Enterprise Agile Issues Resolution<\/h3>\n<p>Here are the key elements of a unified story language:<\/p>\n<ul>\n<li><strong>Standardized user roles<\/strong>: Use a defined list of personas (e.g., &#8220;Customer,&#8221; &#8220;Admin,&#8221; &#8220;Third-Party API&#8221;) to reduce ambiguity.<\/li>\n<li><strong>Consistent acceptance criteria formatting<\/strong>: Use Given-When-Then or BDD-style structure to ensure testable outcomes.<\/li>\n<li><strong>Predefined story weights<\/strong>: Use a shared scale (e.g., T-shirt sizing, Fibonacci) so teams agree on effort.<\/li>\n<li><strong>Common story tags<\/strong>: Use tags like <code>[security]<\/code>, <code>[performance]<\/code>, or <code>[compliance]<\/code> to flag critical non-functional needs.<\/li>\n<\/ul>\n<p>These aren\u2019t rules imposed from above\u2014they\u2019re agreements formed by the teams themselves. When teams co-create the language, they own it.<\/p>\n<h2>Strategies for Synchronizing Distributed Teams<\/h2>\n<p>Distributed teams face time zone, cultural, and process differences. But these aren\u2019t barriers\u2014they\u2019re signals to design better collaboration.<\/p>\n<p>One team in Sydney worked with another in Berlin. Their sprint planning sessions were 12 hours apart. The result? Stories were refined independently. When they met, they discovered duplicates and misaligned priorities.<\/p>\n<p>Now, they use a <strong>shared story backlog<\/strong> and schedule a 30-minute \u201csync window\u201d every sprint. During this time, leads from each team review dependencies, align acceptance criteria, and flag risks. It\u2019s not about replacing local autonomy\u2014it\u2019s about coordination without control.<\/p>\n<h3>Best Practices for Remote Agile Coordination<\/h3>\n<ul>\n<li>Set a common time for refinement\u2014preferably during overlapping hours.<\/li>\n<li>Record key decisions and store them in a shared knowledge base.<\/li>\n<li>Assign a \u201cstory ambassador\u201d per team to act as liaison during cross-team ceremonies.<\/li>\n<li>Conduct joint retrospectives every two sprints to surface systemic issues.<\/li>\n<\/ul>\n<p>These practices don\u2019t add overhead. They reduce it. By aligning early, you prevent the hidden cost of misalignment.<\/p>\n<h2>Measuring Success: Story Health and Flow<\/h2>\n<p>Alignment isn\u2019t just about process\u2014it\u2019s about measurement. Without feedback, teams drift. Without metrics, you can\u2019t improve.<\/p>\n<p>Here are three key indicators of story health in large-scale agile environments:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Metric<\/th>\n<th>Target<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Refinement Rate<\/td>\n<td>At least 1 story per team per sprint<\/td>\n<td>Ensures backlog remains current and actionable.<\/td>\n<\/tr>\n<tr>\n<td>Backlog Volatility<\/td>\n<td>Less than 15% change per sprint<\/td>\n<td>Indicates stable priorities and reduced rework.<\/td>\n<\/tr>\n<tr>\n<td>Completion Predictability<\/td>\n<td>80%+ of committed stories completed<\/td>\n<td>Reflects realistic estimation and consistent flow.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These metrics aren\u2019t about punishing teams\u2014they\u2019re about identifying systemic issues. A spike in backlog volatility? That\u2019s a sign of unclear priorities or poor dependency planning.<\/p>\n<p>Use information radiators\u2014dashboards that update in real time\u2014to make these metrics visible across teams. When a team sees that their story completion rate is below average, they\u2019re more likely to ask, \u201cWhat\u2019s blocking us?\u201d than \u201cWhy am I being measured?\u201d<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I prevent story duplication across teams in a large-scale agile setup?<\/h3>\n<p>Start with a shared story repository and a naming convention that includes the domain or feature area. Use a centralized backlog tool with tagging and search. Conduct regular cross-team story audits every two sprints to identify duplicates.<\/p>\n<h3>What should I do when two teams disagree on a story\u2019s acceptance criteria?<\/h3>\n<p>Bring both teams together for a joint refinement session. Use a neutral facilitator. Focus on the outcome, not the preferred solution. If needed, involve a domain expert or product owner to clarify intent. The goal is shared understanding, not consensus.<\/p>\n<h3>How can I ensure alignment when teams are in different time zones?<\/h3>\n<p>Establish a 45-minute \u201csync window\u201d for refinement and planning. Use asynchronous tools (shared documents, video summaries) to capture decisions. Rotate meeting times to distribute the burden. Prioritize outcomes over meetings.<\/p>\n<h3>Can I use BDD with large-scale agile challenges?<\/h3>\n<p>Absolutely. BDD is especially useful at scale because it forces teams to write tests in plain language. Use Gherkin syntax consistently. Integrate with CI\/CD to automate acceptance testing across teams. This ensures that the same scenario is validated the same way, no matter the team.<\/p>\n<h3>What if a story depends on a team that\u2019s behind schedule?<\/h3>\n<p>Do not assume. Flag the dependency early. Use a risk matrix to assess impact. If the delay is high, consider reprioritizing or splitting the story into smaller, independent parts. Communication is key\u2014don\u2019t wait until the sprint ends to discover the problem.<\/p>\n<h3>How do I balance standardization with team autonomy?<\/h3>\n<p>Define the \u201cwhat\u201d (templates, language, core metrics) but allow teams to own the \u201chow\u201d (refinement style, tools, sprint rhythm). The goal is consistency, not uniformity. A team can be autonomous as long as their output is interoperable with others.<\/p>\n<p>Large-scale agile challenges are not obstacles to agility\u2014they are catalysts for better practice. When teams collaborate not through rigid mandates, but through shared understanding, the result is flow, trust, and sustainable delivery.<\/p>\n<p>Start small. Align early. Measure often. And remember: the most complex systems are built on the simplest principles\u2014clarity, consistency, and trust.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There\u2019s a quiet benefit in getting story alignment right early: the compound effect of shared understanding. When teams speak the same language from day one, the friction of rework, misinterpretation, and misalignment fades\u2014not through process, but through consistency. This isn\u2019t just about documentation; it\u2019s about building a culture where clarity is a daily habit. As [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1762,"menu_order":1,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","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-1764","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>Large Scale Agile Challenges: Mastering Cross-Team Alignment<\/title>\n<meta name=\"description\" content=\"Overcome enterprise agile issues and multi-team agile problems with proven practices for alignment, dependency management, and consistent storytelling at scale.\" \/>\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\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Large Scale Agile Challenges: Mastering Cross-Team Alignment\" \/>\n<meta property=\"og:description\" content=\"Overcome enterprise agile issues and multi-team agile problems with proven practices for alignment, dependency management, and consistent storytelling at scale.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/\",\"name\":\"Large Scale Agile Challenges: Mastering Cross-Team Alignment\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:45:57+00:00\",\"description\":\"Overcome enterprise agile issues and multi-team agile problems with proven practices for alignment, dependency management, and consistent storytelling at scale.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scaling Agile Storytelling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Challenges Unique to Large-Scale Agile\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Large Scale Agile Challenges: Mastering Cross-Team Alignment","description":"Overcome enterprise agile issues and multi-team agile problems with proven practices for alignment, dependency management, and consistent storytelling at scale.","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\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/","og_locale":"pt_PT","og_type":"article","og_title":"Large Scale Agile Challenges: Mastering Cross-Team Alignment","og_description":"Overcome enterprise agile issues and multi-team agile problems with proven practices for alignment, dependency management, and consistent storytelling at scale.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/","name":"Large Scale Agile Challenges: Mastering Cross-Team Alignment","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:45:57+00:00","description":"Overcome enterprise agile issues and multi-team agile problems with proven practices for alignment, dependency management, and consistent storytelling at scale.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/large-scale-agile-challenges\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Scaling Agile Storytelling","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/"},{"@type":"ListItem","position":4,"name":"Challenges Unique to Large-Scale Agile"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1764\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1762"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1764"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}