{"id":1774,"date":"2026-02-25T10:46:01","date_gmt":"2026-02-25T10:46:01","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/"},"modified":"2026-03-02T09:21:45","modified_gmt":"2026-03-02T09:21:45","slug":"story-dependencies-agile-dependency-mapping","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/","title":{"rendered":"Visualizing Dependencies Among Backlogs"},"content":{"rendered":"

When teams operate in silos, even small dependencies can become invisible bottlenecks. I\u2019ve seen programs stall not from technical debt or scope creep, but from untracked story dependencies blooming across team backlogs. The root issue isn\u2019t complexity\u2014it\u2019s visibility. By shifting from reactive firefighting to proactive dependency mapping, you create a shared mental model that surfaces risks before they derail delivery.<\/p>\n

My experience over two decades has shown that story dependencies agile are not anomalies\u2014they\u2019re inevitable. The key isn\u2019t eliminating them, but mastering their visualization and management. In this chapter, you\u2019ll learn how to use visual modeling techniques to map dependencies across teams, ensuring coherence in value delivery and minimizing disruptions.<\/p>\n

What you\u2019ll gain: A repeatable, collaborative method to identify, document, and manage cross-team dependencies using real-world modeling tools and techniques. This approach supports predictable delivery, reduces rework, and strengthens alignment across multiple Agile teams.<\/p>\n

Why Silent Dependencies Break Agile Flow<\/h2>\n

Dependencies often go unnoticed until a team blocks another. A story in Team A might require an API endpoint built by Team B. If Team B delays, Team A\u2019s work stalls\u2014even if they’re fully ready.<\/p>\n

This isn\u2019t just a scheduling problem. It\u2019s a breakdown in shared understanding. Teams work in parallel, but their stories are connected by invisible threads. When these threads snap under pressure, the entire delivery pipeline suffers.<\/p>\n

Dependency mapping visual paradigm turns these hidden connections into visible, manageable signals. It\u2019s not about control\u2014it\u2019s about clarity.<\/p>\n

Mapping Dependencies: The Core Principles<\/h2>\n

Effective dependency mapping rests on three pillars: visibility, traceability, and ownership.<\/p>\n

Visibility means every dependency appears on a shared model. Traceability links each dependency to the actual stories involved. Ownership ensures accountability\u2014someone is responsible for tracking progress.<\/p>\n

Without these, mapping becomes a data dump. With them, it becomes a living artifact that evolves with the backlog.<\/p>\n

Start with the Story Map<\/h3>\n

Begin with your enterprise story map. It\u2019s not just a backlog\u2014it\u2019s a value flow diagram. Organize stories by user journey, then layer dependencies on top.<\/p>\n

Each story becomes a node. A line between two nodes indicates a dependency. Label it: \u00abTeam A \u2192 Team B: API must be ready by Sprint 5.\u00bb<\/p>\n

Use color coding: red for high-risk, yellow for medium, green for low. This allows quick scanning during PI planning or refinement.<\/p>\n

Use Dependency Types to Guide Actions<\/h3>\n

Not all dependencies are equal. Classify them to determine how you\u2019ll manage them.<\/p>\n\n\n\n\n\n\n\n
Dependency Type<\/th>\nDefinition<\/th>\nManagement Approach<\/th>\n<\/tr>\n
Technical<\/td>\nCode, API, or integration point<\/td>\nAlign with architecture team; define interface contracts early<\/td>\n<\/tr>\n
Functional<\/td>\nFeature requires input from another story<\/td>\nDefine acceptance criteria that include dependency status<\/td>\n<\/tr>\n
Resource<\/td>\nSame developer, tester, or environment needed<\/td>\nCoordinate capacity; avoid overcommitment<\/td>\n<\/tr>\n
Temporal<\/td>\nOne story must finish before another starts<\/td>\nUse dependency chains; schedule buffers<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Understanding the type helps you decide whether to rework the story, schedule a sync, or escalate.<\/p>\n

Tools That Make Dependency Mapping Practical<\/h2>\n

Manual diagrams fail at scale. You need a tool that supports real-time collaboration, versioning, and traceability.<\/p>\n

Visual Paradigm is one of the most effective tools for this. It allows you to:<\/p>\n

    \n
  • Create dependency matrices linked to your story artifacts<\/li>\n
  • Automatically generate dependency reports for PI planning<\/li>\n
  • Tag dependencies by risk level, owner, and due date<\/li>\n<\/ul>\n

    I\u2019ve used it in large programs with 50+ teams. The real value isn\u2019t the diagram itself\u2014it\u2019s the shared understanding it fosters during refinement.<\/p>\n

    Integrate with Story Mapping Tools<\/h3>\n

    Story maps are not just for backlog grooming. Use them as the foundation for dependency mapping. Overlay dependency lines directly on the map\u2019s timeline.<\/p>\n

    Example: On a customer onboarding journey, the \u00abValidate Identity\u00bb story (Team A) must precede \u00abCreate Profile\u00bb (Team B). Draw an arrow from A to B, label it \u00abAPI ready by Sprint 3\u00bb. This is not a suggestion\u2014it\u2019s a commitment.<\/p>\n

    Make these maps visible in your team\u2019s workspace. Use digital whiteboards or shared screens during refinement. The goal is to make dependency awareness part of the team\u2019s daily rhythm.<\/p>\n

    Managing Cross-Team Dependencies in Practice<\/h2>\n

    Here\u2019s how I\u2019ve seen teams successfully manage cross-team dependencies:<\/p>\n

      \n
    1. Identify early:<\/strong> During backlog refinement, flag stories that depend on other teams\u2019 output.<\/li>\n
    2. Assign ownership:<\/strong> Designate a dependency owner per story\u2014usually the team responsible for the downstream story.<\/li>\n
    3. Document in the story:<\/strong> Add a \u201cDependencies\u201d section in the story description: \u201cRequires: User Auth API (Team X) by Sprint 4.\u201d<\/li>\n
    4. Update weekly:<\/strong> Review dependency status in sync meetings. Move status from \u00abplanned\u00bb to \u00abin progress\u00bb to \u00abblocked\u00bb or \u00abresolved.\u00bb<\/li>\n
    5. Escalate transparently:<\/strong> If a dependency is at risk, flag it in the information radiator with a red tag.<\/li>\n<\/ol>\n

      These aren\u2019t bureaucratic steps. They\u2019re behaviors that build trust. When teams know exactly what\u2019s holding up delivery, they begin to coordinate proactively.<\/p>\n

      Don\u2019t Over-Model. Focus on High-Value Dependencies<\/h3>\n

      Not every story needs a dependency mapping. Focus on those that impact delivery timelines, team capacity, or user experience.<\/p>\n

      Use a simple rule: if a story\u2019s completion depends on another team\u2019s work, document it. Otherwise, trust the team\u2019s judgment.<\/p>\n

      This keeps the model lean and actionable. Too much detail leads to maintenance fatigue.<\/p>\n

      When Dependencies Break: A Case Example<\/h2>\n

      At a financial services company, two teams were building separate modules for a new digital banking portal. Team A was building the login flow. Team B was building the transaction dashboard.<\/p>\n

      Both teams assumed the authentication service was ready. When the sprint started, Team B discovered the API wasn\u2019t documented. The dependency was untracked.<\/p>\n

      Result: Team B missed their sprint goal. Team A had to pause their work to help debug.<\/p>\n

      The fix? After the fact, we implemented dependency mapping using Visual Paradigm. We added a \u201cdependency link\u201d between the login story and the API documentation story. We also created a shared dependency dashboard visible to all teams.<\/p>\n

      Now, any story relying on a backend service must reference its dependency in the backlog. The risk is visible before sprint planning.<\/p>\n

      Frequently Asked Questions<\/h2>\n

      How do I handle dependencies between teams not on the same roadmap?<\/h3>\n

      Align them through a shared program vision. Use PI planning to synchronize key dependency points. If teams are on different cadences, create a dependency buffer and assign a shared milestone.<\/p>\n

      Can dependency mapping be automated?<\/h3>\n

      Yes. Integrate your story management tool with a modeling platform like Visual Paradigm. Use APIs to sync dependency status. Track changes in real time.<\/p>\n

      What if a team refuses to commit to a dependency?<\/h3>\n

      Escalate to the program manager. The dependency owner must validate the risk. If it\u2019s high-impact, include it in the PI planning risk register.<\/p>\n

      Do I need a dedicated dependency owner?<\/h3>\n

      Not necessarily. Assign it to the team lead or the person managing the downstream story. The key is accountability\u2014not bureaucracy.<\/p>\n

      How often should I review dependency status?<\/h3>\n

      Weekly during refinement. Audit once per PI. Use the dependency dashboard as your early warning system.<\/p>\n

      Remember: the goal isn\u2019t a perfect diagram. It\u2019s a shared understanding that reduces surprises.<\/p>\n","protected":false},"excerpt":{"rendered":"

      When teams operate in silos, even small dependencies can become invisible bottlenecks. I\u2019ve seen programs stall not from technical debt or scope creep, but from untracked story dependencies blooming across team backlogs. The root issue isn\u2019t complexity\u2014it\u2019s visibility. By shifting from reactive firefighting to proactive dependency mapping, you create a shared mental model that surfaces […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1768,"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-1774","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nStory Dependencies Agile: Visualize Cross-Team Dependencies<\/title>\n<meta name=\"description\" content=\"Master dependency mapping visual paradigm to align cross-team dependencies and maintain flow in large-scale Agile programs. Practical techniques for agile professionals to reduce risk and improve delivery coherence.\" \/>\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\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/\" \/>\n<meta property=\"og:locale\" content=\"es_ES\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Story Dependencies Agile: Visualize Cross-Team Dependencies\" \/>\n<meta property=\"og:description\" content=\"Master dependency mapping visual paradigm to align cross-team dependencies and maintain flow in large-scale Agile programs. Practical techniques for agile professionals to reduce risk and improve delivery coherence.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Espa\u00f1ol\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:21:45+00:00\" \/>\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=\"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\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/\",\"name\":\"Story Dependencies Agile: Visualize Cross-Team Dependencies\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/#website\"},\"datePublished\":\"2026-02-25T10:46:01+00:00\",\"dateModified\":\"2026-03-02T09:21:45+00:00\",\"description\":\"Master dependency mapping visual paradigm to align cross-team dependencies and maintain flow in large-scale Agile programs. Practical techniques for agile professionals to reduce risk and improve delivery coherence.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/#breadcrumb\"},\"inLanguage\":\"es\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Structuring Large-Scale Backlogs\",\"item\":\"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Visualizing Dependencies Among Backlogs\"}]},{\"@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":"Story Dependencies Agile: Visualize Cross-Team Dependencies","description":"Master dependency mapping visual paradigm to align cross-team dependencies and maintain flow in large-scale Agile programs. Practical techniques for agile professionals to reduce risk and improve delivery coherence.","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\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/","og_locale":"es_ES","og_type":"article","og_title":"Story Dependencies Agile: Visualize Cross-Team Dependencies","og_description":"Master dependency mapping visual paradigm to align cross-team dependencies and maintain flow in large-scale Agile programs. Practical techniques for agile professionals to reduce risk and improve delivery coherence.","og_url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/","og_site_name":"Visual Paradigm Skills Espa\u00f1ol","article_modified_time":"2026-03-02T09:21:45+00:00","twitter_card":"summary_large_image","twitter_misc":{"Tiempo de lectura":"6 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/","url":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/","name":"Story Dependencies Agile: Visualize Cross-Team Dependencies","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/#website"},"datePublished":"2026-02-25T10:46:01+00:00","dateModified":"2026-03-02T09:21:45+00:00","description":"Master dependency mapping visual paradigm to align cross-team dependencies and maintain flow in large-scale Agile programs. Practical techniques for agile professionals to reduce risk and improve delivery coherence.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/#breadcrumb"},"inLanguage":"es","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/story-dependencies-agile-dependency-mapping\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/es\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Structuring Large-Scale Backlogs","item":"https:\/\/skills.visual-paradigm.com\/es\/docs\/user-story-techniques-large-scale-agile\/enterprise-agile-backlog-structure\/"},{"@type":"ListItem","position":4,"name":"Visualizing Dependencies Among Backlogs"}]},{"@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\/1774","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":1,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1774\/revisions"}],"predecessor-version":[{"id":2468,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1774\/revisions\/2468"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/docs\/1768"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/media?parent=1774"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/es\/wp-json\/wp\/v2\/doc_tag?post=1774"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}