{"id":689,"date":"2026-02-25T10:22:49","date_gmt":"2026-02-25T10:22:49","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/"},"modified":"2026-03-02T09:09:04","modified_gmt":"2026-03-02T09:09:04","slug":"stale-backlog-items-revival","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/","title":{"rendered":"Stories That Grow Stale in the Backlog"},"content":{"rendered":"<p>It\u2019s that moment when you open the backlog and realize half the stories haven\u2019t been touched in months. Not because they\u2019re unimportant\u2014but because they\u2019re forgotten. You\u2019re not alone. I\u2019ve seen teams with dozens of old user stories, gathering dust like outdated technical documentation. The signal? The team hasn\u2019t touched them in a sprint cycle, the acceptance criteria are vague or missing, and no one remembers what they were even for.<\/p>\n<p>That\u2019s not just a backlog problem. It\u2019s a signal that your product backlog has lost alignment with reality. The real turning point happens when the team starts questioning whether a story is even still relevant\u2014when a stakeholder says, \u201cWait, are we still doing this?\u201d That\u2019s when you know the story has gone stale.<\/p>\n<p>My experience over two decades has taught me: a story is a placeholder for conversation. If that conversation hasn\u2019t happened in months, the story has likely outlived its usefulness. But it doesn\u2019t have to be scrapped. The key is not to avoid writing old stories\u2014but to recognize them early and act.<\/p>\n<p>Here, you\u2019ll learn how to diagnose, refresh, or retire stale backlog items. You\u2019ll gain practical frameworks for backlog maintenance agile, avoid the trap of accumulating unactionable items, and keep your team focused on what truly delivers value.<\/p>\n<h2>Why User Stories Go Stale<\/h2>\n<p>Stale backlog items don\u2019t form overnight. They accumulate due to a mix of inertia, changing priorities, and poor tracking. You can spot them by patterns\u2014not just time, but behavior.<\/p>\n<p>Here are the most common causes:<\/p>\n<ul>\n<li><strong>Unclear business context<\/strong> \u2013 The original goal was never validated or revisited.<\/li>\n<li><strong>Missing or outdated acceptance criteria<\/strong> \u2013 The story can\u2019t be tested or verified anymore.<\/li>\n<li><strong>Shifted user needs<\/strong> \u2013 The target user or workflow has changed significantly.<\/li>\n<li><strong>Unrealized technical dependencies<\/strong> \u2013 The story depends on a feature or system that never shipped.<\/li>\n<li><strong>Over-scope without refinement<\/strong> \u2013 The story was never broken down or re-evaluated after initial writing.<\/li>\n<\/ul>\n<p>These are not just &#8222;outdated&#8221; items\u2014they are liabilities. They consume mental bandwidth, clutter planning, and create confusion when the team tries to estimate or implement them.<\/p>\n<h3>Signs Your Story Is Stale<\/h3>\n<p>Not every old user story is stale. But these indicators often mean it\u2019s time for a review:<\/p>\n<ul>\n<li>The story was written more than 6 months ago.<\/li>\n<li>No one on the team can recall the original intent.<\/li>\n<li>Acceptance criteria are missing, vague, or outdated.<\/li>\n<li>The user role or business goal has changed.<\/li>\n<li>It\u2019s been passed over in three consecutive backlog refinement sessions.<\/li>\n<li>It references a feature or system that no longer exists.<\/li>\n<\/ul>\n<p>When multiple signs apply, the story is almost certainly stale. But don\u2019t assume it\u2019s useless. Sometimes, what looks like a dead end is a hidden gem in need of revival.<\/p>\n<h2>Strategies for Handling Stale Backlog Items<\/h2>\n<p>Don\u2019t just delete old user stories. That\u2019s throwing away potential value. Instead, apply a structured approach: diagnose, refresh, or retire.<\/p>\n<h3>1. Audit the Backlog Quarterly<\/h3>\n<p>Run a formal backlog health check every quarter. Use a simple scoring system to assess each story:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Criterion<\/th>\n<th>Score (1\u20135)<\/th>\n<\/tr>\n<tr>\n<td>Clear user role and goal<\/td>\n<td>1\u20135<\/td>\n<\/tr>\n<tr>\n<td>Testable acceptance criteria<\/td>\n<td>1\u20135<\/td>\n<\/tr>\n<tr>\n<td>Alignment with current roadmap<\/td>\n<td>1\u20135<\/td>\n<\/tr>\n<tr>\n<td>Recent team engagement<\/td>\n<td>1\u20135<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Stories scoring below 3 in multiple categories should be flagged for review.<\/p>\n<h3>2. Re-engage the Conversation<\/h3>\n<p>Not every stale story needs to be deleted. Some can be revived. Start by re-clarifying the conversation:<\/p>\n<ol>\n<li>Re-engage the original author or sponsor.<\/li>\n<li>Ask: \u201cIs this still valuable? Has anything changed?\u201d<\/li>\n<li>Update acceptance criteria based on current context.<\/li>\n<li>Re-estimate if necessary.<\/li>\n<li>Re-prioritize with the team.<\/li>\n<\/ol>\n<p>This process isn\u2019t just about updating text\u2014it\u2019s about revalidating the story\u2019s purpose. If the answer is \u201cno,\u201d it\u2019s time to retire.<\/p>\n<h3>3. Retire with Purpose<\/h3>\n<p>When a story is truly obsolete, don\u2019t just delete it. Archive it with a brief note:<\/p>\n<pre><code>Story ID: US-404\r\nStatus: Retired\r\nReason: User role changed; feature replaced by automated workflow.\r\nArchived: 2024-03-15\r\n<\/code><\/pre>\n<p>Retiring is not deleting. It\u2019s documenting why the story no longer matters. This preserves traceability and avoids future confusion.<\/p>\n<h3>4. Prevent Future Stagnation<\/h3>\n<p>Stale backlog items don\u2019t just happen\u2014they\u2019re allowed to happen. Prevent them with:<\/p>\n<ul>\n<li><strong>Time-bound backlog reviews<\/strong> \u2013 Set a policy: \u201cNo story older than 90 days without a check-in.\u201d<\/li>\n<li><strong>Ownership rotation<\/strong> \u2013 Assign each story a \u201cstory owner\u201d responsible for keeping it alive or retiring it.<\/li>\n<li><strong>Link to epics or themes<\/strong> \u2013 Ensure stories are tied to current objectives. If the theme is gone, the story dies.<\/li>\n<\/ul>\n<p>These are not just hygiene practices\u2014they\u2019re governance.<\/p>\n<h2>When to Keep, Revise, or Remove<\/h2>\n<p>Not every story needs the same treatment. Use this decision tree:<\/p>\n<ul>\n<li><strong>Keep<\/strong> \u2013 The story is still relevant, has clear acceptance criteria, and aligns with current goals.<\/li>\n<li><strong>Revise<\/strong> \u2013 The intent is still valid, but the wording, acceptance criteria, or scope is outdated.<\/li>\n<li><strong>Retire<\/strong> \u2013 The story is obsolete, misaligned, or has been replaced.<\/li>\n<li><strong>Split<\/strong> \u2013 The story is too large or covers multiple outcomes.<\/li>\n<\/ul>\n<p>Remember: A story that can\u2019t be tested, understood, or validated is not a story. It\u2019s a placeholder for a conversation that never happened.<\/p>\n<h2>Best Practices for Backlog Maintenance Agile<\/h2>\n<p>Good backlog maintenance isn\u2019t about volume. It\u2019s about quality, relevance, and flow.<\/p>\n<p>Here\u2019s what I\u2019ve seen work in real teams:<\/p>\n<ul>\n<li><strong>Hold a quarterly backlog spring clean<\/strong> \u2013 Dedicate one sprint to reviewing, rewriting, and retiring stories.<\/li>\n<li><strong>Use a \u201cstory health\u201d dashboard<\/strong> \u2013 Track age, last update, and stakeholder engagement.<\/li>\n<li><strong>Set a maximum age for stories<\/strong> \u2013 No story should sit in the backlog longer than 6\u20139 months without a review.<\/li>\n<li><strong>Make refinement a team ritual<\/strong> \u2013 Don\u2019t let stories gather dust between sprints.<\/li>\n<li><strong>Document decisions<\/strong> \u2013 When you retire a story, write why. Future teams will thank you.<\/li>\n<\/ul>\n<p>These practices aren\u2019t about \u201ccleaning up.\u201d They\u2019re about maintaining trust in the backlog as a living product.<\/p>\n<h2>Conclusion<\/h2>\n<p>Stale backlog items aren\u2019t a sign of failure\u2014they\u2019re a symptom. They mean the backlog isn\u2019t being treated as a dynamic, living document. The real goal isn\u2019t to eliminate old user stories. It\u2019s to ensure every story still serves a purpose.<\/p>\n<p>By applying regular audits, re-engaging conversations, and retiring items with clarity, your team can turn backlog rot into backlog renewal. This is not just maintenance\u2014it\u2019s strategy. With consistent backlog maintenance agile, you ensure that only stories that matter reach the sprint table.<\/p>\n<p>Don\u2019t let the backlog become a graveyard of forgotten ideas. Keep it active. Keep it relevant. Keep it alive.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How do I know if a backlog item is truly stale?<\/h3>\n<p>Look for three signals: no recent engagement, outdated acceptance criteria, and misalignment with current business goals. If the original sponsor can\u2019t answer, \u201cIs this still useful?\u201d\u2014it\u2019s likely stale.<\/p>\n<h3>Can I revive an old user story without rewriting it?<\/h3>\n<p>Only if it\u2019s still valid and testable. But that\u2019s rare. Reviving usually means rewriting the description, updating the acceptance criteria, and revalidating the goal. Never assume the original story still makes sense.<\/p>\n<h3>Should I delete old user stories from the backlog?<\/h3>\n<p>No\u2014delete only when the story is obsolete and won\u2019t be needed. Instead, mark it as \u201cretired\u201d with a clear reason. This preserves transparency and traceability for future reference.<\/p>\n<h3>How often should I review my backlog for stale items?<\/h3>\n<p>At minimum, quarterly. But I recommend a dedicated sprint every 6 months for a full backlog audit. This prevents stagnation and keeps the backlog aligned with current priorities.<\/p>\n<h3>What if the original author is no longer on the team?<\/h3>\n<p>Assign a new owner from the product team or ask the product owner to reassess. If no one can clarify the intent, the story is effectively obsolete and should be retired or revised.<\/p>\n<h3>How do I prevent backlog rot in the future?<\/h3>\n<p>Use time-bound reviews, assign story owners, link stories to current epics, and make backlog health a standing agenda item in sprint planning and refinement. Treat the backlog like a living system.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It\u2019s that moment when you open the backlog and realize half the stories haven\u2019t been touched in months. Not because they\u2019re unimportant\u2014but because they\u2019re forgotten. You\u2019re not alone. I\u2019ve seen teams with dozens of old user stories, gathering dust like outdated technical documentation. The signal? The team hasn\u2019t touched them in a sprint cycle, the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":688,"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-689","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>Stale Backlog Items: Reviving Old User Stories<\/title>\n<meta name=\"description\" content=\"Learn how to identify, refresh, or retire old user stories that stagnate in your backlog. Practical strategies for backlog maintenance agile and improving story relevance.\" \/>\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\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Stale Backlog Items: Reviving Old User Stories\" \/>\n<meta property=\"og:description\" content=\"Learn how to identify, refresh, or retire old user stories that stagnate in your backlog. Practical strategies for backlog maintenance agile and improving story relevance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:09:04+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/\",\"name\":\"Stale Backlog Items: Reviving Old User Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:22:49+00:00\",\"dateModified\":\"2026-03-02T09:09:04+00:00\",\"description\":\"Learn how to identify, refresh, or retire old user stories that stagnate in your backlog. Practical strategies for backlog maintenance agile and improving story relevance.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scaling and Lifecycle Issues\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Stories That Grow Stale in the Backlog\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Stale Backlog Items: Reviving Old User Stories","description":"Learn how to identify, refresh, or retire old user stories that stagnate in your backlog. Practical strategies for backlog maintenance agile and improving story relevance.","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\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/","og_locale":"pl_PL","og_type":"article","og_title":"Stale Backlog Items: Reviving Old User Stories","og_description":"Learn how to identify, refresh, or retire old user stories that stagnate in your backlog. Practical strategies for backlog maintenance agile and improving story relevance.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/","og_site_name":"Visual Paradigm Skills Polski","article_modified_time":"2026-03-02T09:09:04+00:00","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"6 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/","name":"Stale Backlog Items: Reviving Old User Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:22:49+00:00","dateModified":"2026-03-02T09:09:04+00:00","description":"Learn how to identify, refresh, or retire old user stories that stagnate in your backlog. Practical strategies for backlog maintenance agile and improving story relevance.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/stale-backlog-items-revival\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Scaling and Lifecycle Issues","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/"},{"@type":"ListItem","position":4,"name":"Stories That Grow Stale in the Backlog"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/689","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/689\/revisions"}],"predecessor-version":[{"id":2402,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/689\/revisions\/2402"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/688"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=689"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=689"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}