{"id":705,"date":"2026-02-25T10:22:57","date_gmt":"2026-02-25T10:22:57","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/"},"modified":"2026-02-25T10:22:57","modified_gmt":"2026-02-25T10:22:57","slug":"user-story-quality-metrics","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/","title":{"rendered":"Integrating Story Quality Metrics into Agile Practice"},"content":{"rendered":"

Most teams start by writing stories, then debate acceptance criteria\u2014only to find themselves rewriting or reworking the same items in subsequent sprints. The real breakthrough isn\u2019t in crafting better stories, but in tracking how well they hold up across cycles. I\u2019ve seen teams improve story clarity by 40% not through training, but by simply measuring acceptance outcomes over time. That\u2019s where user story quality metrics come in.<\/p>\n

Too many teams treat story quality as a subjective judgment. But in practice, it\u2019s not. It\u2019s measurable. It\u2019s observable. It\u2019s tied directly to delivery outcomes. This chapter walks through how to apply, interpret, and act on three key agile story metrics: acceptance success rate, rework ratio, and clarity score\u2014each grounded in real-world sprint data.<\/p>\n

You\u2019ll learn how to stop guessing whether a story was \u201cclear\u201d and start knowing it with data. You\u2019ll also see how tracking story acceptance rate helps identify persistent ambiguity, even when the team thinks they\u2019re aligned.<\/p>\n

Why Metrics Matter Where Stories Are Born<\/h2>\n

Stories are built during refinement. But refinement isn’t a quality control step\u2014it\u2019s a performance amplifier. If you don\u2019t measure how well stories perform in sprint execution, you\u2019re optimizing for process, not value.<\/p>\n

My first insight? A story isn\u2019t \u201cdone\u201d when it\u2019s in the sprint. It\u2019s only done when it\u2019s accepted. And that\u2019s where metrics start.<\/p>\n

Here\u2019s what I\u2019ve learned from 150+ retrospectives: teams that measure story acceptance rate see a 25\u201335% drop in rework within six months\u2014not because stories are rewritten, but because the team starts probing vague language before sprint entry.<\/p>\n

Three Foundational Metrics for Agile Story Quality<\/h3>\n

Let\u2019s break down the three metrics that serve as the backbone of story quality tracking.<\/p>\n

1. Story Acceptance Rate<\/h4>\n

This is the percentage of stories that pass acceptance testing in the sprint they\u2019re delivered. A story is accepted only if all acceptance criteria are met and verified by the product owner.<\/p>\n

Example: 12 out of 15 stories in Sprint 7 passed. Acceptance rate = 80%.<\/p>\n

Why it matters: A consistent rate below 70% signals that stories are too vague or ambiguous. The team is spending too much time rewriting or fixing after sprint start.<\/p>\n

Red flag: Frequent rework on the same type of story (e.g., \u201cUser can filter results\u201d) suggests a framing problem\u2014not a coding one.<\/p>\n

2. Rework Ratio<\/h4>\n

This measures the number of times a story is revised after initial definition. It\u2019s calculated as:<\/p>\n

Rework Ratio = (Number of story revisions after refinement) \/ (Total number of stories in sprint)<\/code><\/pre>\n
A ratio above 25% is a warning. Above 40% indicates systemic issues in clarity or team understanding.<\/p>\n
I once worked with a team whose rework ratio hovered near 60%. The root cause? No shared understanding of \u201cfast\u201d or \u201csecure\u201d in the acceptance criteria. They weren\u2019t lazy\u2014they were ambiguous.<\/p>\n
3. Clarity Score (Subjective, but Measurable)<\/h4>\n
This is a team-driven rating (1\u20135) of story clarity assigned during refinement. It\u2019s based on:<\/p>\n
    \n
  • Is the actor clear? (Yes\/No)<\/li>\n
  • Is the goal tied to user value? (Yes\/No)<\/li>\n
  • Are acceptance criteria testable? (Yes\/No)<\/li>\n
  • Is there a dependency risk? (Yes\/No)<\/li>\n<\/ul>\n
    This score isn\u2019t for reporting\u2014it\u2019s for reflection. Track it per sprint. If the average drops below 3.5, revisit your refinement process.<\/p>\n
    How to Measure and Act: A Four-Step Framework<\/h2>\n
    Don\u2019t collect data for its own sake. Use it to improve.<\/p>\n
      \n
    1. Track weekly<\/strong>: At the end of each sprint, log acceptance rate, rework count, and clarity score per story.<\/li>\n
    2. Review monthly<\/strong>: Plot trends. Use a simple table like this:<\/li>\n<\/ol>\n\n\n\n\n\n\n
      Sprint<\/th>\nAcceptance Rate<\/th>\nRework Ratio<\/th>\nAvg Clarity Score<\/th>\n<\/tr>\n
      Sprint 7<\/td>\n80%<\/td>\n22%<\/td>\n3.8<\/td>\n<\/tr>\n
      Sprint 8<\/td>\n72%<\/td>\n38%<\/td>\n3.2<\/td>\n<\/tr>\n
      Sprint 9<\/td>\n88%<\/td>\n18%<\/td>\n4.1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
      Now ask: What changed between Sprint 8 and 9? The team introduced a 5-minute \u201cclarity check\u201d rule during refinement. No more vague statements like \u201cthe system responds quickly.\u201d Instead: \u201cresponse time under 1.5 seconds.\u201d<\/p>\n
        \n
      1. Diagnose the root cause<\/strong>: If acceptance rate drops, ask: Was the story too broad? Was the acceptance criteria missing? Did the team lack context?<\/li>\n
      2. Act on insight<\/strong>: Run a 15-minute \u201cstory clinic\u201d after each sprint to improve one pattern\u2014e.g., always link acceptance criteria to a user goal.<\/li>\n<\/ol>\n
        Real Example: Fixing Ambiguity in Feature Requests<\/h3>\n
        A healthcare app team kept failing on user authentication stories. Their acceptance rate was stuck at 62%. Re-work ratio was 50%. Clarity score: 2.9.<\/p>\n
        They discovered: \u201cSecure login\u201d meant different things to the PM, Dev, and QA. No shared definition.<\/p>\n
        Fix: They wrote a new acceptance criterion:<\/p>\n
        Given a user attempts to log in with invalid credentials\nWhen they submit the form\nThen the system blocks access for 60 seconds\nAnd displays a message: \"Too many failed attempts. Try again in 60 seconds.\"<\/code><\/pre>\n
        After this change, acceptance rate jumped to 92%. Rework dropped to 12%. The story was no longer \u201cambiguous\u201d \u2014 it was testable, specific, and tied to user safety.<\/p>\n
        Common Pitfalls and How to Avoid Them<\/h2>\n
        Tracking metrics isn\u2019t about surveillance. It\u2019s about learning.<\/p>\n
          \n
        • Mistake: Measuring only acceptance rate<\/strong>
          \n      This ignores rework and clarity. A story can pass acceptance but still require rework due to design flaws or scope creep.<\/li>\n
        • Mistake: Blaming the developer<\/strong>
          \n      If stories keep failing, it\u2019s rarely the dev\u2019s fault. It\u2019s usually a shared understanding gap. Look at the story text, acceptance criteria, and refinement process\u2014not the individual.<\/li>\n
        • Mistake: Ignoring trend context<\/strong>
          \n      A 75% acceptance rate isn\u2019t bad\u2014but if it\u2019s dropping from 90%, the team needs help. Metrics are only meaningful when seen over time.<\/li>\n<\/ul>\n
          Final Thoughts: Metrics Are Conversations in Disguise<\/h2>\n
          User story quality metrics don\u2019t replace conversation. They make it better.<\/p>\n
          When you track story acceptance rate, you\u2019re not measuring performance\u2014you\u2019re revealing friction. When rework spikes, it\u2019s not a failure; it\u2019s a signal to improve clarity. When clarity scores drop, it\u2019s a sign the team needs a refresher on writing value-driven stories.<\/p>\n
          Agile story metrics are not about perfection. They\u2019re about progress. The goal isn\u2019t to get every story right the first time. It\u2019s to learn faster, adapt quicker, and deliver real value\u2014without unnecessary rework.<\/p>\n
          Start small. Pick one metric. Track it. Reflect. Improve. Then repeat.<\/p>\n
          Frequently Asked Questions<\/h2>\n
          How often should we measure user story quality metrics?<\/h3>\n
          Track acceptance rate and rework ratio at the end of every sprint. Clarity score can be reviewed weekly during refinement. Use monthly trends to guide process improvements.<\/p>\n
          What if our acceptance rate is low but the team says stories are fine?<\/h3>\n
          Low acceptance rate is a warning sign\u2014regardless of team sentiment. It means something in the story or acceptance criteria is unclear. Run a retrospective focused on one recurring story type. Ask: \u201cWhat was ambiguous?\u201d<\/p>\n
          Can agile story metrics replace story reviews?<\/h3>\n
          No. Metrics are indicators, not replacements for peer review. They highlight patterns, but only a human review can detect nuance, tone, or emotional alignment with user needs.<\/p>\n
          Does measuring rework ratio encourage blame culture?<\/h3>\n
          Not if framed correctly. Present rework as a team learning opportunity, not a performance score. Focus on \u201cwhy\u201d it happened\u2014not \u201cwho\u201d caused it. For example: \u201cWhy did this story require rework?\u201d<\/p>\n
          How do we handle stories that are split mid-sprint?<\/h3>\n
          Track them as one story for acceptance. If a story is split during sprint and only part is accepted, classify the outcome as \u201cpartial acceptance.\u201d Use this to flag stories that are too large or complex.<\/p>\n
          Should we share these metrics with stakeholders?<\/h3>\n
          Yes\u2014but with context. Show trends, not raw numbers. Example: \u201cOur acceptance rate improved by 18% over two sprints due to clearer acceptance criteria.\u201d This shows progress, not perfection.<\/p>\n","protected":false},"excerpt":{"rendered":"
          Most teams start by writing stories, then debate acceptance criteria\u2014only to find themselves rewriting or reworking the same items in subsequent sprints. The real breakthrough isn\u2019t in crafting better stories, but in tracking how well they hold up across cycles. I\u2019ve seen teams improve story clarity by 40% not through training, but by simply measuring […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":701,"menu_order":3,"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-705","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUser Story Quality Metrics<\/title>\n<meta name=\"description\" content=\"Measure and improve user story quality with actionable agile story metrics. Track acceptance success, rework, and clarity to boost team delivery efficiency and product value.\" \/>\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\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Quality Metrics\" \/>\n<meta property=\"og:description\" content=\"Measure and improve user story quality with actionable agile story metrics. Track acceptance success, rework, and clarity to boost team delivery efficiency and product value.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/\",\"name\":\"User Story Quality Metrics\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:22:57+00:00\",\"description\":\"Measure and improve user story quality with actionable agile story metrics. Track acceptance success, rework, and clarity to boost team delivery efficiency and product value.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Lessons Learned and Continuous Improvement\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Integrating Story Quality Metrics into Agile Practice\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Quality Metrics","description":"Measure and improve user story quality with actionable agile story metrics. Track acceptance success, rework, and clarity to boost team delivery efficiency and product value.","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\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/","og_locale":"fr_FR","og_type":"article","og_title":"User Story Quality Metrics","og_description":"Measure and improve user story quality with actionable agile story metrics. Track acceptance success, rework, and clarity to boost team delivery efficiency and product value.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/","name":"User Story Quality Metrics","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:22:57+00:00","description":"Measure and improve user story quality with actionable agile story metrics. Track acceptance success, rework, and clarity to boost team delivery efficiency and product value.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/user-story-quality-metrics\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Lessons Learned and Continuous Improvement","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/continuous-improvement-user-stories\/"},{"@type":"ListItem","position":4,"name":"Integrating Story Quality Metrics into Agile Practice"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/705","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/705\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/701"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=705"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}