{"id":1103,"date":"2026-02-25T10:35:57","date_gmt":"2026-02-25T10:35:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/"},"modified":"2026-02-25T10:35:57","modified_gmt":"2026-02-25T10:35:57","slug":"refining-user-stories-continuous-practice","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/","title":{"rendered":"Refinement as a Continuous Practice"},"content":{"rendered":"<p>Refining user stories isn\u2019t a one-time task. It\u2019s a rhythm that keeps your backlog alive, relevant, and aligned with customer needs.<\/p>\n<p>When stories sit idle, they lose clarity. Ambiguity creeps in. What once felt intuitive becomes a guessing game. That\u2019s where continuous refinement steps in\u2014not as a sprint-only ritual, but as a daily practice.<\/p>\n<p>I\u2019ve seen teams rush into sprints with poorly shaped stories. The result? Last-minute changes, rework, and frustration. The fix isn\u2019t more documentation\u2014it\u2019s better collaboration.<\/p>\n<p>Over two decades in Agile product delivery taught me: refining user stories is less about formatting and more about maintaining shared understanding. It\u2019s the process of making stories understandable, testable, and ready to deliver\u2014before the sprint even starts.<\/p>\n<p>This chapter walks through how to embed refinement into your workflow, not as an extra burden, but as the engine of agility. You\u2019ll learn what to prioritize, how to avoid common pitfalls, and how to make every story count.<\/p>\n<h2>Why Refinement Must Be Continuous<\/h2>\n<p>Refinement isn\u2019t a checklist. It\u2019s a mindset.<\/p>\n<p>Too often, teams treat backlog grooming as a fixed event\u2014once a week, a 90-minute meeting, done. But user needs shift. Market feedback arrives. Technical debt surfaces. A story that was clear yesterday may be obsolete today.<\/p>\n<p>Continuous refinement means revisiting stories regularly\u2014daily, if needed\u2014especially those in play or near the top of the backlog.<\/p>\n<p>It\u2019s not about making every story perfect. It\u2019s about ensuring no story gets deployed without being understood by the team.<\/p>\n<p>Here\u2019s my rule: if a story isn\u2019t clear to the developer, tester, and product owner, it\u2019s not ready. That\u2019s the bar. Refinement keeps us honest.<\/p>\n<h3>When to Refine: Timing and Triggers<\/h3>\n<p>Refinement doesn\u2019t need to wait for a sprint planning meeting. It happens whenever context changes.<\/p>\n<p>Common triggers include:<\/p>\n<ul>\n<li>New feedback from user testing or support tickets<\/li>\n<li>Technical discoveries that impact feasibility<\/li>\n<li>Shifts in business priorities or roadmap<\/li>\n<li>Discovery of incomplete acceptance criteria during development<\/li>\n<li>Backlog items nearing the top but lacking clarity<\/li>\n<\/ul>\n<p>Think of refinement as maintenance\u2014like tuning a car engine. You don\u2019t wait until it breaks. You adjust it regularly.<\/p>\n<p>At my last client, a fintech startup, we discovered that 70% of story rework came from poorly understood requirements. After instituting continuous refinement, that dropped to under 15% in six months.<\/p>\n<h2>Backlog Refinement Best Practices<\/h2>\n<p>Refining user stories isn\u2019t magic. It\u2019s discipline. Here are the non-negotiables I\u2019ve seen work in real teams:<\/p>\n<ol>\n<li><strong>Keep stories small and focused.<\/strong> If a story needs more than a few hours of work, it\u2019s too big. Split it.<\/li>\n<li><strong>Define \u201cready\u201d clearly.<\/strong> A story isn\u2019t ready until it has acceptance criteria, a clear value statement, and no unknowns.<\/li>\n<li><strong>Involve the whole team.<\/strong> Developers, testers, UX\u2014everyone brings a different lens. The story improves when all voices are heard.<\/li>\n<li><strong>Use estimation as a signal, not a goal.<\/strong> Story points help prioritize, but don\u2019t let them become a proxy for quality.<\/li>\n<li><strong>Revisit old stories regularly.<\/strong> If a story hasn\u2019t been touched in weeks, it might be stale or outdated.<\/li>\n<\/ol>\n<p>These aren\u2019t rules. They\u2019re guardrails. They keep refinement from becoming a chore or a side project.<\/p>\n<h3>Refinement vs. Grooming: A Clarification<\/h3>\n<p>\u201cBacklog grooming\u201d is a term I still hear. But it\u2019s misleading. Grooming implies polishing an old artifact. Refinement is about evolution.<\/p>\n<p>Refinement is active, iterative, and collaborative. It\u2019s not about fixing broken stories. It\u2019s about building shared understanding as the product evolves.<\/p>\n<p>Teams that treat refinement as an ongoing conversation, not a meeting, are the ones who ship faster and with fewer defects.<\/p>\n<h2>How to Run Effective Refinement Sessions<\/h2>\n<p>Even with the best intentions, refinement can go off track. Here\u2019s how to keep it focused and productive.<\/p>\n<p>Set a consistent time\u201415\u201330 minutes per day, or 60 minutes weekly. Keep it small. Invite only those who need to be there.<\/p>\n<p>Start with one story. Ask three questions:<\/p>\n<ul>\n<li>What\u2019s the user trying to achieve?<\/li>\n<li>What does \u201cdone\u201d look like?<\/li>\n<li>What risks or unknowns remain?<\/li>\n<\/ul>\n<p>Answering these in real time clears ambiguity. It\u2019s not about perfection\u2014it\u2019s about progress.<\/p>\n<p>Use visual aids. A simple whiteboard, sticky notes, or a shared digital board helps teams see the story\u2019s shape, dependencies, and complexity.<\/p>\n<p>Here\u2019s a real example: A health tech team was struggling with a story about \u201csecure data sharing.\u201d The conversation revealed that \u201csecure\u201d meant different things to compliance, engineering, and UX. By refining the story together\u2014adding specific acceptance criteria like \u201cdata must be encrypted in transit and at rest\u201d\u2014the team avoided a major rework later.<\/p>\n<h3>Common Pitfalls to Avoid<\/h3>\n<p>Even with good intentions, refinement can fail. Watch out for:<\/p>\n<ul>\n<li><strong>Over-documenting.<\/strong> A story with 50 lines of text is a red flag. If you\u2019re writing paragraphs, you\u2019re not writing a story.<\/li>\n<li><strong>Letting one person dominate.<\/strong> The PO shouldn\u2019t monopolize the conversation. Refinement is a team effort.<\/li>\n<li><strong>Skipping acceptance criteria.<\/strong> No criteria = no testability. No testability = no confidence.<\/li>\n<li><strong>Refining without context.<\/strong> A story without a user persona or business goal becomes abstract and forgettable.<\/li>\n<\/ul>\n<p>Every story should answer: Who benefits? How? Why now?<\/p>\n<h2>Measuring the Impact of Refinement<\/h2>\n<p>You can\u2019t improve what you don\u2019t measure. But don\u2019t fall into the trap of tracking refinement hours.<\/p>\n<p>Focus on outcomes, not effort. Track:<\/p>\n<ul>\n<li>Number of stories that were rejected due to poor clarity<\/li>\n<li>Stories that were reworked or delayed due to ambiguity<\/li>\n<li>Time saved in sprint planning due to better-prepared stories<\/li>\n<li>Team satisfaction with backlog clarity (via retrospectives)<\/li>\n<\/ul>\n<p>Use this data to refine your refinement.<\/p>\n<p>At one company, we introduced a \u201cclarity score\u201d for each story\u2014rated 1\u20135 by the team. After three months, the average jumped from 2.8 to 4.3. That meant less time spent in sprint planning and more time building.<\/p>\n<h2>Refinement Checklist: Daily, Weekly, and Long-Term<\/h2>\n<p>Use this checklist to audit your refinement process.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Frequency<\/th>\n<th>Check<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Daily<\/td>\n<td>Review top 3 backlog stories<\/td>\n<td>Prevents overload and maintains relevance<\/td>\n<\/tr>\n<tr>\n<td>Weekly<\/td>\n<td>Run a 30-minute refinement session<\/td>\n<td>Reinforces collaboration and clarity<\/td>\n<\/tr>\n<tr>\n<td>Monthly<\/td>\n<td>Re-evaluate acceptance criteria standards<\/td>\n<td>Ensures consistency across stories<\/td>\n<\/tr>\n<tr>\n<td>Quarterly<\/td>\n<td>Assess team\u2019s story quality<\/td>\n<td>Identifies gaps in understanding or process<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Adjust this based on team size, complexity, and delivery cadence. But keep the rhythm.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>How often should we refine user stories?<\/h3>\n<p>Daily refinement is ideal. Even 15 minutes a day keeps stories sharp. For larger teams, dedicate 60 minutes per week in a focused session.<\/p>\n<h3>Who should attend a refinement session?<\/h3>\n<p>Include the Product Owner, Developers, Testers, and UX if the story impacts design. Invite others only if they add unique context.<\/p>\n<h3>What if a story can\u2019t be refined further?<\/h3>\n<p>If a story is still unclear, it\u2019s not ready. Put it back in the backlog and revisit only when context improves. Don\u2019t force it.<\/p>\n<h3>Does refining user stories replace estimation?<\/h3>\n<p>No. Estimation happens after refinement. A story must be clear enough to estimate. Refinement enables estimation, not the other way around.<\/p>\n<h3>Should we refine stories in sprint planning?<\/h3>\n<p>Only if necessary. The goal is to have stories ready before sprint planning. If you\u2019re refining during planning, it\u2019s a sign your process is behind.<\/p>\n<h3>How do we know when a story is \u201crefined\u201d enough?<\/h3>\n<p>A story is ready when: the value is clear, acceptance criteria are defined, dependencies are known, and no one has questions. Use the Definition of Ready (DoR) as your guide.<\/p>\n<p>Refining user stories is not a phase. It\u2019s the heartbeat of a healthy product backlog.<\/p>\n<p>When done right, refinement transforms stories from vague ideas into actionable work. It builds trust, reduces uncertainty, and ensures teams don\u2019t waste time on what doesn\u2019t matter.<\/p>\n<p>Start small. Be consistent. Listen more than you speak.<\/p>\n<p>And remember: a user story is a promise to talk. Refinement keeps that promise alive.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Refining user stories isn\u2019t a one-time task. It\u2019s a rhythm that keeps your backlog alive, relevant, and aligned with customer needs. When stories sit idle, they lose clarity. Ambiguity creeps in. What once felt intuitive becomes a guessing game. That\u2019s where continuous refinement steps in\u2014not as a sprint-only ritual, but as a daily practice. I\u2019ve [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1102,"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":"","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-1103","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>Refining User Stories for Agile Success<\/title>\n<meta name=\"description\" content=\"Master the art of backlog refinement best practices to keep user stories clear, valuable, and sprint-ready. Learn how continuous refinement drives Agile delivery success.\" \/>\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\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Refining User Stories for Agile Success\" \/>\n<meta property=\"og:description\" content=\"Master the art of backlog refinement best practices to keep user stories clear, valuable, and sprint-ready. Learn how continuous refinement drives Agile delivery success.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tiempo de lectura\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/\",\"name\":\"Refining User Stories for Agile Success\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:35:57+00:00\",\"description\":\"Master the art of backlog refinement best practices to keep user stories clear, valuable, and sprint-ready. Learn how continuous refinement drives Agile delivery success.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Refinement, Slicing, and Collaboration\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Refinement as a Continuous Practice\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"es\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#organization\",\"name\":\"Visual Paradigm Skills Espa\u00f1ol\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"es\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Espa\u00f1ol\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Refining User Stories for Agile Success","description":"Master the art of backlog refinement best practices to keep user stories clear, valuable, and sprint-ready. Learn how continuous refinement drives Agile delivery success.","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\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/","og_locale":"es_ES","og_type":"article","og_title":"Refining User Stories for Agile Success","og_description":"Master the art of backlog refinement best practices to keep user stories clear, valuable, and sprint-ready. Learn how continuous refinement drives Agile delivery success.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"7 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/","name":"Refining User Stories for Agile Success","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:35:57+00:00","description":"Master the art of backlog refinement best practices to keep user stories clear, valuable, and sprint-ready. Learn how continuous refinement drives Agile delivery success.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/refining-user-stories-continuous-practice\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Refinement, Slicing, and Collaboration","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/"},{"@type":"ListItem","position":4,"name":"Refinement as a Continuous Practice"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/es\/#website","url":"https:\/\/skills.visual-paradigm.com\/es\/","name":"Visual Paradigm Skills Espa\u00f1ol","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/es\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"es"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/es\/#organization","name":"Visual Paradigm Skills Espa\u00f1ol","url":"https:\/\/skills.visual-paradigm.com\/es\/","logo":{"@type":"ImageObject","inLanguage":"es","@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/es\/wp-content\/uploads\/sites\/5\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Espa\u00f1ol"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1103\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1102"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=1103"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=1103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}