{"id":1108,"date":"2026-02-25T10:35:58","date_gmt":"2026-02-25T10:35:58","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/"},"modified":"2026-03-02T09:21:13","modified_gmt":"2026-03-02T09:21:13","slug":"user-story-estimation-confidence","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/","title":{"rendered":"Estimating User Stories with Confidence"},"content":{"rendered":"

Estimation isn\u2019t about guessing\u2014when done right, it\u2019s a disciplined act of collective judgment that builds trust across the team. I\u2019ve seen teams skip estimation entirely, only to face chaotic sprints and missed commitments. Others try to force precision, treating story points as literal hours. The real breakthrough comes when estimation becomes a conversation, not a deadline.<\/p>\n

What shifts everything is understanding that story points reflect complexity, effort, and risk\u2014not time. This lets teams focus on relative sizing, which reduces cognitive bias and fosters collaboration. In this chapter, you\u2019ll learn how to apply planning poker agile, Fibonacci sequences, and t-shirt sizing to improve forecasting and align expectations. You\u2019ll walk away with a framework that turns estimation from a burden into a shared insight engine.<\/p>\n

Why Story Points Are More Than Numbers<\/h2>\n

Story points aren\u2019t a measure of time\u2014they\u2019re a proxy for effort, complexity, and uncertainty. A story rated at 5 points isn\u2019t \u201cfive hours.\u201d It\u2019s a signal that the work involves multiple unknowns, dependencies, or technical debt.<\/p>\n

Teams often misunderstand this early on. They\u2019ll ask, \u201cHow many hours will this take?\u201d\u2014but that\u2019s the wrong question. The better question is: \u201cHow much effort does this require, relative to other stories?\u201d<\/p>\n

When estimating, we\u2019re not predicting the future. We\u2019re calibrating our shared understanding. The goal isn\u2019t perfection\u2014it\u2019s consistency.<\/p>\n

How Story Points Reflect Team Context<\/h3>\n

Every team\u2019s scale is unique. A 3-point story for one team might be a 5 for another, based on velocity, expertise, and tooling. That\u2019s why estimation should always be done by the team that will deliver the work.<\/p>\n

Using story points helps avoid the trap of \u201ctime-based estimation,\u201d where one person\u2019s guess becomes a commitment. Instead, we use relative sizing to maintain alignment and reduce emotional pressure.<\/p>\n

Planning Poker Agile: A Conversation, Not a Vote<\/h2>\n

Planning poker agile is more than a game\u2014it\u2019s a structured way to surface disagreements, clarify assumptions, and build shared ownership.<\/p>\n

Here\u2019s how it works:<\/p>\n

    \n
  1. One story is read aloud by the product owner.<\/li>\n
  2. Team members privately select a card representing their estimate.<\/li>\n
  3. All cards are revealed at once.<\/li>\n
  4. If estimates vary, the highest and lowest explain their reasoning.<\/li>\n
  5. Repeat until consensus is reached.<\/li>\n<\/ol>\n

    Disagreements aren\u2019t failures\u2014they\u2019re opportunities. When a junior developer estimates a 5 and a senior says 2, the conversation reveals risk, knowledge gaps, or hidden complexity.<\/p>\n

    My advice: never let planning poker become a ritual. If the team\u2019s discussion is shallow, revisit the acceptance criteria. If the same story keeps getting debated, it\u2019s not ready.<\/p>\n

    When Planning Poker Fails\u2014and How to Fix It<\/h3>\n

    Planning poker fails when teams rush, lack shared context, or the story is vague. I\u2019ve seen teams lose 20 minutes debating a 3 vs 5 when the real issue was missing acceptance criteria.<\/p>\n

    Fix it by pausing and asking: \u201cWhat does success look like?\u201d If the answer isn’t clear, don\u2019t estimate. Go back to refinement.<\/p>\n

    Choosing the Right Scale: Fibonacci, T-Shirt Sizing, and Beyond<\/h2>\n

    Most teams use the Fibonacci sequence: 1, 2, 3, 5, 8, 13, 21. It reflects the increasing uncertainty as stories grow larger. But a 21-point story is not just twice as hard as an 8-point one\u2014it\u2019s significantly more complex.<\/p>\n

    Yet not all teams need Fibonacci. Some prefer t-shirt sizing\u2014S, M, L, XL\u2014which works well for high-level planning or when stories are still in flux.<\/p>\n

    Comparing Estimation Methods<\/h3>\n\n\n\n\n\n\n
    Method<\/th>\nBest For<\/th>\nPros<\/th>\nCons<\/th>\n<\/tr>\n
    Fibonacci (1, 2, 3, 5, 8, 13)<\/td>\nTeam-level estimation<\/td>\nReflects growing uncertainty; clear scale<\/td>\nSteeper learning curve; hard to use for very small stories<\/td>\n<\/tr>\n
    T-shirt Sizing (S, M, L, XL)<\/td>\nEpics, discovery sprints, planning workshops<\/td>\nSimple to understand; fast for large-scale prioritization<\/td>\nLacks granularity; not ideal for sprint planning<\/td>\n<\/tr>\n
    Modified Fibonacci (0, \u00bd, 1, 2, 3, 5, 8, 13, 20, 40)<\/td>\nTeams needing flexibility<\/td>\nIncludes \u00bd for small estimates; avoids \u201crounding up\u201d bias<\/td>\nRequires team buy-in<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    My recommendation: start with Fibonacci. If your team finds it too rigid, try modified Fibonacci or t-shirt sizing for discovery phases. But don\u2019t switch just for the sake of novelty.<\/p>\n

    Building Trust Through Consistent Estimation<\/h2>\n

    Estimation becomes meaningful only when it\u2019s consistent over time. A team that estimates poorly may not be wrong\u2014they may just need more calibration.<\/p>\n

    Use sprint retrospectives to review estimation accuracy. Ask:<\/p>\n

      \n
    • Did we complete what we committed to?<\/li>\n
    • Were our estimates realistic?<\/li>\n
    • What stories were underestimated or overestimated?<\/li>\n<\/ul>\n

      When you compare actual effort to story points across multiple sprints, you\u2019ll see patterns. A team averaging 25 points per sprint doesn\u2019t mean every story is \u201c25 points.\u201d It means they\u2019re good at sizing relative to their own history.<\/p>\n

      How to Calibrate Your Team\u2019s Estimation<\/h3>\n

      Every few sprints, do a quick calibration session:<\/p>\n

        \n
      1. Select 3\u20135 previously completed stories.<\/li>\n
      2. Re-estimate them in silence.<\/li>\n
      3. Compare old vs. new estimates.<\/li>\n
      4. Discuss why differences occurred.<\/li>\n<\/ol>\n

        This isn\u2019t about correcting the past\u2014it\u2019s about improving future judgment.<\/p>\n

        Common Pitfalls and How to Avoid Them<\/h2>\n

        1. Estimating Too Early<\/h3>\n

        Estimating before the story is refined leads to low accuracy. If the acceptance criteria are unclear or the story is too broad, estimation is just guesswork.<\/p>\n

        Fix: Only estimate stories in the Definition of Ready. If not, send it back for refinement.<\/p>\n

        2. Letting One Person Drive the Estimate<\/h3>\n

        Even in a team of experts, the person with the loudest voice can dominate. I\u2019ve seen teams where the tech lead always says \u201c3\u201d and everyone else agrees\u2014even if they disagree.<\/p>\n

        Fix: Use planning poker agile to hide estimates until everyone reveals. Encourage junior members to speak first.<\/p>\n

        3. Confusing Estimation with Prioritization<\/h3>\n

        Just because a story is small doesn\u2019t mean it\u2019s valuable. A 2-point story might be a technical refactoring that enables future work.<\/p>\n

        Fix: Separate estimation from prioritization. Use story points for effort. Use impact, value, and risk for ordering.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        What if my team can\u2019t agree on story points?<\/h3>\n

        Disagreement is normal. Use planning poker agile to surface the root cause. Ask: \u201cWhat makes this harder or easier than the last story?\u201d If the team still can\u2019t reach consensus, split the story or defer until more information is available.<\/p>\n

        How do I estimate stories that involve external dependencies?<\/h3>\n

        Estimate based on the team\u2019s ability to control the work. If a story depends on an external API that\u2019s unstable, add a risk buffer. Tag it as “pending” until the dependency is confirmed. Avoid inflating story points just because the work is delayed.<\/p>\n

        Can we use story points for non-functional requirements?<\/h3>\n

        Absolutely. Stories like \u201cAs a user, I want the login to respond within 2 seconds\u201d can be estimated. But be clear about the criteria\u2014speed, scalability, or security are all factors in complexity. Involve the right people (e.g., devops, QA) in the estimate.<\/p>\n

        Should we re-estimate stories in later sprints?<\/h3>\n

        Only if the story has changed significantly. Re-estimation is rare and should be done with the whole team. If the story is still in progress, don\u2019t re-estimate unless new risks emerge.<\/p>\n

        How do story points relate to velocity?<\/h3>\n

        Velocity is the sum of story points completed per sprint. It\u2019s a team metric\u2014not a target. Use it to forecast capacity, not to pressure teams. A stable velocity means the team can plan with confidence.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Estimation isn\u2019t about guessing\u2014when done right, it\u2019s a disciplined act of collective judgment that builds trust across the team. I\u2019ve seen teams skip estimation entirely, only to face chaotic sprints and missed commitments. Others try to force precision, treating story points as literal hours. The real breakthrough comes when estimation becomes a conversation, not a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1102,"menu_order":5,"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-1108","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nUser Story Estimation: Confidence in Agile Planning<\/title>\n<meta name=\"description\" content=\"Master user story estimation with proven methods like planning poker agile, story points, and t-shirt sizing. Improve forecasting and team alignment in Agile projects with practical guidance from an experienced practitioner.\" \/>\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\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/\" \/>\n<meta property=\"og:locale\" content=\"pt_PT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"User Story Estimation: Confidence in Agile Planning\" \/>\n<meta property=\"og:description\" content=\"Master user story estimation with proven methods like planning poker agile, story points, and t-shirt sizing. Improve forecasting and team alignment in Agile projects with practical guidance from an experienced practitioner.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Portugu\u00eas\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:21:13+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Tempo estimado de leitura\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/\",\"name\":\"User Story Estimation: Confidence in Agile Planning\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\"},\"datePublished\":\"2026-02-25T10:35:58+00:00\",\"dateModified\":\"2026-03-02T09:21:13+00:00\",\"description\":\"Master user story estimation with proven methods like planning poker agile, story points, and t-shirt sizing. Improve forecasting and team alignment in Agile projects with practical guidance from an experienced practitioner.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/#breadcrumb\"},\"inLanguage\":\"pt-PT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Write Effective User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Refinement, Slicing, and Collaboration\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Estimating User Stories with Confidence\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-PT\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#organization\",\"name\":\"Visual Paradigm Skills Portugu\u00eas\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-PT\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Portugu\u00eas\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"User Story Estimation: Confidence in Agile Planning","description":"Master user story estimation with proven methods like planning poker agile, story points, and t-shirt sizing. Improve forecasting and team alignment in Agile projects with practical guidance from an experienced practitioner.","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\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/","og_locale":"pt_PT","og_type":"article","og_title":"User Story Estimation: Confidence in Agile Planning","og_description":"Master user story estimation with proven methods like planning poker agile, story points, and t-shirt sizing. Improve forecasting and team alignment in Agile projects with practical guidance from an experienced practitioner.","og_url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/","og_site_name":"Visual Paradigm Skills Portugu\u00eas","article_modified_time":"2026-03-02T09:21:13+00:00","twitter_card":"summary_large_image","twitter_misc":{"Tempo estimado de leitura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/","name":"User Story Estimation: Confidence in Agile Planning","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website"},"datePublished":"2026-02-25T10:35:58+00:00","dateModified":"2026-03-02T09:21:13+00:00","description":"Master user story estimation with proven methods like planning poker agile, story points, and t-shirt sizing. Improve forecasting and team alignment in Agile projects with practical guidance from an experienced practitioner.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/#breadcrumb"},"inLanguage":"pt-PT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/user-story-estimation-confidence\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pt\/"},{"@type":"ListItem","position":2,"name":"How to Write Effective User Stories","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/"},{"@type":"ListItem","position":3,"name":"Refinement, Slicing, and Collaboration","item":"https:\/\/skills.visual-paradigm.com\/pt\/docs\/how-to-write-effective-user-stories\/refinement-slicing-collaboration\/"},{"@type":"ListItem","position":4,"name":"Estimating User Stories with Confidence"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#website","url":"https:\/\/skills.visual-paradigm.com\/pt\/","name":"Visual Paradigm Skills Portugu\u00eas","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pt\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-PT"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#organization","name":"Visual Paradigm Skills Portugu\u00eas","url":"https:\/\/skills.visual-paradigm.com\/pt\/","logo":{"@type":"ImageObject","inLanguage":"pt-PT","@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pt\/wp-content\/uploads\/sites\/9\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Portugu\u00eas"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pt\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1108","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1108\/revisions"}],"predecessor-version":[{"id":2463,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1108\/revisions\/2463"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/docs\/1102"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/media?parent=1108"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pt\/wp-json\/wp\/v2\/doc_tag?post=1108"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}