{"id":1819,"date":"2026-02-25T10:46:17","date_gmt":"2026-02-25T10:46:17","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/"},"modified":"2026-02-25T10:46:17","modified_gmt":"2026-02-25T10:46:17","slug":"agile-glossary-enterprise","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/","title":{"rendered":"Appendix: Glossary of Large-Scale Agile Story Terms"},"content":{"rendered":"<p>When I first stepped into enterprise-scale Agile, I was handed a dozen acronyms and no clear way to distinguish between them. The confusion wasn\u2019t just in names\u2014it was in meaning, ownership, and flow. That moment taught me something critical: scaling isn\u2019t about adding more layers\u2014it\u2019s about creating shared understanding across complexity.<\/p>\n<p>This glossary is built from over 20 years of experience working with global enterprises, where alignment isn\u2019t a document\u2014it\u2019s a daily practice. I\u2019ve distilled the most critical terms into precise, actionable definitions that reflect real-world usage, not just textbook theory.<\/p>\n<p>Here, you\u2019ll find clear distinctions between epics, features, and stories; how dependency modeling shapes delivery; and what a \u201cvalid\u201d acceptance criterion looks like at scale. Whether you&#8217;re in a SAFe team, a LeSS-based structure, or a custom agile setup, these definitions help align your language, reduce ambiguity, and improve cross-team collaboration.<\/p>\n<p>Use this as a living reference. Revisit it during PI planning, backlog refinement, or when new teams join. Let it be the common ground that allows complex systems to evolve with agility and clarity.<\/p>\n<h2>Core Elements of Large-Scale Agile Storying<\/h2>\n<h3>Epics<\/h3>\n<p>An epic is a large body of work that delivers significant value but is too big to be completed by a single team in one sprint. It\u2019s typically broken down into features and stories.<\/p>\n<p>In enterprise environments, epics often originate from strategic objectives, OKRs, or portfolio-level initiatives.<\/p>\n<p><strong>Key insight:<\/strong> Not every large story is an epic. An epic must represent a meaningful, cohesive piece of business value\u2014often spanning multiple teams and systems.<\/p>\n<ul>\n<li>Originates from portfolio or program backlog<\/li>\n<li>Typically spans multiple iterations<\/li>\n<li>Must be decomposable into features<\/li>\n<li>Tracked via epic ID or reference in tools<\/li>\n<\/ul>\n<h3>Features<\/h3>\n<p>A feature is a specific function or capability that delivers measurable value to the user or customer. It\u2019s a logical grouping of related stories and is often owned by a single team or domain.<\/p>\n<p>Features are typically planned at the program level and are used to organize work that crosses multiple teams or involves integration testing.<\/p>\n<p><strong>Practical example:<\/strong> \u201cUser Authentication via Third-Party Identity Providers\u201d is a feature that may involve backend, frontend, and security teams.<\/p>\n<ul>\n<li>Owned by a single Agile Release Train (ART) or team<\/li>\n<li>Grouped under a program increment (PI)<\/li>\n<li>Has acceptance criteria that define completion<\/li>\n<li>May include multiple stories<\/li>\n<\/ul>\n<h3>User Stories<\/h3>\n<p>A user story is a concise, informal description of a feature from the user\u2019s perspective. It follows the format: \u201cAs a [type of user], I want [some goal] so that [some reason].\u201d<\/p>\n<p>At scale, stories must be small enough to be completed in one sprint but large enough to deliver tangible value.<\/p>\n<p><strong>My rule of thumb:<\/strong> If a story takes more than three sprints to complete, it\u2019s not a story\u2014it\u2019s an epic in disguise.<\/p>\n<ul>\n<li>Written in plain language, not technical jargon<\/li>\n<li>Each story should be testable and independent<\/li>\n<li>Estimates should reflect effort, not time<\/li>\n<li>Acceptance criteria must be specific<\/li>\n<\/ul>\n<h2>Advanced Concepts and Cross-Team Coordination<\/h2>\n<h3>Dependency Mapping<\/h3>\n<p>Dependency mapping identifies how stories, features, or epics rely on one another across teams. This is crucial in large systems where one team\u2019s work affects another\u2019s delivery.<\/p>\n<p>Dependencies aren\u2019t just technical\u2014they include shared services, data models, APIs, or shared user journeys.<\/p>\n<p><strong>Pro tip:<\/strong> Use visual dependency diagrams in story mapping or Kanban boards to surface hidden risks early.<\/p>\n<table border=\"1\" cellpadding=\"4\">\n<tbody>\n<tr>\n<th>Dependency Type<\/th>\n<th>Example<\/th>\n<th>Impact if Delayed<\/th>\n<\/tr>\n<tr>\n<td>Technical<\/td>\n<td>API contract not ready<\/td>\n<td>Frontend team blocked<\/td>\n<\/tr>\n<tr>\n<td>Data<\/td>\n<td>Shared database schema change<\/td>\n<td>Integration testing fails<\/td>\n<\/tr>\n<tr>\n<td>Business<\/td>\n<td>Payment gateway approval needed<\/td>\n<td>Feature cannot be tested<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Shared Acceptance Criteria<\/h3>\n<p>When multiple teams contribute to a single feature or user journey, acceptance criteria must be shared and agreed upon.<\/p>\n<p>These criteria ensure that all pieces of the story are tested and validated as a whole\u2014especially important in integrated systems.<\/p>\n<p><strong>Best practice:<\/strong> Use BDD (Behavior-Driven Development) syntax with Gherkin to write shared, executable criteria.<\/p>\n<pre><code>Given the user is logged in\nWhen they submit the payment form\nThen the transaction should be confirmed within 3 seconds\nAnd a confirmation email should be sent<\/code><\/pre>\n<h3>Definition of Done (DoD) at Scale<\/h3>\n<p>The Definition of Done is a shared standard that a story must meet before it\u2019s considered complete. At scale, this becomes a cross-team agreement.<\/p>\n<p>Each team may apply its own internal DoD, but the overall program DoD includes shared requirements like integration testing, security scanning, and deployment readiness.<\/p>\n<p><strong>Common elements in a scaled DoD:<\/strong><\/p>\n<ul>\n<li>Code reviewed and merged<\/li>\n<li>Unit and integration tests passing<\/li>\n<li>Security scan passed (SAST\/DAST)<\/li>\n<li>Documentation updated<\/li>\n<li>Deployed to staging environment<\/li>\n<li>Validated in end-to-end tests<\/li>\n<\/ul>\n<h2>Scaling Frameworks and Their Story Language<\/h2>\n<h3>SAFe User Story Structure<\/h3>\n<p>The Scaled Agile Framework (SAFe) introduces a clear hierarchy: Portfolio \u2192 Program \u2192 Team.<\/p>\n<p>Stories are the smallest unit of work at the team level, derived from features, which stem from epics.<\/p>\n<p>Each story must be traceable back to a feature or epic. This traceability is essential for program-level reporting and PI planning.<\/p>\n<p><strong>SAFe Tip:<\/strong> Use \u201cAs a [role], I want [capability] to [benefit]\u201d with a clear business value statement.<\/p>\n<h3>LeSS and Nexus<\/h3>\n<p>LeSS (Large-Scale Scrum) and Nexus (the scaling framework for Scrum) emphasize minimal process overhead and maximum transparency.<\/p>\n<p>Story writing remains simple and user-focused. However, LeSS introduces the concept of &#8220;Product Owners&#8221; and &#8220;Scrum Masters&#8221; at multiple levels, which affects how stories are refined and prioritized.<\/p>\n<p>Unlike SAFe, LeSS doesn\u2019t require features as a formal level. Instead, stories are grouped by theme or user journey.<\/p>\n<h3>Disciplined Agile (DA) Story Approach<\/h3>\n<p>Disciplined Agile emphasizes adapting story practices based on context. It supports a range of techniques from simple anecdotes to full modeling.<\/p>\n<p>DA encourages lightweight, adaptive story writing\u2014especially in complex or regulated environments.<\/p>\n<p><strong>Key principle:<\/strong> Don\u2019t force a model on a team. Let the nature of the work determine the level of detail.<\/p>\n<h2>Advanced Story Patterns and Practices<\/h2>\n<h3>Reusable Story Patterns<\/h3>\n<p>Organizations with multiple products or product lines often reuse common story fragments.<\/p>\n<p>For example, \u201cAs a user, I want to reset my password via email\u201d appears across banking, e-commerce, and SaaS products.<\/p>\n<p><strong>Benefit:<\/strong> Reuse reduces duplication, speeds up refinement, and ensures consistency.<\/p>\n<p>Store these in a central story library with versioning and usage notes.<\/p>\n<h3>Business-Driven Story Writing<\/h3>\n<p>Stories should reflect business outcomes, not just technical features.<\/p>\n<p>Instead of: \u201cAdd a dropdown menu\u201d<\/p>\n<p>Write: \u201cAs a customer, I want to filter my order list by status so I can quickly find pending deliveries.\u201d<\/p>\n<p>This links directly to business value and enables better prioritization.<\/p>\n<h3>Non-Functional Requirements (NFRs) in Stories<\/h3>\n<p>NFRs\u2014like performance, security, and availability\u2014are often hidden in acceptance criteria.<\/p>\n<p>Include them explicitly in the story to avoid rework.<\/p>\n<p><strong>Example:<\/strong> \u201cThe system must process 1,000 login attempts per second with 99.9% uptime.\u201d<\/p>\n<p>These are not just technical specs\u2014they are acceptance criteria.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between an epic and a feature in SAFe?<\/h3>\n<p>An epic is a large initiative originating at the portfolio level, often spanning multiple PIs. A feature is a capability that delivers value and is planned at the program level. Epics must be decomposed into features before being broken into user stories.<\/p>\n<h3>How do I ensure consistency in story writing across teams?<\/h3>\n<p>Establish a shared story template, common acceptance criteria format, and a central story library. Use regular story workshops and peer reviews to enforce standards.<\/p>\n<h3>Can a story be owned by multiple teams?<\/h3>\n<p>Yes, but only when it involves shared responsibilities. Use cross-team story ownership with a single Product Owner and clear dependency mapping. Avoid splitting ownership too thinly\u2014this leads to accountability gaps.<\/p>\n<h3>What is a \u201cvalid\u201d acceptance criterion?<\/h3>\n<p>A valid criterion is specific, testable, unambiguous, and tied to actual user value. It should be written in plain language and executable (e.g., via BDD). It must pass verification in integrated testing.<\/p>\n<h3>How do I handle dependency risks in large-scale Agile?<\/h3>\n<p>Map all dependencies early using visual models. Flag high-risk dependencies in the backlog. Use dependency guards in PI planning, and reinforce shared ownership to reduce bottlenecks.<\/p>\n<h3>Why do we need a scaled agile glossary?<\/h3>\n<p>Because agility at scale isn\u2019t about more processes\u2014it\u2019s about shared language. A common glossary prevents misunderstandings, reduces rework, and ensures all teams align on core concepts like \u201cepic,\u201d \u201cfeature,\u201d and \u201cdefinition of done.\u201d<\/p>\n<p><strong>agile glossary enterprise<\/strong> is not just a tool\u2014it\u2019s a foundation for alignment, transparency, and sustainable agility across complex organizations.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I first stepped into enterprise-scale Agile, I was handed a dozen acronyms and no clear way to distinguish between them. The confusion wasn\u2019t just in names\u2014it was in meaning, ownership, and flow. That moment taught me something critical: scaling isn\u2019t about adding more layers\u2014it\u2019s about creating shared understanding across complexity. This glossary is built [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1813,"menu_order":5,"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-1819","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 Glossary Enterprise<\/title>\n<meta name=\"description\" content=\"Master essential large-scale agile story terms with this authoritative glossary. Perfect for enterprise practitioners seeking clarity, alignment, and consistency across teams and frameworks.\" \/>\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\/scaled-agile-case-studies\/agile-glossary-enterprise\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Agile Glossary Enterprise\" \/>\n<meta property=\"og:description\" content=\"Master essential large-scale agile story terms with this authoritative glossary. Perfect for enterprise practitioners seeking clarity, alignment, and consistency across teams and frameworks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/\" \/>\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\/scaled-agile-case-studies\/agile-glossary-enterprise\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/\",\"name\":\"Agile Glossary Enterprise\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:46:17+00:00\",\"description\":\"Master essential large-scale agile story terms with this authoritative glossary. Perfect for enterprise practitioners seeking clarity, alignment, and consistency across teams and frameworks.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/#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\":\"Real-World Lessons and Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Appendix: Glossary of Large-Scale Agile Story Terms\"}]},{\"@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":"Agile Glossary Enterprise","description":"Master essential large-scale agile story terms with this authoritative glossary. Perfect for enterprise practitioners seeking clarity, alignment, and consistency across teams and frameworks.","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\/scaled-agile-case-studies\/agile-glossary-enterprise\/","og_locale":"id_ID","og_type":"article","og_title":"Agile Glossary Enterprise","og_description":"Master essential large-scale agile story terms with this authoritative glossary. Perfect for enterprise practitioners seeking clarity, alignment, and consistency across teams and frameworks.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/","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\/scaled-agile-case-studies\/agile-glossary-enterprise\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/","name":"Agile Glossary Enterprise","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:46:17+00:00","description":"Master essential large-scale agile story terms with this authoritative glossary. Perfect for enterprise practitioners seeking clarity, alignment, and consistency across teams and frameworks.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/agile-glossary-enterprise\/#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":"Real-World Lessons and Case Studies","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/"},{"@type":"ListItem","position":4,"name":"Appendix: Glossary of Large-Scale Agile Story Terms"}]},{"@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\/1819","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\/1819\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1813"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1819"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}