{"id":1818,"date":"2026-02-25T10:46:16","date_gmt":"2026-02-25T10:46:16","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/"},"modified":"2026-02-25T10:46:16","modified_gmt":"2026-02-25T10:46:16","slug":"continuous-alignment-agile-evolving-story-flow","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/","title":{"rendered":"Evolving Toward Continuous Alignment and Story Flow"},"content":{"rendered":"

Continuous alignment agile is not a process\u2014it\u2019s a state. It\u2019s the ability to maintain shared purpose, synchronized delivery, and adaptive responsiveness across multiple teams without requiring rigid, top-down mandates.<\/p>\n

Many mistake this for simply running PI Planning or syncing backlogs. But true alignment happens when teams don\u2019t just follow a schedule\u2014they evolve together through shared understanding, transparent flow, and continuous feedback.<\/p>\n

I\u2019ve worked with organizations where sprint planning became a ritual, only to see stories stall at the integration stage. The problem wasn\u2019t velocity or capacity. It was misaligned expectations and fragile dependencies. The root fix? Not more ceremonies, but better story flow.<\/p>\n

What you\u2019ll discover here is how mature teams move beyond scaling frameworks into a rhythm of continuous alignment, where story flow becomes a living system\u2014visible, adaptive, and self-correcting.<\/p>\n

The Difference Between Synchronization and Continuous Alignment<\/h2>\n

Syncing teams via ceremonies is mechanical. Continuous alignment is intentional.<\/p>\n

Synchronization stops at meetings. Continuous alignment thrives in the space between.<\/p>\n

One team completes a story. Another team depends on it. Instead of waiting for the next planning session, the dependency is flagged, discussed, and resolved in real time.<\/p>\n

This is where story flow maturity begins\u2014not in process adherence, but in responsiveness to value.<\/p>\n

Why Story Flow Matters at Scale<\/h3>\n

At scale, stories are not isolated units. They are nodes in a network.<\/p>\n

Each story carries a thread of user value, but only if it flows smoothly across teams. When that flow breaks\u2014because of unclear acceptance criteria, uncoordinated delivery, or missing dependencies\u2014the entire system slows.<\/p>\n

Consider a banking platform where one team builds a transaction validation story, and another builds the audit logging story. If the validation story changes without informing the logging team, integration fails. Not because of bad code\u2014but because of broken flow.<\/p>\n

Building Story Flow Maturity<\/h2>\n

Story flow maturity isn\u2019t about how many stories get done. It\u2019s about how predictably and transparently value moves through the system.<\/p>\n

Here\u2019s how it unfolds in practice:<\/p>\n

    \n
  1. Define clear entry and exit criteria<\/strong> for every story, including when dependencies must be resolved.<\/li>\n
  2. Map stories to value streams<\/strong> so teams understand where their work fits in the bigger picture.<\/li>\n
  3. Visualize flow<\/strong> using a Kanban board that spans teams and shows work-in-progress limits.<\/li>\n
  4. Monitor bottlenecks<\/strong> in real time through cumulative flow diagrams.<\/li>\n
  5. Hold daily syncs focused on blockers<\/strong>, not status updates.<\/li>\n<\/ol>\n

    These aren\u2019t silver bullets. But they create a culture where alignment isn\u2019t forced\u2014it emerges.<\/p>\n

    Measuring Story Flow: What to Track<\/h3>\n

    Not every metric is helpful. Focus on these three:<\/p>\n

      \n
    • Story age<\/strong> \u2013 Time from backlog to done. High age indicates bottlenecks.<\/li>\n
    • Lead time per team<\/strong> \u2013 How long it takes a story to move through the team\u2019s workflow.<\/li>\n
    • Dependency resolution time<\/strong> \u2013 Average time taken to resolve cross-team dependencies.<\/li>\n<\/ul>\n

      These are not vanity metrics. They expose where flow breaks\u2014and where teams need to improve coordination.<\/p>\n

      The Evolution of Scaling Agile<\/h2>\n

      Scaling agile isn\u2019t a one-time transformation. It\u2019s an evolutionary journey.<\/p>\n

      Early stages focus on structure: epics, features, PI Planning. Teams follow templates. Governance is centralized.<\/p>\n

      As teams mature, focus shifts from \u201cwhat to do\u201d to \u201chow to do it together.\u201d The goal isn\u2019t compliance. It\u2019s coherence.<\/p>\n

      The evolution of scaling agile is not linear. It\u2019s cyclical\u2014each cycle deepens alignment, refines flow, and strengthens shared ownership.<\/p>\n

      Stages of Evolution<\/h3>\n\n\n\n\n\n\n\n
      Stage<\/th>\nFocus<\/th>\nKey Indicator<\/th>\nTeam Behavior<\/th>\n<\/tr>\n<\/thead>\n
      Stage 1: Structural Scaling<\/td>\nAlignment via hierarchy<\/td>\nStories mapped to epics and features<\/td>\nDependence on external planning<\/td>\n<\/tr>\n
      Stage 2: Flow Optimization<\/td>\nAlignment via workflow<\/td>\nStories flowing smoothly through teams<\/td>\nProactive dependency management<\/td>\n<\/tr>\n
      Stage 3: Continuous Alignment<\/td>\nAlignment via shared understanding<\/td>\nStories adapted in real time based on feedback<\/td>\nTeams adjust without waiting for ceremonies<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Most teams stall at Stage 2. Few reach Stage 3. But the goal isn\u2019t perfection\u2014it\u2019s progress.<\/p>\n

      Real-World Example: Financial Services Platform<\/h3>\n

      One enterprise I worked with had 12 teams building a unified customer dashboard. Initially, stories were aligned only during PI Planning. Integration failures were common.<\/p>\n

      We introduced a shared Kanban board with cross-team visibility. Teams could see pending dependency requests. A simple \u201cblocked\u201d tag triggered immediate discussion.<\/p>\n

      Within three months, integration defects dropped by 60%. Story lead time improved by 40%. Not because of more people, but because flow became visible and responsive.<\/p>\n

      Practices That Support Continuous Alignment<\/h2>\n

      Alignment isn\u2019t built in a vacuum. It\u2019s cultivated through deliberate practices.<\/p>\n

      1. Shared Acceptance Criteria Across Teams<\/h3>\n

      When teams write stories independently, acceptance criteria often diverge. This creates friction at integration.<\/p>\n

      Solution: Establish a shared template for acceptance criteria\u2014a living document updated during refinement.<\/p>\n

      Example: A story about \u201cvalidating user identity\u201d must include the following acceptance criteria across all teams:<\/p>\n

        \n
      • Validates via two-factor authentication<\/li>\n
      • Logs failed attempts with IP and timestamp<\/li>\n
      • Locks account after 5 failed attempts<\/li>\n<\/ul>\n

        2. Story Refinement Through a Common Lens<\/h3>\n

        Refinement should not be a siloed task. It\u2019s a conversation across teams.<\/p>\n

        Run joint refinement sessions every two weeks. Use a shared digital workspace.<\/p>\n

        Focus on three questions:<\/p>\n

          \n
        1. Does this story deliver measurable user value?<\/li>\n
        2. Are dependencies clearly identified and communicated?<\/li>\n
        3. Can the acceptance criteria be tested by multiple teams?<\/li>\n<\/ol>\n

          3. Lightweight Governance With No Bureaucracy<\/h3>\n

          Too many organizations add layers of approval for every story. The result? Delayed flow.<\/p>\n

          Instead, adopt lightweight governance:<\/p>\n

            \n
          • Product owners own story quality.<\/li>\n
          • Architecture review is embedded in refinement, not a separate gate.<\/li>\n
          • Any team can raise a dependency flag\u2014no sign-off needed.<\/li>\n<\/ul>\n

            Trust, not control, drives alignment.<\/p>\n

            Conclusion<\/h2>\n

            Continuous alignment agile is not a destination. It\u2019s a mindset\u2014one that values flow over form, understanding over documentation, and collaboration over control.<\/p>\n

            Story flow maturity is measured not by how many stories are delivered, but by how smoothly value moves from idea to user.<\/p>\n

            The evolution of scaling agile is not about process. It\u2019s about people learning to work together\u2014adaptively, transparently, and with shared purpose.<\/p>\n

            Start by making flow visible. Then let it guide you.<\/p>\n

            Frequently Asked Questions<\/h2>\n

            What is story flow maturity?<\/h3>\n

            Story flow maturity is the ability to maintain predictable, transparent, and adaptive movement of user stories across teams. It\u2019s measured by lead time, dependency resolution speed, and integration success rate\u2014not just velocity.<\/p>\n

            How does continuous alignment agile differ from PI Planning?<\/h3>\n

            PI Planning is a snapshot of alignment. Continuous alignment agile is the ongoing state of alignment. PI Planning sets goals; continuous alignment maintains them through real-time feedback and flow.<\/p>\n

            Can small teams achieve continuous alignment agile?<\/h3>\n

            Yes. Even small teams benefit from aligning story flow with value delivery. The principles\u2014visibility, shared understanding, and responsiveness\u2014apply at any scale.<\/p>\n

            How do I get started with story flow?<\/h3>\n

            Start with a shared Kanban board. Define entry\/exit criteria. Run joint refinement sessions. Track story age and dependency resolution time. Use this data to improve flow.<\/p>\n

            Why do most teams fail to achieve continuous alignment?<\/h3>\n

            Most teams focus on delivering stories, not on how they flow. They miss visibility into dependencies, lack shared acceptance criteria, and wait for ceremonies to resolve issues. The fix is not more process\u2014but better flow.<\/p>\n

            What role does the Product Owner play in story flow?<\/h3>\n

            The Product Owner ensures stories are valuable, well-written, and aligned with goals. They also resolve conflicts between teams and ensure dependencies are visible. They\u2019re not just a backlog manager\u2014they\u2019re a flow enabler.<\/p>\n","protected":false},"excerpt":{"rendered":"

            Continuous alignment agile is not a process\u2014it\u2019s a state. It\u2019s the ability to maintain shared purpose, synchronized delivery, and adaptive responsiveness across multiple teams without requiring rigid, top-down mandates. Many mistake this for simply running PI Planning or syncing backlogs. But true alignment happens when teams don\u2019t just follow a schedule\u2014they evolve together through shared […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1813,"menu_order":4,"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-1818","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nContinuous Alignment Agile: Evolving Story Flow<\/title>\n<meta name=\"description\" content=\"Master continuous alignment agile with proven story flow maturity practices. Learn how mature teams maintain adaptability and seamless cross-team collaboration in large-scale Agile environments.\" \/>\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\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Continuous Alignment Agile: Evolving Story Flow\" \/>\n<meta property=\"og:description\" content=\"Master continuous alignment agile with proven story flow maturity practices. Learn how mature teams maintain adaptability and seamless cross-team collaboration in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Deutsch\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Gesch\u00e4tzte Lesezeit\" \/>\n\t<meta name=\"twitter:data1\" content=\"6\u00a0Minuten\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/\",\"name\":\"Continuous Alignment Agile: Evolving Story Flow\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\"},\"datePublished\":\"2026-02-25T10:46:16+00:00\",\"description\":\"Master continuous alignment agile with proven story flow maturity practices. Learn how mature teams maintain adaptability and seamless cross-team collaboration in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/#breadcrumb\"},\"inLanguage\":\"de\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Real-World Lessons and Case Studies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Evolving Toward Continuous Alignment and Story Flow\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"name\":\"Visual Paradigm Skills Deutsch\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"de\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#organization\",\"name\":\"Visual Paradigm Skills Deutsch\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"de\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Deutsch\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Continuous Alignment Agile: Evolving Story Flow","description":"Master continuous alignment agile with proven story flow maturity practices. Learn how mature teams maintain adaptability and seamless cross-team collaboration in large-scale Agile environments.","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\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/","og_locale":"de_DE","og_type":"article","og_title":"Continuous Alignment Agile: Evolving Story Flow","og_description":"Master continuous alignment agile with proven story flow maturity practices. Learn how mature teams maintain adaptability and seamless cross-team collaboration in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/","og_site_name":"Visual Paradigm Skills Deutsch","twitter_card":"summary_large_image","twitter_misc":{"Gesch\u00e4tzte Lesezeit":"6\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/","url":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/","name":"Continuous Alignment Agile: Evolving Story Flow","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#website"},"datePublished":"2026-02-25T10:46:16+00:00","description":"Master continuous alignment agile with proven story flow maturity practices. Learn how mature teams maintain adaptability and seamless cross-team collaboration in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/continuous-alignment-agile-evolving-story-flow\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/de\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Real-World Lessons and Case Studies","item":"https:\/\/skills.visual-paradigm.com\/de\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-case-studies\/"},{"@type":"ListItem","position":4,"name":"Evolving Toward Continuous Alignment and Story Flow"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/de\/#website","url":"https:\/\/skills.visual-paradigm.com\/de\/","name":"Visual Paradigm Skills Deutsch","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/de\/#organization","name":"Visual Paradigm Skills Deutsch","url":"https:\/\/skills.visual-paradigm.com\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/de\/wp-content\/uploads\/sites\/4\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Deutsch"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/de\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1818","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1818\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/docs\/1813"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/media?parent=1818"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/de\/wp-json\/wp\/v2\/doc_tag?post=1818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}