{"id":1765,"date":"2026-02-25T10:45:58","date_gmt":"2026-02-25T10:45:58","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/"},"modified":"2026-02-25T10:45:58","modified_gmt":"2026-02-25T10:45:58","slug":"enterprise-backlog-management","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/","title":{"rendered":"From Team Backlogs to Enterprise Backlogs"},"content":{"rendered":"<p>When teams operate in isolation, even well-crafted stories can drift apart from strategic intent. That disconnect becomes a silent obstacle to delivery\u2014especially in large organizations where alignment is not assumed, but earned. I\u2019ve seen teams build value-rich features only to discover they didn\u2019t support the next release\u2019s KPIs because no one had connected the dots from story to strategy.<\/p>\n<p>Enterprise backlog management isn\u2019t about centralizing control. It\u2019s about creating a shared path from idea to impact\u2014where each team\u2019s work contributes meaningfully to a larger vision. The right approach transforms fragmented backlogs into a coordinated flow of value.<\/p>\n<p>By the end of this chapter, you\u2019ll know how to structure and manage enterprise-level backlogs with clarity and purpose. You\u2019ll understand how to align cross-team efforts, integrate portfolio-level strategy, and ensure that every story\u2014from sprint to roadmap\u2014serves both business and technical goals.<\/p>\n<h2>Why Backlog Alignment Matters at Scale<\/h2>\n<p>At the team level, backlog management is straightforward: write, prioritize, refine, deliver. But as systems grow, complexity multiplies\u2014especially when multiple teams own parts of a single feature or customer journey.<\/p>\n<p>Without alignment, teams may deliver independently, only to face integration failures or duplicated effort. Worse, they might solve the wrong problem altogether.<\/p>\n<p>Enter cross-team backlog alignment. This isn\u2019t a process\u2014it\u2019s a mindset. It means every story, no matter where it lives, is traceable to a shared objective. It ensures that when Team A finishes a story about payment processing, it supports not just their sprint goal but also the broader initiative to improve checkout conversion.<\/p>\n<p>And that\u2019s where enterprise backlog management becomes essential. It\u2019s not about adding more layers of bureaucracy. It\u2019s about creating clarity through structure and shared understanding.<\/p>\n<h2>Building the Enterprise Backlog Hierarchy<\/h2>\n<p>Enterprise backlogs aren\u2019t just \u201cbig backlogs.\u201d They are structured hierarchies that connect strategy to execution. Think of them as living maps\u2014dynamic, evolving, and aligned with business outcomes.<\/p>\n<p>Here\u2019s how to build one:<\/p>\n<ol>\n<li><strong>Start with strategy:<\/strong> Define objectives, OKRs, or strategic themes. These become the foundation of all work.<\/li>\n<li><strong>Break into portfolio-level epics:<\/strong> Translate high-level goals into large-scale initiatives that span multiple teams.<\/li>\n<li><strong>Create program-level features:<\/strong> These are deliverables that span one or more Agile Teams and contribute to a PI (Program Increment).<\/li>\n<li><strong>Break features into team-level stories:<\/strong> Each story must deliver measurable value, be testable, and align with a feature.<\/li>\n<\/ol>\n<p>Every story should answer: What part of a feature does it enable? How does it support a capability? Where does it fit in the bigger picture?<\/p>\n<p>Use tools like story mapping or visual dependency boards to keep the hierarchy visible. I\u2019ve used this approach in a financial services firm where a single \u201ccustomer onboarding\u201d feature spanned three teams and required over 30 stories. Without visual alignment, we\u2019d have missed two critical integration points.<\/p>\n<h3>Mapping Strategy to Execution: A Real Example<\/h3>\n<p>At a global logistics company, the business goal was to reduce shipment delays by 20% in 12 months. We started by defining a portfolio epic: \u201cImprove Real-Time Tracking and Exception Handling.\u201d<\/p>\n<p>That became a program feature: \u201cEnable Exception Alerts via Mobile and Web.\u201d<\/p>\n<p>Three teams then broke it down:<\/p>\n<ul>\n<li>Team A: \u201cAs a customer, I want to receive an SMS alert when my shipment is delayed so I can respond quickly.\u201d<\/li>\n<li>Team B: \u201cAs a dispatcher, I want to see all delayed shipments on a real-time dashboard so I can re-route them.\u201d<\/li>\n<li>Team C: \u201cAs a system, I want to detect delays based on GPS data and weather alerts using a rule engine so I can trigger notifications.\u201d<\/li>\n<\/ul>\n<p>Each story was traceable to the original objective. When PI planning came around, we knew exactly which stories contributed to the outcome\u2014and which needed refinement.<\/p>\n<h2>Integrating Portfolio Backlog Agile<\/h2>\n<p>Portfolio backlog agile isn\u2019t just a concept. It\u2019s a practice. It means the portfolio backlog isn\u2019t static. It evolves through continuous refinement, driven by feedback, market changes, and delivery performance.<\/p>\n<p>But how do you maintain agility here? By keeping it lightweight.<\/p>\n<p>Agile portfolios should not be bloated with unnecessary documentation. Instead, use concise epics with a clear outcome, value, and acceptance criteria. Every entry should answer:<\/p>\n<ul>\n<li>What business problem does it solve?<\/li>\n<li>How will we know it\u2019s working?<\/li>\n<li>Which teams will own it?<\/li>\n<li>What dependencies exist?<\/li>\n<\/ul>\n<p>Keep the portfolio backlog focused on outcomes, not features. A team can\u2019t deliver value if the goal is vague. \u201cImprove customer experience\u201d is not a story. \u201cReduce average customer wait time by 30%\u201d is.<\/p>\n<h3>Portfolio Backlog Governance Without Bureaucracy<\/h3>\n<p>I\u2019ve noticed a pattern: organizations that over-govern their portfolio backlogs end up stifling innovation. The fix? Light, outcome-based oversight.<\/p>\n<p>Here\u2019s how:<\/p>\n<ul>\n<li>Hold quarterly portfolio reviews to reassess priorities and remove low-impact epics.<\/li>\n<li>Use a simple scoring model based on value, risk, and effort\u2014no need for complex tools.<\/li>\n<li>Empower product managers and architects to co-own the backlog, not managers.<\/li>\n<li>Limit backlog refinement to one dedicated session per sprint\u2014no more.<\/li>\n<\/ul>\n<p>Keep the focus on what matters: delivering value, not filling forms.<\/p>\n<h2>Managing Dependencies Across Teams<\/h2>\n<p>Dependencies are inevitable. But they don\u2019t have to slow you down. The key is visibility and proactive management.<\/p>\n<p>When a story in Team A relies on a story in Team B, both teams must know it. And not just at sprint planning\u2014throughout execution.<\/p>\n<p>Use dependency mapping techniques:<\/p>\n<ul>\n<li>Color-code stories in story mapping by team or domain.<\/li>\n<li>Use arrows or labels to show who depends on whom.<\/li>\n<li>Update dependency status in real time during stand-ups or syncs.<\/li>\n<\/ul>\n<p>One team I worked with used a shared digital story map with color-coded swimlanes. When a dependency risk emerged, the entire program could see it\u2014and act.<\/p>\n<h3>Dependency Management Checklist<\/h3>\n<ul>\n<li><strong>Identify dependencies early:<\/strong> During story refinement, flag any cross-team or external dependencies.<\/li>\n<li><strong>Document in stories:<\/strong> Include dependency notes in acceptance criteria or metadata.<\/li>\n<li><strong>Track in real time:<\/strong> Use dashboards to visualize dependency status.<\/li>\n<li><strong>Escalate proactively:<\/strong> If a delay is likely, alert stakeholders before sprint end.<\/li>\n<\/ul>\n<h2>Scaling Without Losing Context<\/h2>\n<p>Agile thrives on context. At scale, that context risks getting lost in translation. Teams may start writing stories like \u201cAs a user, I want to log in\u201d without understanding who the user is\u2014or why it matters.<\/p>\n<p>Reintroduce context through:<\/p>\n<ul>\n<li><strong>User personas:<\/strong> Define real user types across business lines.<\/li>\n<li><strong>Value streams:<\/strong> Map how stories flow through systems and touch customers.<\/li>\n<li><strong>Shared language:<\/strong> Use consistent naming: \u201ccustomer,\u201d \u201corder,\u201d \u201cshipment\u201d \u2014 not \u201centity X\u201d or \u201citem Y.\u201d<\/li>\n<\/ul>\n<p>These aren\u2019t just templates. They\u2019re tools for shared understanding.<\/p>\n<h3>Story Example: Context Matters<\/h3>\n<p>Consider two versions of a story:<\/p>\n<pre><code>As a user, I want to log in so I can access my account.<\/code><\/pre>\n<p>Now, this:<\/p>\n<pre><code>As a returning customer in the UK, I want to log in via my mobile app so I can track my order and receive delivery notifications, because I\u2019m used to managing my shipments on the go.<\/code><\/pre>\n<p>The second version isn\u2019t just more detailed\u2014it\u2019s tied to a specific user journey, location, and business need. That\u2019s the kind of story that scales well.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between a portfolio backlog and an enterprise backlog?<\/h3>\n<p>The portfolio backlog includes strategic epics and investment areas. The enterprise backlog is the full hierarchy\u2014portfolio epics, program features, team stories\u2014linked by shared goals. Think of the portfolio backlog as the top layer, and enterprise backlog as the entire structure.<\/p>\n<h3>How do we ensure cross-team backlog alignment when teams are in different time zones?<\/h3>\n<p>Use asynchronous refinement. Record short videos or audio notes during story sessions. Share story maps and dependency boards in a shared space. Sync only during key events like PI planning or sprint reviews.<\/p>\n<h3>Can we use agile estimation at scale without a PI planning session?<\/h3>\n<p>Not effectively. PI planning is essential for synchronizing teams. But estimation can be lightweight\u2014use T-shirt sizing or flow metrics instead of story points if it reduces friction.<\/p>\n<h3>What if our teams don\u2019t agree on story ownership?<\/h3>\n<p>Use a shared accountability model. Define clear roles: who owns the story, who delivers it, who validates it. Document this in a story ownership matrix. Avoid vague terms like \u201cshared\u201d or \u201ccollaborative\u201d without clarity.<\/p>\n<h3>How do we prevent backlog bloat in an enterprise environment?<\/h3>\n<p>Apply the \u201cMinimum Viable Story\u201d rule: every story must deliver value and be testable. Review stories every 2\u20133 sprints. Remove or refactor any that no longer serve a purpose. Use a \u201cstory health\u201d metric\u2014refinement rate, completion predictability, dependency load.<\/p>\n<h3>Is portfolio backlog agile feasible in regulated industries?<\/h3>\n<p>Yes. The key is lightweight documentation. Focus on outcomes, not processes. In regulated environments, use traceability matrices to link stories to compliance requirements\u2014but avoid over-documenting. The goal is agility, not compliance for compliance\u2019s sake.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When teams operate in isolation, even well-crafted stor [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1762,"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-1765","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 Backlog Management at Scale<\/title>\n<meta name=\"description\" content=\"Master enterprise backlog management with proven techniques for cross-team backlog alignment and portfolio backlog agile integration. Scale user stories with confidence.\" \/>\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\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Enterprise Backlog Management at Scale\" \/>\n<meta property=\"og:description\" content=\"Master enterprise backlog management with proven techniques for cross-team backlog alignment and portfolio backlog agile integration. Scale user stories with confidence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/\",\"name\":\"Enterprise Backlog Management at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:45:58+00:00\",\"description\":\"Master enterprise backlog management with proven techniques for cross-team backlog alignment and portfolio backlog agile integration. Scale user stories with confidence.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scaling Agile Storytelling\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"From Team Backlogs to Enterprise Backlogs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Enterprise Backlog Management at Scale","description":"Master enterprise backlog management with proven techniques for cross-team backlog alignment and portfolio backlog agile integration. Scale user stories with confidence.","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\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/","og_locale":"zh_CN","og_type":"article","og_title":"Enterprise Backlog Management at Scale","og_description":"Master enterprise backlog management with proven techniques for cross-team backlog alignment and portfolio backlog agile integration. Scale user stories with confidence.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"7 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/","name":"Enterprise Backlog Management at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:45:58+00:00","description":"Master enterprise backlog management with proven techniques for cross-team backlog alignment and portfolio backlog agile integration. Scale user stories with confidence.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/enterprise-backlog-management\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Scaling Agile Storytelling","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/user-story-techniques-large-scale-agile\/scaling-agile-storytelling\/"},{"@type":"ListItem","position":4,"name":"From Team Backlogs to Enterprise Backlogs"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1765","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1765\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1762"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=1765"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=1765"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}