{"id":1802,"date":"2026-02-25T10:46:11","date_gmt":"2026-02-25T10:46:11","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/"},"modified":"2026-03-02T09:05:28","modified_gmt":"2026-03-02T09:05:28","slug":"scaled-agile-estimation-story-points-vs-flow-metrics","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/","title":{"rendered":"Agile Estimation at Scale: Story Points vs Flow Metrics"},"content":{"rendered":"<p>One small shift separates teams who estimate with confidence from those stuck in estimation paralysis: stopping to ask, \u201cWhat are we trying to predict?\u201d\u2014and instead focusing on what we want to measure. This simple pivot turns estimation from an exercise in guesswork into a tool for transparency and flow.<\/p>\n<p>For over two decades, I\u2019ve worked with enterprise teams where story points were initially embraced as a silver bullet. But as complexity grew, so did the noise. Teams debated whether \u201c8\u201d meant \u201chigh effort\u201d or \u201cthree weeks.\u201d Story points at scale quickly became a source of misalignment, not clarity.<\/p>\n<p>My breakthrough came when I stopped treating estimation as a task and started seeing it as a measurement of delivery predictability. That\u2019s when flow metrics agile\u2014cycle time, lead time, throughput\u2014became my primary lens. The real power of scaled agile estimation isn\u2019t in the number of points; it\u2019s in the consistency of delivery.<\/p>\n<p>By the end of this chapter, you\u2019ll understand how to weigh story points at scale against empirical flow metrics, when to use each, and how to transition from a point-based culture to a flow-driven one without losing alignment.<\/p>\n<h2>Why Story Points at Scale Often Break Down<\/h2>\n<p>Story points were designed for small, co-located teams with stable velocity. But in large-scale Agile, that simplicity fractures.<\/p>\n<p>When multiple teams operate under different contexts\u2014different tech stacks, varying skill levels, distributed ownership\u2014comparing story points becomes meaningless. A \u201c5\u201d in one team might be a \u201c3\u201d in another.<\/p>\n<p>Teams start using story points not to estimate effort, but to justify capacity. We\u2019ve turned estimation into a compliance ritual, not a planning tool.<\/p>\n<p>Consider this: a team estimates 200 story points for a feature. The business expects delivery in two sprints. The team delivers 80 points. The remaining 120 are \u201cin flight.\u201d The next sprint, they deliver 40. The business asks, \u201cWhy aren\u2019t we on track?\u201d<\/p>\n<p>Here\u2019s the truth: story points don\u2019t predict delivery. They reflect past performance in a context that no longer exists. That\u2019s why scaled agile estimation must evolve.<\/p>\n<h3>Three Signs You Need to Move Beyond Story Points<\/h3>\n<ul>\n<li>Teams are measuring velocity instead of throughput.<\/li>\n<li>Estimates are based on historical averages, not team capacity.<\/li>\n<li>Estimation discussions are dominated by political negotiation, not value alignment.<\/li>\n<\/ul>\n<p>When these happen, story points at scale are no longer estimating\u2014they\u2019re hiding inefficiencies.<\/p>\n<h2>Flow Metrics Agile: The Empirical Alternative<\/h2>\n<p>Flow metrics agile are grounded in the real world. They measure what actually happens, not what someone thinks should happen.<\/p>\n<p>Throughput\u2014the number of stories completed per sprint\u2014gives a clear, observable baseline. Cycle time\u2014the time from story start to completion\u2014reveals how fast value flows through the system.<\/p>\n<p>When I led a delivery program across 12 teams, we found that throughput varied by 40% between teams. But when we normalized for team size and skill, we discovered that the variation wasn\u2019t in effort\u2014it was in process bottlenecks.<\/p>\n<p>One team had a cycle time of 3 days; another took 8. The difference wasn\u2019t in story size\u2014it was in how work was pulled, reviewed, and deployed.<\/p>\n<p>That\u2019s where flow metrics agile become powerful: they expose invisible constraints.<\/p>\n<h3>Key Flow Metrics to Track at Scale<\/h3>\n<p>Start with these three:<\/p>\n<ul>\n<li><strong>Throughput:<\/strong> Average number of stories completed per sprint. Use for forecasting.<\/li>\n<li><strong>Lead Time:<\/strong> Time from story creation to deployment. Measures end-to-end delivery speed.<\/li>\n<li><strong>Cycle Time:<\/strong> Time from start of development to deployment. Focuses on work-in-process efficiency.<\/li>\n<\/ul>\n<p>These metrics don\u2019t require story points. They just require consistent data\u2014something teams can collect through their backlog tools or CI\/CD pipelines.<\/p>\n<p>For example: a team with a 5-day average cycle time and 12 stories per sprint can reliably forecast 10 stories in a 4-day sprint. No estimation needed\u2014just data.<\/p>\n<h2>How to Transition from Points to Flow<\/h2>\n<p>Shifting from story points to flow metrics isn\u2019t a one-off event. It\u2019s a cultural and process transformation. Here\u2019s how to do it, step-by-step.<\/p>\n<ol>\n<li><strong>Stop estimating in points.<\/strong> Remove story points from backlogs. Replace them with a simple \u201cready\u201d or \u201cin progress\u201d flag.<\/li>\n<li><strong>Track one metric per team.<\/strong> Start with throughput. Measure weekly. Plot it on a simple line chart.<\/li>\n<li><strong>Calculate average cycle time.<\/strong> Use the date the story enters \u201cin progress\u201d to when it\u2019s deployed. Average it monthly.<\/li>\n<li><strong>Run a 30-day flow experiment.<\/strong> For one sprint, team members log entry and exit times for every story. Use this to calibrate cycle times.<\/li>\n<li><strong>Use flow to forecast.<\/strong> Apply historical throughput to predict delivery timelines. If a team averages 8 stories per sprint, 40 stories will take 5 sprints\u2014regardless of story complexity.<\/li>\n<\/ol>\n<p>After three months, revisit. You\u2019ll find teams are more predictable, and estimation meetings have shrunk from 2 hours to 20 minutes.<\/p>\n<h3>When Story Points Still Make Sense<\/h3>\n<p>Not every situation demands a full switch. In some cases, story points at scale serve a useful purpose\u2014but only if used correctly.<\/p>\n<p>Use story points when:<\/p>\n<ul>\n<li>Planning at the program level (e.g., PI planning), where relative sizing helps align team capacity.<\/li>\n<li>Comparing effort across teams with identical workflows and skill levels.<\/li>\n<li>Estimating features that are still too abstract to break into stories.<\/li>\n<\/ul>\n<p>But never let story points drive acceptance. The real measure of value is delivery\u2014measured in throughput and cycle time.<\/p>\n<h2>Comparing Estimation Models at Scale<\/h2>\n<p>Let\u2019s compare the two approaches side by side.<\/p>\n<table>\n<thead>\n<tr>\n<th>Aspect<\/th>\n<th>Story Points at Scale<\/th>\n<th>Flow Metrics Agile<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>What it measures<\/td>\n<td>Relative effort (subjective)<\/td>\n<td>Actual delivery speed (objective)<\/td>\n<\/tr>\n<tr>\n<td>Forecast accuracy<\/td>\n<td>Low (depends on velocity)<\/td>\n<td>High (based on historical throughput)<\/td>\n<\/tr>\n<tr>\n<td>Team adaptability<\/td>\n<td>Low (fixed velocity)<\/td>\n<td>High (predicts based on flow)<\/td>\n<\/tr>\n<tr>\n<td>Dependency management<\/td>\n<td>Hard (no visibility into flow)<\/td>\n<td>Easy (track cycle time across teams)<\/td>\n<\/tr>\n<tr>\n<td>Team buy-in<\/td>\n<td>Often low (perceived as bureaucratic)<\/td>\n<td>High (based on shared data)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This table isn\u2019t about which is better\u2014it\u2019s about which is more aligned with the goals of scaled agile estimation.<\/p>\n<p>When the goal is predictability, flow wins. When the goal is alignment during PI planning, story points may still have a place\u2014but only when paired with flow data.<\/p>\n<h2>What to Do When Teams Resist the Shift<\/h2>\n<p>Resistance is expected. Some teams will say, \u201cWe\u2019ve been using points for years.\u201d Others will say, \u201cWe can\u2019t forecast without points.\u201d<\/p>\n<p>My advice: don\u2019t fight the resistance. Explain what you\u2019re measuring\u2014and what you\u2019re not.<\/p>\n<p>\u201cWe\u2019re not abandoning estimation. We\u2019re moving from guessing effort to measuring delivery. The number of points doesn\u2019t matter. What matters is how fast you deliver.\u201d<\/p>\n<p>Start by running a 2-week pilot. Track both story points and flow metrics. Show the data side by side. Let the results speak.<\/p>\n<p>One client ran this pilot. They saw that flow predictions were 92% accurate over three sprints. Story point forecasts were 58% accurate. The team didn\u2019t need to change their work\u2014they just needed to change how they measured it.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use story points and flow metrics together?<\/h3>\n<p>Yes\u2014but only in a layered way. Use story points for high-level planning (e.g., PI planning). Use flow metrics for delivery forecasting and process improvement. Don\u2019t mix them in the same sprint.<\/p>\n<h3>Do flow metrics agile work for non-iterative teams?<\/h3>\n<p>Yes. Even in release-based or waterfall-adjacent teams, cycle time and throughput can be measured. Track from \u201cwork initiated\u201d to \u201cdeployed.\u201d It reveals bottlenecks, even if delivery isn\u2019t sprint-based.<\/p>\n<h3>What if our throughput varies wildly?<\/h3>\n<p>That\u2019s a signal. Variability means inconsistency. Look at process\u2014work-in-progress limits, review delays, dependency queues. Flow metrics agile help you detect and fix these issues.<\/p>\n<h3>How often should I review flow metrics?<\/h3>\n<p>Weekly for teams, monthly for programs. Don\u2019t wait for PI planning. Use flow data to adjust capacity and scope in real time.<\/p>\n<h3>Is flow metrics agile suitable for regulated industries?<\/h3>\n<p>Absolutely. Compliance isn\u2019t about estimation\u2014it\u2019s about traceability and auditability. Flow metrics can be stored and reported without altering the work. Use them to demonstrate predictability and process control.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One small shift separates teams who estimate with confidence from those stuck in estimation paralysis: stopping to ask, \u201cWhat are we trying to predict?\u201d\u2014and instead focusing on what we want to measure. This simple pivot turns estimation from an exercise in guesswork into a tool for transparency and flow. For over two decades, I\u2019ve worked [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1801,"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-1802","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>Scaled Agile Estimation: Story Points vs Flow Metrics<\/title>\n<meta name=\"description\" content=\"Compare story points at scale with empirical flow metrics in Agile estimation. Learn when to use each for reliable delivery forecasting in large-scale Agile environments.\" \/>\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\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scaled Agile Estimation: Story Points vs Flow Metrics\" \/>\n<meta property=\"og:description\" content=\"Compare story points at scale with empirical flow metrics in Agile estimation. Learn when to use each for reliable delivery forecasting in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:05:28+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/\",\"name\":\"Scaled Agile Estimation: Story Points vs Flow Metrics\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:46:11+00:00\",\"dateModified\":\"2026-03-02T09:05:28+00:00\",\"description\":\"Compare story points at scale with empirical flow metrics in Agile estimation. Learn when to use each for reliable delivery forecasting in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Supporting Practices and Scaled Facilitation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Agile Estimation at Scale: Story Points vs Flow Metrics\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scaled Agile Estimation: Story Points vs Flow Metrics","description":"Compare story points at scale with empirical flow metrics in Agile estimation. Learn when to use each for reliable delivery forecasting in large-scale Agile environments.","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\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/","og_locale":"de_DE","og_type":"article","og_title":"Scaled Agile Estimation: Story Points vs Flow Metrics","og_description":"Compare story points at scale with empirical flow metrics in Agile estimation. Learn when to use each for reliable delivery forecasting in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/","og_site_name":"Visual Paradigm Skills Deutsch","article_modified_time":"2026-03-02T09:05:28+00:00","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/","name":"Scaled Agile Estimation: Story Points vs Flow Metrics","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:46:11+00:00","dateModified":"2026-03-02T09:05:28+00:00","description":"Compare story points at scale with empirical flow metrics in Agile estimation. Learn when to use each for reliable delivery forecasting in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/scaled-agile-estimation-story-points-vs-flow-metrics\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Supporting Practices and Scaled Facilitation","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/"},{"@type":"ListItem","position":4,"name":"Agile Estimation at Scale: Story Points vs Flow Metrics"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1802","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1802\/revisions"}],"predecessor-version":[{"id":2383,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1802\/revisions\/2383"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1801"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1802"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}