{"id":1803,"date":"2026-02-25T10:46:11","date_gmt":"2026-02-25T10:46:11","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/"},"modified":"2026-02-25T10:46:11","modified_gmt":"2026-02-25T10:46:11","slug":"agile-prioritization-at-scale","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/","title":{"rendered":"Backlog Prioritization in Multi-Team Environments"},"content":{"rendered":"<p>When multiple teams depend on a shared backlog, arbitrary ordering leads to wasted effort, misaligned delivery, and delayed value. Agile prioritization at scale isn\u2019t about ranking stories\u2014it\u2019s about ensuring the right work flows to the right teams at the right time.<\/p>\n<p>Too many organizations default to relative story point size or arbitrary sprint goals. That breaks down when dependencies span teams, domains, or even business units.<\/p>\n<p>I\u2019ve worked with enterprise teams where the backlog was a graveyard of unvaluable features because priority was determined by seniority, not impact. The solution? Use economic frameworks grounded in real-world value, not politics.<\/p>\n<p>Here, you\u2019ll learn how to apply WSJF prioritization and cost of delay agile to ensure that the highest-value work flows first\u2014across teams, domains, and timelines.<\/p>\n<h2>Why Traditional Prioritization Fails at Scale<\/h2>\n<p>In small teams, a simple MoSCoW or MoSCoW-style ranking may suffice. But in large programs, what\u2019s \u201curgent\u201d for one team may be \u201clow value\u201d for the customer. Prioritization must reflect real business impact.<\/p>\n<p>When teams prioritize in isolation, they often end up building features that satisfy internal milestones but don\u2019t deliver measurable user value. This creates what I call \u201calignment theater\u201d\u2014teams working hard but in different directions.<\/p>\n<p>The root problem: many backlogs are managed as lists, not dynamic flow systems. Without economic signals, teams can\u2019t distinguish between \u201cimportant\u201d and \u201chigh-impact\u201d work.<\/p>\n<h3>Common Pitfalls in Multi-Team Prioritization<\/h3>\n<ul>\n<li>Ranking by team capacity instead of business value<\/li>\n<li>Allowing stakeholders to assign priority based on influence, not outcome<\/li>\n<li>Using arbitrary labels like \u201cHigh,\u201d \u201cMedium,\u201d \u201cLow\u201d without measurable criteria<\/li>\n<li>Letting dependencies drive priority instead of value<\/li>\n<li>Ignoring the cumulative cost of delay across multiple teams<\/li>\n<\/ul>\n<h2>Introducing WSJF: The Economic Engine of Agile Prioritization<\/h2>\n<p>WSJF\u2014Weighted Shortest Job First\u2014is the gold standard for prioritizing work at scale. It\u2019s not a framework. It\u2019s a decision-making model rooted in economic theory and proven in complex programs.<\/p>\n<p>WSJF calculates the cost of delay per unit of job size. The higher the WSJF score, the higher the priority.<\/p>\n<p>Formula: <strong>WSJF = Cost of Delay \/ Job Size<\/strong><\/p>\n<p>The cost of delay isn\u2019t just about time. It includes revenue loss, compliance risk, competitive disadvantage, and customer retention. Job size refers to the relative effort to deliver the feature.<\/p>\n<h3>Breaking Down the Cost of Delay<\/h3>\n<p>Cost of delay agile isn\u2019t a guess. It\u2019s derived from four key components:<\/p>\n<ol>\n<li><strong>Time criticality<\/strong> \u2013 How quickly must this deliver to avoid impact?<\/li>\n<li><strong>Customer value<\/strong> \u2013 What benefit does the user receive?<\/li>\n<li><strong>Business value<\/strong> \u2013 How much revenue or cost avoidance does it enable?<\/li>\n<li><strong>Risk reduction<\/strong> \u2013 Does delaying work increase exposure to risk or regulatory penalty?<\/li>\n<\/ol>\n<p>When I guided a financial services program through PI planning, we used cost of delay agile to re-prioritize 300+ features. The top 15% of stories by WSJF delivered 70% of the projected business value. The rest were deferred until a future PI.<\/p>\n<h2>Step-by-Step WSJF Prioritization<\/h2>\n<p>Here\u2019s how to apply WSJF in your enterprise backlog:<\/p>\n<ol>\n<li><strong>Define each story\u2019s cost of delay<\/strong> using one of the four components above. Assign a numeric value (e.g., 1\u201310).<\/li>\n<li><strong>Estimate job size<\/strong> using story points or relative effort units (e.g., 2, 5, 8).<\/li>\n<li><strong>Calculate WSJF score<\/strong> by dividing cost of delay by job size.<\/li>\n<li><strong>Sort by WSJF score<\/strong> in descending order.<\/li>\n<li><strong>Assign to teams<\/strong> based on capacity and dependency alignment.<\/li>\n<\/ol>\n<p>Pro tip: Don\u2019t over-analyze. A 1\u20135 scale for cost of delay is sufficient. Accuracy matters less than consistency.<\/p>\n<h3>WSJF Prioritization Example<\/h3>\n<table>\n<tbody>\n<tr>\n<th>Story<\/th>\n<th>Cost of Delay (1\u201310)<\/th>\n<th>Job Size (SP)<\/th>\n<th>WSJF Score<\/th>\n<\/tr>\n<tr>\n<td>Reset failed login lockout<\/td>\n<td>9<\/td>\n<td>3<\/td>\n<td>3.0<\/td>\n<\/tr>\n<tr>\n<td>Dashboard redesign<\/td>\n<td>7<\/td>\n<td>8<\/td>\n<td>0.875<\/td>\n<\/tr>\n<tr>\n<td>Export data to PDF<\/td>\n<td>5<\/td>\n<td>2<\/td>\n<td>2.5<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Even though the dashboard redesign has higher business value, the login fix has a higher WSJF score because it delivers value faster with less cost.<\/p>\n<h2>When to Use WSJF vs. Cost of Delay Agile<\/h2>\n<p>WSJF and cost of delay agile are deeply connected. WSJF is the calculation. Cost of delay agile is the philosophy behind it.<\/p>\n<p>Use cost of delay agile when:<\/p>\n<ul>\n<li>You\u2019re aligning multiple teams on a shared value stream<\/li>\n<li>Dependencies span business and technical domains<\/li>\n<li>You need to justify delayed work to leadership<\/li>\n<li>You\u2019re running PI planning and need to sequence features<\/li>\n<\/ul>\n<p>Use WSJF when:<\/p>\n<ul>\n<li>Ranking individual stories in the backlog<\/li>\n<li>Deciding which items to pull into the next sprint<\/li>\n<li>Comparing work across different teams with different effort estimates<\/li>\n<\/ul>\n<p>They\u2019re not alternatives. They\u2019re complementary.<\/p>\n<h2>Practical Application: Scaling Across Teams<\/h2>\n<p>At scale, you can\u2019t apply WSJF to every story. Instead, apply it at the feature or capability level, then break down dependencies.<\/p>\n<p>Example: A feature like \u201cEnable Multi-Factor Authentication\u201d may include:<\/p>\n<ul>\n<li>Backend: User authentication service (cost of delay: 9)<\/li>\n<li>Frontend: UI implementation (cost of delay: 6)<\/li>\n<li>Compliance: Audit log integration (cost of delay: 8)<\/li>\n<\/ul>\n<p>Each piece gets a cost of delay based on shared risk. Then, apply WSJF per team to sequence delivery.<\/p>\n<p>Don\u2019t let a single team\u2019s capacity override the economic signal. If a low-impact story blocks high-impact work, restructure the flow.<\/p>\n<h2>Common Misunderstandings About WSJF<\/h2>\n<ul>\n<li><strong>\u201cIt\u2019s too complex for our teams.\u201d<\/strong> It\u2019s actually simpler than many alternatives. Start with one team, use cost of delay on a 1\u20135 scale, and track outcomes.<\/li>\n<li><strong>\u201cWe can\u2019t measure cost of delay.\u201d<\/strong> You don\u2019t need perfect data. Use stakeholder input, market research, or past PI results to estimate.<\/li>\n<li><strong>\u201cIt prioritizes small items only.\u201d<\/strong> No\u2014it favors high impact per unit effort. A large story can win if its cost of delay is high enough.<\/li>\n<li><strong>\u201cIt ignores dependencies.\u201d<\/strong> It doesn\u2019t ignore them\u2014it makes them visible. High-impact stories with blocking dependencies get flagged for early resolution.<\/li>\n<\/ul>\n<h2>Integrating WSJF into Your Agile Artifacts<\/h2>\n<p>Make WSJF visible across your workflow:<\/p>\n<ul>\n<li>Display WSJF scores in the product backlog<\/li>\n<li>Show risk of delay in sprint planning: \u201cIf we delay this, what\u2019s the business impact?\u201d<\/li>\n<li>Use WSJF scores to inform PI planning and release sequencing<\/li>\n<li>Include WSJF in backlog refinement sessions to guide decisions<\/li>\n<\/ul>\n<p>Don\u2019t make it a spreadsheet-only tool. Embed it in your planning ceremonies.<\/p>\n<h2>Measuring Success: What to Watch For<\/h2>\n<p>Agile prioritization at scale isn\u2019t complete without feedback. Track these metrics:<\/p>\n<ul>\n<li><strong>Value delivered per sprint<\/strong> \u2013 Compare against WSJF ranking<\/li>\n<li><strong>Backlog volatility<\/strong> \u2013 Frequent changes signal poor prioritization<\/li>\n<li><strong>Story completion rate by WSJF tier<\/strong> \u2013 Are high-WSJF stories delivered?<\/li>\n<li><strong>Dependency resolution time<\/strong> \u2013 High-wait time for dependencies indicates misalignment<\/li>\n<\/ul>\n<p>If high-WSJF stories are left behind, re-evaluate your cost of delay estimation model.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How often should we re-calculate WSJF scores?<\/h3>\n<p>Re-calculate at each PI planning or major backlog refinement cycle. Adjust if business context changes\u2014like new regulations, market shifts, or customer feedback.<\/p>\n<h3>Can WSJF be used for technical debt?<\/h3>\n<p>Yes, but assign a cost of delay based on risk: potential outages, security vulnerabilities, or compliance exposure. Technical debt with high cost of delay should be prioritized.<\/p>\n<h3>What if two stories have the same WSJF score?<\/h3>\n<p>Use dependency alignment. If one blocks the other, prioritize the blocker. If both are independent, use team capacity or delivery risk.<\/p>\n<h3>How do I handle stories with no clear cost of delay?<\/h3>\n<p>Use stakeholder consensus. Ask: \u201cWhat happens if we delay this by 3 months?\u201d Be specific\u2014do not rely on \u201cit\u2019s important.\u201d Translate to risk, cost, or revenue impact.<\/p>\n<h3>Is WSJF suitable for non-technical stakeholders?<\/h3>\n<p>Yes. Explain it as: \u201cWe\u2019ll deliver the most impactful work first, so you get value sooner.\u201d Use simple visuals\u2014like a leaderboard of features by WSJF score.<\/p>\n<h3>Can WSJF replace story point estimation?<\/h3>\n<p>No. Use story points for effort estimation. WSJF is for prioritization. They serve different purposes. Think of story points as a \u201ccost,\u201d and WSJF as a \u201creturn.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When multiple teams depend on a shared backlog, arbitrary ordering leads to wasted effort, misaligned delivery [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1801,"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-1803","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>Agile Prioritization at Scale<\/title>\n<meta name=\"description\" content=\"Master WSJF prioritization and cost of delay agile in multi-team environments. Learn how to align enterprise backlogs with strategic value and flow 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\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Agile Prioritization at Scale\" \/>\n<meta property=\"og:description\" content=\"Master WSJF prioritization and cost of delay agile in multi-team environments. Learn how to align enterprise backlogs with strategic value and flow at scale.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills\u65e5\u672c\u8a9e\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/\",\"name\":\"Agile Prioritization at Scale\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\"},\"datePublished\":\"2026-02-25T10:46:11+00:00\",\"description\":\"Master WSJF prioritization and cost of delay agile in multi-team environments. Learn how to align enterprise backlogs with strategic value and flow at scale.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Supporting Practices and Scaled Facilitation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Backlog Prioritization in Multi-Team Environments\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#organization\",\"name\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills\u65e5\u672c\u8a9e\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Agile Prioritization at Scale","description":"Master WSJF prioritization and cost of delay agile in multi-team environments. Learn how to align enterprise backlogs with strategic value and flow 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\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/","og_locale":"ja_JP","og_type":"article","og_title":"Agile Prioritization at Scale","og_description":"Master WSJF prioritization and cost of delay agile in multi-team environments. Learn how to align enterprise backlogs with strategic value and flow at scale.","og_url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/","og_site_name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","twitter_card":"summary_large_image","twitter_misc":{"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"6\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/","name":"Agile Prioritization at Scale","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website"},"datePublished":"2026-02-25T10:46:11+00:00","description":"Master WSJF prioritization and cost of delay agile in multi-team environments. Learn how to align enterprise backlogs with strategic value and flow at scale.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-prioritization-at-scale\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ja\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Supporting Practices and Scaled Facilitation","item":"https:\/\/skills.visual-paradigm.com\/ja\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/"},{"@type":"ListItem","position":4,"name":"Backlog Prioritization in Multi-Team Environments"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#website","url":"https:\/\/skills.visual-paradigm.com\/ja\/","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ja\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#organization","name":"Visual Paradigm Skills\u65e5\u672c\u8a9e","url":"https:\/\/skills.visual-paradigm.com\/ja\/","logo":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ja\/wp-content\/uploads\/sites\/12\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills\u65e5\u672c\u8a9e"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ja\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1803","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1803\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/docs\/1801"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/media?parent=1803"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ja\/wp-json\/wp\/v2\/doc_tag?post=1803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}