{"id":691,"date":"2026-02-25T10:22:50","date_gmt":"2026-02-25T10:22:50","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/"},"modified":"2026-02-25T10:22:50","modified_gmt":"2026-02-25T10:22:50","slug":"refinement-inconsistency-agile","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/","title":{"rendered":"Inconsistent Refinement Practices"},"content":{"rendered":"<p>When a team says they&#8217;re &#8222;refining the backlog&#8221; but the work feels chaotic, like someone\u2019s rearranging a garage without a system\u2014this is refinement inconsistency. I\u2019ve seen teams skip it for weeks, then try to cram three sprints\u2019 worth of prep into a single session. The result? Half-baked stories, rushed estimates, and sprint zero surprises.<\/p>\n<p>Refinement inconsistency isn\u2019t about effort\u2014it\u2019s about rhythm. When sessions are unpredictable, no one treats them as a commitment. Conversations become reactive, not proactive. Stories don\u2019t get clarity; they get abandoned or delivered with assumptions baked in.<\/p>\n<p>You\u2019ll know it\u2019s happening if your team asks, \u201cIs this sprint\u2019s refinement even happening?\u201d or if the backlog is full of vague, oversized epics with no clear path forward. I\u2019ve worked with teams where refinement was just an afterthought, often squeezed between meetings or left for the last minute of a sprint. That\u2019s not refinement\u2014 it\u2019s triage under duress.<\/p>\n<p>What you gain from this chapter is a clear, repeatable approach to backlog grooming patterns. You\u2019ll learn how to build a stable refinement cadence agile that supports velocity, clarity, and sustainable delivery. No fluff. No magic. Just practical rhythm.<\/p>\n<h2>Why Refinement Cadence Agile Matters<\/h2>\n<p>Refinement isn\u2019t a one-time task. It\u2019s a continuous process that needs structure. Without a cadence, teams lose context, miss alignment, and waste time re-clarifying stories that should\u2019ve been ready.<\/p>\n<p>Think of refinement as the nervous system of your backlog. If the signals are erratic, the system misfires. The team might start coding without understanding the real user need, or worse, they\u2019ll build something nobody actually wanted.<\/p>\n<p>Here\u2019s what happens when you have no consistent refinement cadence:<\/p>\n<ul>\n<li>Stories arrive in sprint planning already too vague or too large.<\/li>\n<li>Estimates vary wildly because no one agrees on scope.<\/li>\n<li>Acceptance criteria are added too late, causing rework.<\/li>\n<li>Team members lose trust in the process.<\/li>\n<\/ul>\n<p>That\u2019s refinement inconsistency in action.<\/p>\n<h3>The Hidden Cost of Irregular Sessions<\/h3>\n<p>I once worked with a team that held refinement only \u201cwhen free\u201d between sprint reviews. They called it \u201cagile flexibility.\u201d It wasn\u2019t flexibility\u2014it was chaos. Their velocity fluctuated wildly, and they often pulled incomplete stories into sprints. Why? Because refinement wasn\u2019t a rhythm\u2014it was an event.<\/p>\n<p>One key insight: consistency beats frequency. A weekly 30-minute session is more effective than a monthly 3-hour marathon. You\u2019re not trying to do everything at once\u2014you\u2019re trying to stay aligned.<\/p>\n<p>Refinement cadence agile isn\u2019t about how long you meet. It\u2019s about how predictably you meet. When refinement becomes a recurring, time-boxed event, the team starts treating it with the same respect as sprint planning or demos.<\/p>\n<h2>Practical Cadence Models for Consistent Refinement<\/h2>\n<p>There\u2019s no one-size-fits-all refinement cadence agile. But there are proven models that work across teams of different sizes and maturity levels. The key is to anchor it to the sprint rhythm and keep it lightweight.<\/p>\n<h3>Model 1: Weekly, Time-Boxed, Team-Shared<\/h3>\n<p>Set a fixed time each week\u2014ideally right after sprint review or sprint planning\u2014for a 30- to 45-minute session. This keeps refinement predictable and embedded in the team\u2019s rhythm.<\/p>\n<p>Use this time to:<\/p>\n<ul>\n<li>Break down large epics into manageable stories.<\/li>\n<li>Clarify acceptance criteria with the team.<\/li>\n<li>Update estimates based on new information.<\/li>\n<li>Validate alignment with the roadmap.<\/li>\n<\/ul>\n<p>This model works best for teams with stable sprint lengths and moderate story complexity. It prevents backlog rot by ensuring stories are maintained regularly.<\/p>\n<h3>Model 2: Bi-Weekly Refinement with Pre-Work<\/h3>\n<p>For teams with higher story volume, consider a bi-weekly refinement session\u2014but with a twist: ask the team to come prepared.<\/p>\n<p>Before the session, ask stakeholders or product owners to:<\/p>\n<ul>\n<li>Review the top 5 backlog items.<\/li>\n<li>Write summary descriptions or sketches.<\/li>\n<li>Identify any dependency or risk.<\/li>\n<\/ul>\n<p>During the session, focus only on discussion and validation. This cuts down on wasted time and ensures that refinement isn\u2019t just a conversation\u2014it\u2019s a decision point.<\/p>\n<h3>Model 3: Story-Specific Refinement (For High-Value or Complex Features)<\/h3>\n<p>Some stories are too complex to be refined in bulk. When dealing with high-stakes, cross-team, or technical stories, schedule a dedicated refinement session.<\/p>\n<p>Use this to:<\/p>\n<ul>\n<li>Map user flows or decision trees.<\/li>\n<li>Collaborate with QA on edge cases.<\/li>\n<li>Validate assumptions with developers.<\/li>\n<\/ul>\n<p>These aren\u2019t routine meetings\u2014they\u2019re targeted refinement events. They\u2019re not for every story, but they\u2019re essential for critical features.<\/p>\n<h2>Comparing Refinement Cadence Models<\/h2>\n<p>Here\u2019s how the three models compare based on team size, sprint length, and story complexity:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Cadence Model<\/th>\n<th>Best For<\/th>\n<th>Team Size<\/th>\n<th>Sprint Length<\/th>\n<th>Story Complexity<\/th>\n<\/tr>\n<tr>\n<td>Weekly, time-boxed<\/td>\n<td>Most teams, stable backlog<\/td>\n<td>Small to medium<\/td>\n<td>2\u20134 weeks<\/td>\n<td>Low to medium<\/td>\n<\/tr>\n<tr>\n<td>Bi-weekly with pre-work<\/td>\n<td>High-volume backlogs, mature teams<\/td>\n<td>Medium to large<\/td>\n<td>2\u20134 weeks<\/td>\n<td>Medium<\/td>\n<\/tr>\n<tr>\n<td>Story-specific refinement<\/td>\n<td>Complex or cross-functional features<\/td>\n<td>Large<\/td>\n<td>2\u20134 weeks<\/td>\n<td>High<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Choose based on your team\u2019s current stage, not what sounds \u201cideal.\u201d I\u2019ve seen teams succeed with weekly sessions even when they were large and complex\u2014because they focused on quality over quantity.<\/p>\n<h2>Common Pitfalls to Avoid<\/h2>\n<p>Even with a cadence, teams still fall into traps. Here are the most frequent:<\/p>\n<ul>\n<li><strong>Refinement without ownership:<\/strong> When no one owns the outcome, sessions become discussion forums with no decisions.<\/li>\n<li><strong>Too many stories at once:<\/strong> Trying to refine 10 items in 30 minutes leads to surface-level work. Focus on the top 3\u20135.<\/li>\n<li><strong>Skipping acceptance criteria:<\/strong> A story without testable outcomes is a liability. Always ask: \u201cHow will we know this is done?\u201d<\/li>\n<li><strong>Ignoring feedback loops:<\/strong> If stories keep getting pulled into sprints unready, revisit your Definition of Ready.<\/li>\n<\/ul>\n<p>Refinement is not a checklist. It\u2019s a conversation. If you\u2019re not asking clarifying questions, you\u2019re not refining\u2014you\u2019re just renaming.<\/p>\n<h2>How to Establish a Sustainable Refinement Cadence Agile<\/h2>\n<p>Start small. Choose one model. Test it for two sprints. Then reflect:<\/p>\n<ol>\n<li>Did the team feel the sessions were valuable?<\/li>\n<li>Were stories ready by sprint planning?<\/li>\n<li>Did velocity improve or stabilize?<\/li>\n<li>Did rework decrease?<\/li>\n<\/ol>\n<p>Adjust as needed. But never abandon the cadence entirely. Even if it\u2019s just 15 minutes a week, consistency builds trust.<\/p>\n<p>Remember: refinement isn\u2019t about finishing work\u2014it\u2019s about creating clarity. When refinement becomes a ritual, not a chore, the backlog starts to breathe.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the ideal length for a refinement session?<\/h3>\n<p>30 to 45 minutes is optimal. Too short, and you can\u2019t make meaningful progress. Too long, and focus drops. Keep it tight. Time-box it like sprint planning.<\/p>\n<h3>Can we refine stories in parallel across teams?<\/h3>\n<p>Yes\u2014but only if each team has its own cadence and ownership. Cross-team story alignment should happen during backlog refinement syncs, not during their individual sessions.<\/p>\n<h3>How do we handle refinement when the Product Owner is busy?<\/h3>\n<p>Refinement isn\u2019t their sole responsibility. Even if they\u2019re unavailable, the team can still refine stories using existing user research, previous feedback, and design artifacts. The key is to ensure they review the output before sprint planning.<\/p>\n<h3>Should refinement happen before or after sprint planning?<\/h3>\n<p>Typically after sprint planning\u2014because planning sets the sprint goal. But refinement should be continuous: start refining for the next sprint during the current one.<\/p>\n<h3>How often should we revisit stories we\u2019ve already refined?<\/h3>\n<p>Revisit stories if context changes, new risks emerge, or new user feedback arrives. A story should be re-refined only if its understanding or purpose has evolved.<\/p>\n<h3>What if my team doesn\u2019t agree on story size during refinement?<\/h3>\n<p>Use the team\u2019s agreed-upon story size framework. If disagreement persists, split the story into smaller pieces or use spike stories to explore. The goal isn\u2019t consensus on size\u2014it\u2019s clarity on scope.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a team says they&#8217;re &#8222;refining the backlog&#8221; but the work feels chaotic, like someone\u2019s rearranging a garage without a system\u2014this is refinement inconsistency. I\u2019ve seen teams skip it for weeks, then try to cram three sprints\u2019 worth of prep into a single session. The result? Half-baked stories, rushed estimates, and sprint zero surprises. Refinement [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":688,"menu_order":2,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-691","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>Fixing Refinement Inconsistency in Agile<\/title>\n<meta name=\"description\" content=\"Resolve refinement inconsistency in Agile with proven backlog grooming patterns and a sustainable refinement cadence agile. Boost team rhythm and story quality through consistent practices.\" \/>\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\/refinement-inconsistency-agile\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Fixing Refinement Inconsistency in Agile\" \/>\n<meta property=\"og:description\" content=\"Resolve refinement inconsistency in Agile with proven backlog grooming patterns and a sustainable refinement cadence agile. Boost team rhythm and story quality through consistent practices.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\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\/refinement-inconsistency-agile\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/\",\"name\":\"Fixing Refinement Inconsistency in Agile\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:22:50+00:00\",\"description\":\"Resolve refinement inconsistency in Agile with proven backlog grooming patterns and a sustainable refinement cadence agile. Boost team rhythm and story quality through consistent practices.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/#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\/refinement-inconsistency-agile\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/#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\":\"Inconsistent Refinement Practices\"}]},{\"@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":"Fixing Refinement Inconsistency in Agile","description":"Resolve refinement inconsistency in Agile with proven backlog grooming patterns and a sustainable refinement cadence agile. Boost team rhythm and story quality through consistent practices.","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\/refinement-inconsistency-agile\/","og_locale":"pl_PL","og_type":"article","og_title":"Fixing Refinement Inconsistency in Agile","og_description":"Resolve refinement inconsistency in Agile with proven backlog grooming patterns and a sustainable refinement cadence agile. Boost team rhythm and story quality through consistent practices.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/","og_site_name":"Visual Paradigm Skills Polski","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\/refinement-inconsistency-agile\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/","name":"Fixing Refinement Inconsistency in Agile","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:22:50+00:00","description":"Resolve refinement inconsistency in Agile with proven backlog grooming patterns and a sustainable refinement cadence agile. Boost team rhythm and story quality through consistent practices.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/#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\/refinement-inconsistency-agile\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/common-mistakes-in-writing-user-stories\/scaling-and-lifecycle-issues\/refinement-inconsistency-agile\/#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":"Inconsistent Refinement Practices"}]},{"@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\/691","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":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/691\/revisions"}],"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=691"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=691"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}