{"id":1814,"date":"2026-02-25T10:46:15","date_gmt":"2026-02-25T10:46:15","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/"},"modified":"2026-03-02T09:15:40","modified_gmt":"2026-03-02T09:15:40","slug":"enterprise-agile-case-study-global-product-line","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/","title":{"rendered":"Enterprise Case Study: Scaling Agile in a Global Product Line"},"content":{"rendered":"<p>When teams begin to work in parallel across continents, time zones, and business units, the very foundation of Agile\u2014shared understanding\u2014starts to fracture. I\u2019ve seen this happen repeatedly: teams write stories in isolation, dependencies pile up unnoticed, and progress stalls not from technical debt, but from misalignment. The real test of scaling isn\u2019t volume\u2014it\u2019s coherence. This chapter dives into a real-world enterprise case study where a global product line implemented scaled story practices, transforming from reactive firefighting to predictable, customer-centric delivery.<\/p>\n<p>What I\u2019ve learned over 20 years: scaling isn\u2019t about adding more meetings or layers of documentation. It\u2019s about creating clarity in complexity. This enterprise case study reveals how thoughtful story management global agile practices restored flow, reduced rework, and aligned cross-functional teams around measurable business value.<\/p>\n<h2>Initial Challenges: The Breaking Point<\/h2>\n<p>Our client\u2014a Fortune 500 provider of industrial automation software\u2014operated across five regions, with over 120 developers, 42 product managers, and 14 independent Agile teams. Initial attempts at scaling led to chaos. Epics were oversized, acceptance criteria were inconsistent, and stories were often disconnected from user value.<\/p>\n<p>Teams worked in silos. A story in Europe might be complete by Friday, but the dependency in India wasn\u2019t ready. No shared definition of &#171;done.&#187; No visibility into upcoming work. The result? Missed releases, rework, and growing frustration.<\/p>\n<h3>Root Causes Identified<\/h3>\n<ul>\n<li><strong>Unclear story ownership:<\/strong> Multiple teams claimed responsibility for the same feature without alignment.<\/li>\n<li><strong>Fragmented acceptance criteria:<\/strong> Each team defined &#171;complete&#187; differently, leading to integration failures.<\/li>\n<li><strong>Lack of dependency mapping:<\/strong> Dependencies were tracked in spreadsheets, not visual models.<\/li>\n<li><strong>Poor prioritization:<\/strong> Business value wasn\u2019t consistently linked to stories; backlog volatility was high.<\/li>\n<\/ul>\n<h2>Turning Point: Introducing a Unified Story Framework<\/h2>\n<p>After a PI planning session revealed that only 37% of committed stories were delivered on time, leadership committed to change. We began by establishing a <strong>shared story language<\/strong>\u2014a simple, reusable template that every team adopted.<\/p>\n<p>The template was not bureaucratic. It was practical: <em>As a [user], I want [goal] so that [benefit]<\/em>. Acceptance criteria followed a simple format: <em>Given\u2026 When\u2026 Then\u2026<\/em>, with a focus on measurable outcomes.<\/p>\n<p>This wasn\u2019t about enforcing rules\u2014it was about creating a common ground. We ran facilitation workshops, co-created standards, and introduced a lightweight certification process for backlog owners.<\/p>\n<h3>Key Pillars of Success<\/h3>\n<ol>\n<li><strong>Standardized story templates:<\/strong> Ensured consistency across teams and regions.<\/li>\n<li><strong>Shared acceptance criteria:<\/strong> Created a reusable library of common scenarios (e.g., login, data export).<\/li>\n<li><strong>Dedicated dependency mapping sessions:<\/strong> Held bi-weekly, with visual models to track cross-team blockers.<\/li>\n<li><strong>Value-driven prioritization:<\/strong> Each story was linked to an OKR or business outcome using a simple scorecard.<\/li>\n<\/ol>\n<h2>Scaling with Visual Models: The Story Map Breakthrough<\/h2>\n<p>One of the most transformative steps was introducing <strong>enterprise story mapping<\/strong>. We built a high-level map at the program level, visualizing the customer journey across all product lines.<\/p>\n<p>Each feature was broken into smaller stories, with dependency tags and ownership fields. We used a digital collaborative canvas\u2014based on Visual Paradigm\u2014that updated in real time. This allowed all teams to see how their work contributed to the larger picture.<\/p>\n<p>For example, a critical story in the German team\u2014<em>\u201cAs a factory operator, I want to reset a machine\u2019s calibration remotely so I can resume production after maintenance\u201d<\/em>\u2014was flagged as a dependency for the US team\u2019s next release. This visibility prevented a six-week delay.<\/p>\n<h3>Visual Dependency Tracking<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Story ID<\/th>\n<th>Owner Team<\/th>\n<th>Dependency<\/th>\n<th>Impact Level<\/th>\n<\/tr>\n<tr>\n<td>S-2023-012<\/td>\n<td>Germany<\/td>\n<td>US-304<\/td>\n<td>High<\/td>\n<\/tr>\n<tr>\n<td>S-2023-015<\/td>\n<td>India<\/td>\n<td>Germany-2023-012<\/td>\n<td>High<\/td>\n<\/tr>\n<tr>\n<td>S-2023-018<\/td>\n<td>US<\/td>\n<td>None<\/td>\n<td>Medium<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table evolved into a real-time dashboard displayed in all team rooms and shared via Slack. When a dependency was blocked, the entire program was alerted.<\/p>\n<h2>From Framework to Culture: Sustaining Momentum<\/h2>\n<p>Scaling Agile isn\u2019t about one-time transformation\u2014it\u2019s about continuous alignment. We introduced a <strong>story health score<\/strong> across all teams, measuring:<\/p>\n<ul>\n<li>Refinement rate (how many stories per sprint are ready)<\/li>\n<li>Backlog volatility (stories added\/removed mid-sprint)<\/li>\n<li>Dependency density (number of external dependencies per story)<\/li>\n<li>Delivery predictability (on-time completion rate)<\/li>\n<\/ul>\n<p>These metrics were reviewed monthly in a program-level retrospective. The goal wasn\u2019t blame\u2014it was improvement.<\/p>\n<p>Over 18 months, delivery predictability improved from 42% to 87%. Rework due to misalignment dropped by 63%. Teams reported feeling more in control, and business stakeholders praised the increased transparency.<\/p>\n<h2>Key Takeaways from This Enterprise Agile Case Study<\/h2>\n<p>What worked wasn\u2019t a rigid framework\u2014it was discipline, shared purpose, and simplicity. The core principles:<\/p>\n<ul>\n<li>Start with a <strong>common language<\/strong>\u2014not for compliance, but to reduce ambiguity.<\/li>\n<li>Use <strong>visual models<\/strong> to make dependencies and value flow visible.<\/li>\n<li>Measure <strong>story health<\/strong>, not just velocity.<\/li>\n<li>Trust teams, but <strong>enforce alignment through shared practices<\/strong>, not top-down mandates.<\/li>\n<\/ul>\n<p>For organizations grappling with story management global agile, this case study offers a proven blueprint. It\u2019s not about perfection\u2014it\u2019s about progress. And in large agile environments, that progress compounds.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How did you ensure consistency across teams in different time zones?<\/h3>\n<p>We scheduled biweekly syncs using rotating times. All story refinements were documented in a central repository, and video summaries were used to capture decisions. This kept all teams aligned, even when they couldn\u2019t attend live.<\/p>\n<h3>How do you handle stories that span multiple teams with different technical stacks?<\/h3>\n<p>We introduced a <strong>shared interface layer<\/strong>. All cross-team stories included a contract (e.g., API spec) that defined inputs, outputs, and error codes. This allowed teams to work independently while guaranteeing integration.<\/p>\n<h3>Can story templates really reduce misalignment?<\/h3>\n<p>Absolutely. When everyone writes stories the same way, the focus shifts from <em>how<\/em> to <em>what<\/em>. We saw a 40% reduction in rework after standardizing templates. The key is to keep them lightweight\u2014no template should take more than five minutes to apply.<\/p>\n<h3>How often should story health metrics be reviewed?<\/h3>\n<p>Monthly program retrospectives are ideal. But teams should review their own metrics weekly. The goal is transparency, not compliance. Metrics help identify trends\u2014like rising dependency density\u2014before they become crises.<\/p>\n<h3>What if a team resists adopting the shared story framework?<\/h3>\n<p>Start with a pilot. Let one team adopt the new process and demonstrate the impact. Use their results to invite others. The key is to show value, not enforce rules. Culture change happens through demonstration, not decree.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When teams begin to work in parallel across continents, time zones, and business units, the very foundation of Agile\u2014shared understanding\u2014starts to fracture. I\u2019ve seen this happen repeatedly: teams write stories in isolation, dependencies pile up unnoticed, and progress stalls not from technical debt, but from misalignment. The real test of scaling isn\u2019t volume\u2014it\u2019s coherence. This [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1813,"menu_order":0,"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-1814","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>Enterprise Agile Case Study: Global Product Line Scaling<\/title>\n<meta name=\"description\" content=\"Discover how a global enterprise scaled Agile through user story techniques, overcoming dependency chaos and alignment gaps. A real-world case study for large agile 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\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Enterprise Agile Case Study: Global Product Line Scaling\" \/>\n<meta property=\"og:description\" content=\"Discover how a global enterprise scaled Agile through user story techniques, overcoming dependency chaos and alignment gaps. A real-world case study for large agile teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:15:40+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"5 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/\",\"name\":\"Enterprise Agile Case Study: Global Product Line Scaling\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:46:15+00:00\",\"dateModified\":\"2026-03-02T09:15:40+00:00\",\"description\":\"Discover how a global enterprise scaled Agile through user story techniques, overcoming dependency chaos and alignment gaps. A real-world case study for large agile teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Lessons and Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Enterprise Case Study: Scaling Agile in a Global Product Line\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Enterprise Agile Case Study: Global Product Line Scaling","description":"Discover how a global enterprise scaled Agile through user story techniques, overcoming dependency chaos and alignment gaps. A real-world case study for large agile 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\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/","og_locale":"ru_RU","og_type":"article","og_title":"Enterprise Agile Case Study: Global Product Line Scaling","og_description":"Discover how a global enterprise scaled Agile through user story techniques, overcoming dependency chaos and alignment gaps. A real-world case study for large agile teams.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","article_modified_time":"2026-03-02T09:15:40+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"5 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/","name":"Enterprise Agile Case Study: Global Product Line Scaling","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:46:15+00:00","dateModified":"2026-03-02T09:15:40+00:00","description":"Discover how a global enterprise scaled Agile through user story techniques, overcoming dependency chaos and alignment gaps. A real-world case study for large agile teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/enterprise-agile-case-study-global-product-line\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Real-World Lessons and Case Studies","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/"},{"@type":"ListItem","position":4,"name":"Enterprise Case Study: Scaling Agile in a Global Product Line"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1814\/revisions"}],"predecessor-version":[{"id":2436,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1814\/revisions\/2436"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1813"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=1814"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=1814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}