{"id":1442,"date":"2026-02-25T10:41:39","date_gmt":"2026-02-25T10:41:39","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/"},"modified":"2026-02-25T10:41:39","modified_gmt":"2026-02-25T10:41:39","slug":"scrum-team-interactions-cohesive-team","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/","title":{"rendered":"Role Interactions in Scrum: Building a Cohesive Team"},"content":{"rendered":"

Too many teams treat the Scrum roles as isolated boxes on a diagram. I\u2019ve seen teams copy the roles from a template, assign titles to individuals, and then wonder why collaboration feels forced or leadership gaps emerge. The real work begins not in naming roles, but in how they interact.<\/p>\n

There\u2019s no one-size-fits-all chart for role interactions. What matters is the rhythm and intent behind each conversation. The Product Owner doesn\u2019t just hand off work to the Development Team\u2014she ensures clarity, value, and alignment. The Scrum Master doesn\u2019t just \u00ab\u00a0run meetings\u00a0\u00bb\u2014she removes blockers so the team can focus on delivering value.<\/p>\n

When you understand how Scrum roles work together, you\u2019ll stop treating events as procedural tasks and start seeing them as living conversations. This chapter breaks down those interactions with real examples, communication patterns, and visual cues to help beginners avoid common missteps and build trust across roles.<\/p>\n

How Scrum Roles Work Together: The Core of Team Cohesion<\/h2>\n

Interaction Patterns Across Scrum Events<\/h3>\n

Each Scrum event creates a natural moment for roles to engage. These aren\u2019t rigid handoffs\u2014they\u2019re collaborative touchpoints where intent, clarity, and ownership converge.<\/p>\n

Sprint Planning:<\/strong> The Product Owner brings the sprint goal and backlog items. The Development Team asks questions, estimates effort, and breaks down tasks. The Scrum Master ensures timeboxing, facilitates discussion, and protects the team from external interference.<\/p>\n

Daily Scrum:<\/strong> The Development Team synchronizes on progress, plans the day, and identifies blockers. The Scrum Master observes and intervenes only if a constraint arises. The Product Owner may attend to clarify priorities but doesn\u2019t dominate.<\/p>\n

Sprint Review:<\/strong> The team demonstrates the increment. The Product Owner evaluates acceptance criteria. Stakeholders provide feedback. The Scrum Master ensures feedback is constructive and focused. This is where value is validated\u2014not in isolation, but through shared understanding.<\/p>\n

Sprint Retrospective:<\/strong> The team reflects on the sprint. The Scrum Master guides the reflection, ensures psychological safety, and helps identify improvements. The Product Owner and Development Team co-create action items. No one role owns the process\u2014everyone contributes.<\/p>\n

Visualizing Role Interactions<\/h3>\n

Here\u2019s a simple representation of how roles interact during events:<\/p>\n\n\n\n\n\n\n\n
Event<\/th>\nPrimary Interaction<\/th>\nKey Role Responsibilities<\/th>\n<\/tr>\n
Sprint Planning<\/td>\nProduct Owner \u2194 Development Team<\/td>\nGoal setting, backlog refinement, task breakdown<\/td>\n<\/tr>\n
Daily Scrum<\/td>\nDevelopment Team \u2194 Scrum Master<\/td>\nSynchronization, obstacle removal, focus maintenance<\/td>\n<\/tr>\n
Sprint Review<\/td>\nDevelopment Team \u2194 Product Owner \u2194 Stakeholders<\/td>\nDemo, feedback, acceptance, value validation<\/td>\n<\/tr>\n
Sprint Retrospective<\/td>\nScrum Master \u2194 Entire Team<\/td>\nFacilitation, reflection, action planning<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

How Scrum Roles Work Together: Practical Scenarios<\/h2>\n

Scenario 1: When the Product Owner Doesn\u2019t Clarify<\/h3>\n

The team starts work on a backlog item without clear acceptance criteria. The Scrum Master notices the confusion and steps in. She doesn\u2019t dictate the solution\u2014she invites the Product Owner to clarify the goal and expected outcome.<\/p>\n

The Development Team can\u2019t deliver \u00ab\u00a0done\u00a0\u00bb if they don\u2019t know what \u00ab\u00a0done\u00a0\u00bb means. The Scrum Master ensures this conversation happens early, and the team doesn\u2019t proceed until clarity is established.<\/p>\n

Scenario 2: A Blocker Emerges Mid-Sprint<\/h3>\n

A developer discovers a dependency on another team\u2019s API. The Scrum Master doesn\u2019t solve it\u2014she facilitates a discussion: \u201cWho on the team can reach out to the dependent team?\u201d<\/p>\n

If no one has bandwidth, the Scrum Master helps the team escalate with context. She ensures the team\u2019s focus stays on the sprint goal, not on administrative overhead.<\/p>\n

Scenario 3: The Development Team Overcommits<\/h3>\n

During sprint planning, the team commits to more work than they can realistically deliver. The Scrum Master observes the velocity trend and gently questions: \u201cIs this realistic based on past performance?\u201d<\/p>\n

She doesn\u2019t override the decision\u2014but she ensures the team reflects on it during the retrospective. This is how self-organization grows: through feedback, not force.<\/p>\n

Preventing Role Confusion and Overlap<\/h2>\n

Role confusion often arises from misaligned expectations. Here are common pitfalls and how to address them:<\/p>\n

    \n
  • Mistake:<\/strong> The Scrum Master takes ownership of sprint tasks. Solution:<\/strong> The Scrum Master facilitates, not executes. Only the Development Team delivers the increment.<\/li>\n
  • Mistake:<\/strong> The Product Owner acts as the team\u2019s manager. Solution:<\/strong> The Product Owner prioritizes, the Development Team plans and delivers. No one manages the team\u2014just supports the process.<\/li>\n
  • Mistake:<\/strong> The Development Team works in silos. Solution:<\/strong> The Scrum Master encourages collaboration, uses the Daily Scrum to surface dependencies, and promotes collective ownership.<\/li>\n<\/ul>\n

    When roles become blurred, it\u2019s not about titles\u2014it\u2019s about behaviors. The Scrum Master doesn\u2019t \u00ab\u00a0manage\u00a0\u00bb the team. The Product Owner doesn\u2019t \u00ab\u00a0assign\u00a0\u00bb work. The Development Team doesn\u2019t \u00ab\u00a0wait for direction.\u00a0\u00bb Instead, they respond to value, adapt to feedback, and improve together.<\/p>\n

    Scrum Roles Collaboration Beginners: A Framework for Success<\/h2>\n

    Building effective Scrum team interactions takes more than understanding roles. It requires consistent alignment, trust, and regular reflection.<\/p>\n

    Use this checklist to evaluate your team\u2019s role interactions after each sprint:<\/p>\n

      \n
    1. Did the Product Owner clearly communicate the sprint goal and backlog items?<\/li>\n
    2. Did the Development Team understand acceptance criteria before starting work?<\/li>\n
    3. Did the Scrum Master help remove impediments without taking over?<\/li>\n
    4. Did stakeholders provide feedback during the review?<\/li>\n
    5. Did the team identify at least one actionable improvement in the retrospective?<\/li>\n<\/ol>\n

      Review this checklist as a team. Don\u2019t chase perfection\u2014focus on consistency. Over time, this builds a rhythm of trust and transparency.<\/p>\n

      Frequently Asked Questions<\/h2>\n

      How do the Scrum roles work together in practice?<\/h3>\n

      The Product Owner defines what to build and why. The Development Team decides how to build it. The Scrum Master ensures the process works and removes obstacles. They collaborate through events like Sprint Planning, Daily Scrum, Sprint Review, and Retrospective\u2014each with a shared purpose: delivering value.<\/p>\n

      Can the Scrum Master also be part of the Development Team?<\/h3>\n

      Yes. The Scrum Master can be a developer, but they must not perform development tasks that compromise their role as a facilitator. If they do, their focus may shift from team health to delivery, risking conflict of interest. The key is that their primary responsibility is process improvement, not task execution.<\/p>\n

      What happens if the Product Owner is unavailable during a sprint?<\/h3>\n

      The team should pause work on high-priority items that require clarification. The Scrum Master can help escalate to leadership, but the team must not make assumptions. The sprint goal remains intact, but delivery depends on clarity. This is why the Product Owner\u2019s availability is critical.<\/p>\n

      How do I handle a team member who isn\u2019t engaging in Scrum events?<\/h3>\n

      Start with empathy. Ask privately: \u201cWhat\u2019s making it hard to participate?\u201d If it\u2019s lack of clarity, help reframe the event\u2019s purpose. If it\u2019s resistance, involve the Scrum Master to create psychological safety. Never exclude someone\u2014instead, support inclusion.<\/p>\n

      Is it okay for the Development Team to self-organize without the Scrum Master?<\/h3>\n

      Yes\u2014but only when the Scrum Master has trained them to do so. The goal is not to remove the Scrum Master, but to build autonomy. Self-organization isn\u2019t chaos\u2014it\u2019s the result of disciplined collaboration, transparency, and continuous feedback.<\/p>\n

      How do we ensure the Product Owner doesn\u2019t dominate the Daily Scrum?<\/h3>\n

      Set a clear rule: only the Development Team speaks during the Daily Scrum. The Product Owner may observe but doesn\u2019t direct. If they interrupt, the Scrum Master gently reminds them: \u00ab\u00a0We’re here to align the team, not assign work.\u00a0\u00bb Over time, the team learns to own their planning.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Too many teams treat the Scrum roles as isolated boxes on a diagram. I\u2019ve seen teams copy the roles from a template, assign titles to individuals, and then wonder why collaboration feels forced or leadership gaps emerge. The real work begins not in naming roles, but in how they interact. There\u2019s no one-size-fits-all chart for […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1438,"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-1442","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nScrum Team Interactions: Cohesion Through Collaboration<\/title>\n<meta name=\"description\" content=\"Master how Scrum roles work together seamlessly. Learn practical interaction patterns, communication flow, and strategies to prevent role confusion for high-performing teams.\" \/>\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\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scrum Team Interactions: Cohesion Through Collaboration\" \/>\n<meta property=\"og:description\" content=\"Master how Scrum roles work together seamlessly. Learn practical interaction patterns, communication flow, and strategies to prevent role confusion for high-performing teams.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/\" \/>\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\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/\",\"name\":\"Scrum Team Interactions: Cohesion Through Collaboration\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:41:39+00:00\",\"description\":\"Master how Scrum roles work together seamlessly. Learn practical interaction patterns, communication flow, and strategies to prevent role confusion for high-performing teams.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum Essentials: Beginner\u2019s Guide to Agile\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Defining Scrum Roles Clearly\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Role Interactions in Scrum: Building a Cohesive Team\"}]},{\"@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":"Scrum Team Interactions: Cohesion Through Collaboration","description":"Master how Scrum roles work together seamlessly. Learn practical interaction patterns, communication flow, and strategies to prevent role confusion for high-performing teams.","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\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/","og_locale":"fr_FR","og_type":"article","og_title":"Scrum Team Interactions: Cohesion Through Collaboration","og_description":"Master how Scrum roles work together seamlessly. Learn practical interaction patterns, communication flow, and strategies to prevent role confusion for high-performing teams.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/","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\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/","name":"Scrum Team Interactions: Cohesion Through Collaboration","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:41:39+00:00","description":"Master how Scrum roles work together seamlessly. Learn practical interaction patterns, communication flow, and strategies to prevent role confusion for high-performing teams.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/scrum-team-interactions-cohesive-team\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Scrum Essentials: Beginner\u2019s Guide to Agile","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/"},{"@type":"ListItem","position":3,"name":"Defining Scrum Roles Clearly","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/scrum-essentials-beginners-guide-to-agile\/defining-scrum-roles-clearly\/"},{"@type":"ListItem","position":4,"name":"Role Interactions in Scrum: Building a Cohesive Team"}]},{"@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\/1442","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\/1442\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/1438"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=1442"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=1442"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}