{"id":1771,"date":"2026-02-25T10:46:00","date_gmt":"2026-02-25T10:46:00","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/"},"modified":"2026-02-25T10:46:00","modified_gmt":"2026-02-25T10:46:00","slug":"cross-team-user-stories-aligning-agile-at-scale","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/","title":{"rendered":"Writing Stories That Work Across Teams"},"content":{"rendered":"<p>When teams share ownership of a feature, the user story must reflect that reality\u2014not a false sense of individual accountability. A well-formed cross team user story respects shared ownership and enables multi team agile collaboration without fragmenting the user experience.<\/p>\n<p>My rule is simple: if a story cannot be meaningfully completed by one team alone, it must be written so that all teams involved understand their role in delivering a unified outcome. This isn\u2019t about bureaucracy\u2014it\u2019s about clarity, shared understanding, and flow.<\/p>\n<p>Over two decades in enterprise Agile, I\u2019ve seen teams fail not from lack of effort, but from misaligned story ownership. The fix isn\u2019t more meetings\u2014it\u2019s better writing.<\/p>\n<p>This chapter equips you with practical, battle-tested methods to write stories that work across teams. You\u2019ll learn how to define shared story ownership, manage dependencies without control, and design stories that scale with the product\u2014without losing agility.<\/p>\n<h2>What Makes a Story Truly Cross-Team?<\/h2>\n<p>Not all stories that span teams are created equal. A true cross team user story serves a single user need while requiring coordinated work across multiple teams.<\/p>\n<p>Here\u2019s how to recognize one:<\/p>\n<ul>\n<li>It cannot be delivered by any one team without input from others.<\/li>\n<li>It involves shared acceptance criteria that only make sense when interpreted collectively.<\/li>\n<li>It links to a single value stream, not multiple independent outcomes.<\/li>\n<li>It requires synchronized delivery or integration\u2014often in the same release increment.<\/li>\n<\/ul>\n<p>For example: \u201cAs a customer, I want to view my billing history and download a PDF, so I can file taxes.\u201d This spans finance, document services, and UI teams. No one team owns the full experience.<\/p>\n<h3>Key Principles for Cross-Team Story Writing<\/h3>\n<p>These principles are rooted in real-world practice, not theory.<\/p>\n<ol>\n<li><strong>Start from the user, not the system.<\/strong> Always anchor the story to a user need. This ensures alignment across teams and prevents technical silos.<\/li>\n<li><strong>Declare ownership upfront.<\/strong> Explicitly state which teams are responsible for which parts of the delivery. Use a shared ownership matrix if needed.<\/li>\n<li><strong>Define shared acceptance criteria.<\/strong> These must be agreed upon and testable across teams. Avoid \u201cteam-specific\u201d criteria that fragment the outcome.<\/li>\n<li><strong>Use a common language.<\/strong> Avoid jargon unique to one team. If a feature involves \u201cinvoice reconciliation,\u201d define it in business terms, not just technical ones.<\/li>\n<\/ol>\n<p>These aren\u2019t optional. They\u2019re the foundation of multi team agile collaboration. Without them, stories become dependencies wrapped in ambiguity.<\/p>\n<h2>How to Structure a Cross-Team Story<\/h2>\n<p>Structure matters. A well-structured story guides teams through collaboration, not confusion.<\/p>\n<p>Here\u2019s a proven format:<\/p>\n<pre><code>As a [user type],\nI want [goal],\nSo that [benefit].\n \n[Shared story ownership]\n- Team A: Implement frontend UI and user interaction\n- Team B: Provide API endpoint with data filter and export logic\n- Team C: Secure audit trail for compliance\n\n[Shared acceptance criteria]\n- User can filter by month and year\n- User can export 12 months of history in PDF\n- Exported file includes customer ID, date range, and total amount\n- All data is secured per PCI-DSS standards\n- Integration test passes with real user scenario<\/code><\/pre>\n<p>This format makes roles, responsibilities, and outcomes explicit. It prevents \u201cI thought you\u2019d do it\u201d moments.<\/p>\n<h3>When to Split\u2014And When to Keep Together<\/h3>\n<p>Not every story that spans teams needs to be split into three. But when it does, ask: \u201cCan this story be validated only when all teams deliver?\u201d If yes, keep it as one story with shared ownership.<\/p>\n<p>Use the following decision tree:<\/p>\n<ul>\n<li>If the outcome requires integration and can\u2019t be tested independently\u2014keep as one story.<\/li>\n<li>If teams can deliver parts in parallel but the value is realized only when combined\u2014still one story, but with sub-tasks.<\/li>\n<li>If the user experience is independent per team\u2014split into separate stories.<\/li>\n<\/ul>\n<p>Splitting too early fragments value. Holding too long creates bottlenecks. The sweet spot is when teams can collaborate without blocking each other.<\/p>\n<h2>Shared Story Ownership: Practical Guidelines<\/h2>\n<p>Shared story ownership is not a buzzword. It\u2019s a practice that defines how teams cooperate.<\/p>\n<p>It means:<\/p>\n<ul>\n<li>Everyone involved has a stake in success.<\/li>\n<li>Decisions about scope, timing, and acceptance are made collaboratively.<\/li>\n<li>No team can unilaterally block delivery.<\/li>\n<li>Feedback loops are shared and transparent.<\/li>\n<\/ul>\n<p>But ownership doesn\u2019t mean equal contribution. It means shared accountability. One team may do the bulk of the work, but all must agree to the acceptance criteria and integration test.<\/p>\n<h3>Tools That Support Shared Ownership<\/h3>\n<p>Use these to make shared story ownership visible and actionable:<\/p>\n<ul>\n<li><strong>Ownership matrix.<\/strong> A table that maps team names to story components (UI, backend, integration, testing).<\/li>\n<li><strong>Shared definition of done (DoD).<\/strong> One DoD for the story, even if teams have their own internal DoD.<\/li>\n<li><strong>Integrated backlog refinement.<\/strong> Hold joint workshops where all teams attend and co-create acceptance criteria.<\/li>\n<li><strong>Information radiators.<\/strong> Visual displays showing story progress, dependency status, and team commitments.<\/li>\n<\/ul>\n<p>These tools don\u2019t replace trust\u2014they make it visible. They support multi team agile collaboration by reducing ambiguity.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even with good intentions, teams fall into traps. Here are the most common:<\/p>\n<h3>1. The \u201cI\u2019ll Wait for You\u201d Story<\/h3>\n<p>One team starts work, but can\u2019t finish because another team hasn\u2019t delivered. The story becomes blocked.<\/p>\n<p><strong>Solution:<\/strong> Define dependencies explicitly. Use a dependency matrix to flag risks early. If Team B is delaying Team A, revisit the story\u2019s acceptance criteria\u2014do they really need to wait?<\/p>\n<h3>2. Hidden Dependencies in Acceptance Criteria<\/h3>\n<p>Acceptance criteria assume a service exists. But the service isn\u2019t ready. The integration fails.<\/p>\n<p><strong>Solution:<\/strong> Use contract testing. Define API contracts in advance. Use stubs or mocks during development. Never assume.<\/p>\n<h3>3. Ownership Ambiguity<\/h3>\n<p>Everyone says they\u2019ll do it. No one does.<\/p>\n<p><strong>Solution:<\/strong> Assign a primary owner per component. The primary owner coordinates, but all teams are accountable. Use the \u201cone team, one owner\u201d rule per component.<\/p>\n<h2>Case Study: Insurance Platform Integration<\/h2>\n<p>A large insurance provider needed to deliver a \u201ccustomer claims dashboard\u201d that spanned claims, billing, and customer service teams.<\/p>\n<p>Initially, they created three separate stories. But users couldn\u2019t see the full picture. Delays piled up, and teams blamed each other.<\/p>\n<p>They restructured into one story with shared ownership:<\/p>\n<pre><code>As a claims manager,\nI want to view a real-time summary of pending claims, payments, and customer interactions,\nSo that I can assess risk and prioritize follow-ups.\n\n[Shared story ownership]\n- Claims Team: Fetch claim status and assign priority\n- Billing Team: Retrieve payment history and due dates\n- Customer Service Team: Pull recent interaction logs\n\n[Shared acceptance criteria]\n- Dashboard loads in under 3 seconds\n- All data is synchronized in real time\n- User can filter by claim type, status, and date\n- All views are role-based and secure\n- Integration test passes with live data<\/code><\/pre>\n<p>Result: Delivery time dropped by 40%, and team alignment improved. The story became a shared KPI, not a handoff.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do we handle disagreements on acceptance criteria across teams?<\/h3>\n<p>Hold a joint refinement session with all teams. Use the \u201cyes, and\u201d mindset\u2014build on each other\u2019s input. If consensus isn\u2019t possible, escalate to a shared decision-maker (like a product manager or architect). But never skip alignment.<\/p>\n<h3>Can one team own a cross-team story?<\/h3>\n<p>Yes\u2014but only if they\u2019re responsible for coordination and integration. The owner must be accountable for the end-to-end outcome. No team can \u201cown\u201d a story and then pass it off like a baton.<\/p>\n<h3>What if teams are in different time zones?<\/h3>\n<p>Use asynchronous collaboration tools. Record refinement sessions. Share meeting notes and decisions. Use shared documents with real-time editing. The key is transparency, not synchrony.<\/p>\n<h3>How do we track progress on a cross-team story?<\/h3>\n<p>Use a shared Kanban board. Each team updates their column. Use a story owner to monitor integration points. Add a \u201cdependency status\u201d column to flag risks early.<\/p>\n<h3>Do cross-team stories need PI planning?<\/h3>\n<p>Yes\u2014but only if they impact a Program Increment. For stories that don\u2019t affect the PI, use regular backlog refinement. But if the story spans multiple teams and impacts delivery, include it in PI planning.<\/p>\n<h3>How do we ensure compliance in shared stories?<\/h3>\n<p>Define compliance requirements in the shared acceptance criteria. Assign a compliance owner to verify. Use automated checks (e.g., audit log validation) and integrate them into the CI\/CD pipeline.<\/p>\n<p>When done right, cross team user stories aren\u2019t a burden. They\u2019re a force multiplier. They turn fragmented efforts into unified value delivery.<\/p>\n<p>Focus on shared story ownership. Prioritize multi team agile collaboration. And always, always write with the user in mind.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When teams share ownership of a feature, the user story must reflect that reality\u2014not a false sense of individual accountability. A well-formed cross team user story respects shared ownership and enables multi team agile collaboration without fragmenting the user experience. My rule is simple: if a story cannot be meaningfully completed by one team alone, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1768,"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-1771","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 User Stories: Aligning Agile at Scale<\/title>\n<meta name=\"description\" content=\"Learn how to write cross team user stories with shared story ownership and multi team agile collaboration. Master scalable, aligned, and actionable story practices for enterprise Agile delivery.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cross Team User Stories: Aligning Agile at Scale\" \/>\n<meta property=\"og:description\" content=\"Learn how to write cross team user stories with shared story ownership and multi team agile collaboration. Master scalable, aligned, and actionable story practices for enterprise Agile delivery.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/\",\"name\":\"Cross Team User Stories: Aligning Agile at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:46:00+00:00\",\"description\":\"Learn how to write cross team user stories with shared story ownership and multi team agile collaboration. Master scalable, aligned, and actionable story practices for enterprise Agile delivery.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structuring Large-Scale Backlogs\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Writing Stories That Work Across Teams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Cross Team User Stories: Aligning Agile at Scale","description":"Learn how to write cross team user stories with shared story ownership and multi team agile collaboration. Master scalable, aligned, and actionable story practices for enterprise Agile delivery.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/","og_locale":"id_ID","og_type":"article","og_title":"Cross Team User Stories: Aligning Agile at Scale","og_description":"Learn how to write cross team user stories with shared story ownership and multi team agile collaboration. Master scalable, aligned, and actionable story practices for enterprise Agile delivery.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"7 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/","name":"Cross Team User Stories: Aligning Agile at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:46:00+00:00","description":"Learn how to write cross team user stories with shared story ownership and multi team agile collaboration. Master scalable, aligned, and actionable story practices for enterprise Agile delivery.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/cross-team-user-stories-aligning-agile-at-scale\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Structuring Large-Scale Backlogs","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/"},{"@type":"ListItem","position":4,"name":"Writing Stories That Work Across Teams"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1771","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1771\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1768"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1771"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}