{"id":10905,"date":"2026-03-06T02:32:39","date_gmt":"2026-03-05T18:32:39","guid":{"rendered":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/"},"modified":"2026-03-06T02:32:39","modified_gmt":"2026-03-05T18:32:39","slug":"deep-product-backlog-scrum-agile","status":"publish","type":"post","link":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/","title":{"rendered":"Scrum : Que signifie DEEP dans le Product Backlog ?"},"content":{"rendered":"
Le Product Backlog<\/a> est une liste ordonn\u00e9e de tout ce qui est connu comme n\u00e9cessaire pour le produit. C’est la source unique de v\u00e9rit\u00e9 pour tout changement apport\u00e9 au produit. Le Product Owner<\/a> est responsable du Product Backlog, y compris son contenu, sa visibilit\u00e9 et son tri.<\/div>\n
Le Product Backlog n’est jamais final. Les changements dans les besoins commerciaux, les conditions du march\u00e9 ou la technologie peuvent entra\u00eener des modifications dans le Product Backlog. Il \u00e9volue au fur et \u00e0 mesure que le produit et l’environnement du projet \u00e9voluent. Les exigences ne cessent jamais de changer, donc le Product Backlog reste un artefact Scrum<\/a>.<\/div>\n
Les \u00e9l\u00e9ments de plus haut niveau dans le Product Backlog sont plus granulaires et contiennent plus de d\u00e9tails \u2014 en raison de la disponibilit\u00e9 d’informations suppl\u00e9mentaires \u2014 ainsi que des estimations plus pr\u00e9cises. Les \u00e9l\u00e9ments de plus bas niveau sont des \u00e9l\u00e9ments de haut niveau, plus importants, avec des estimations plus approximatives. Au fur et \u00e0 mesure que l’\u00e9quipe obtient plus d’informations sur les \u00e9l\u00e9ments de plus bas niveau, ils sont divis\u00e9s davantage en morceaux plus petits et plus g\u00e9rables. L’\u00e9quipe de d\u00e9veloppement est responsable des estimations des \u00e9l\u00e9ments du Product Backlog.<\/div>\n
\n

Comprendre la gestion du Product Backlog<\/h2>\n<\/div>\n
Le Product Backlog liste toutes les fonctionnalit\u00e9s, exigences, am\u00e9liorations et corrections n\u00e9cessaires au d\u00e9veloppement du produit. Les \u00e9l\u00e9ments du Product Backlog ont des attributs tels que :D<\/strong>\u00e9taill\u00e9 (niveau appropri\u00e9 de d\u00e9tail),E<\/strong>estim\u00e9 (en points d’histoire),P<\/strong>prioris\u00e9, etE<\/strong>mis \u00e0 jour (ajout\u00e9, supprim\u00e9 et mis \u00e0 jour continuellement) pour refl\u00e9ter des ajustements opportuns et opportuns du backlog.<\/div>\n
Roman Pichler, auteur de Gestion agile des produits avec Scrum<\/em><\/div>\n
\u00ab Cr\u00e9ez un produit que les clients aiment. \u00bb Nous utilisons l’acronyme DEEP pour d\u00e9crire les caract\u00e9ristiques d’un Product Backlog bien g\u00e9r\u00e9. Ainsi, DEEP est un acronyme d\u00e9crivant la qualit\u00e9 du Product Backlog dans Scrum, compos\u00e9 de :D<\/strong>\u00e9taill\u00e9,E<\/strong>estim\u00e9,E<\/strong>mis \u00e0 jour, etP<\/strong>prioris\u00e9s.<\/em><\/div>\n
\"Understanding<\/div>\n
\n

D\u00e9taill\u00e9<\/h3>\n<\/div>\n
Les histoires situ\u00e9es en haut du Backlog produit sont cens\u00e9es \u00eatre ex\u00e9cut\u00e9es lors du prochainSprint<\/a>, donc elles doivent \u00eatre bien d\u00e9finies pour permettre \u00e0 l’\u00e9quipe de les g\u00e9rer efficacement. G\u00e9n\u00e9ralement, les \u00e9l\u00e9ments situ\u00e9s en haut sont plus petits et plus granulaires, tandis que les \u00e9l\u00e9ments situ\u00e9s plus bas deviennent plus grands et moins pr\u00e9cis, comme indiqu\u00e9 dans la figure ci-dessous :<\/div>\n
\"Detailed<\/div>\n
\n

Estim\u00e9<\/h3>\n<\/div>\n
Les \u00e9l\u00e9ments du Backlog produit sont estim\u00e9s. Les \u00e9l\u00e9ments situ\u00e9s en haut du backlog ont des estimations plus pr\u00e9cises. Les \u00e9l\u00e9ments de faible priorit\u00e9 sont estim\u00e9s \u00e0 un niveau plus \u00e9lev\u00e9 et peuvent \u00eatre r\u00e9estim\u00e9s lorsque l’\u00e9quipe acquiert davantage d’informations.<\/div>\n
\"User<\/div>\n
\n

\u00c9mergent<\/h3>\n<\/div>\n
Le Backlog produit n’est pas statique \u2014 il \u00e9volue constamment. Au fur et \u00e0 mesure que le projet progresse, davantage d’informations et de connaissances sont acquises, et les histoires utilisateurs du Backlog produit sont ajout\u00e9es, supprim\u00e9es ou r\u00e9organis\u00e9es.<\/div>\n
\"Agile<\/div>\n
\n

Prioris\u00e9<\/h3>\n<\/div>\n
Dans le Backlog produit, les \u00e9l\u00e9ments de haute priorit\u00e9 sont plus valorisants. Les \u00e9l\u00e9ments de faible priorit\u00e9 sont list\u00e9s plus tard. L’\u00e9quipe travaille toujours sur les \u00e9l\u00e9ments de haute priorit\u00e9 afin de garantir que la valeur maximale soit livr\u00e9e dans le produit ou le syst\u00e8me en cours de d\u00e9veloppement.<\/div>\n
\"Prioritized<\/div>\n
\n

R\u00e9sum\u00e9<\/h2>\n<\/div>\n
DEEP est un concept utile appliqu\u00e9 auAffinage du Backlog produit<\/a>processus \u2014 l’activit\u00e9 continue d’ajout de d\u00e9tails, d’estimation et de tri aux \u00e9l\u00e9ments du Backlog produit afin de le maintenir en bon \u00e9tat.<\/div>\n
Pendant l’affinage du Backlog produit, les \u00e9l\u00e9ments sont revus et modifi\u00e9s. L’\u00e9quipe Scrum d\u00e9cide de la mani\u00e8re et du moment o\u00f9 l’affinage est effectu\u00e9. L’affinage prend g\u00e9n\u00e9ralement au plus 10 % de la capacit\u00e9 de l’\u00e9quipe de d\u00e9veloppement. Toutefois, les \u00e9l\u00e9ments du Backlog produit peuvent \u00eatre mis \u00e0 jour \u00e0 tout moment par le Product Owner, ou selon les besoins.<\/div>\n","protected":false},"excerpt":{"rendered":"

Product Backlog projects have described attributes (D appropriate details), Story points (E stimated), order (P rioritized), and they are constantly added, deleted and updated (E merged) in the backlog to reflect the backlog of teams in a timely and appropriate manner. (\u4ea7\u54c1Backlog\u9879\u76ee\u5177\u6709\u63cf\u8ff0\u7684\u5c5e\u6027\uff08D\u9002\u5f53\u7684\u8be6\u7ec6\u8bf4\u660e\uff09\uff0cStory points\uff08E\u00a0stimated\uff09\uff0corder\uff08P\u00a0rioritized\uff09\uff0c\u5e76\u4e14\u5b83\u4eec\u5728\u79ef\u538b\u4e2d\u4e0d\u65ad\u88ab\u6dfb\u52a0\uff0c\u5220\u9664\u548c\u66f4\u65b0\uff08E\u5408\u5e76\uff09\u4ee5\u53cd\u6620\u5230\u5bf9\u4ee5\u53ca\u65f6\u548c\u6070\u5f53\u7684\u65b9\u5f0f\u79ef\u538b\u56e2\u961f\u7684\u79ef\u538b\u3002)<\/p>\n","protected":false},"author":3479,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_yoast_wpseo_title":"Que signifie DEEP dans le Backlog produit Scrum ?","_yoast_wpseo_metadesc":"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.","fifu_image_url":"","fifu_image_alt":"","footnotes":""},"categories":[83],"tags":[],"class_list":["post-10905","post","type-post","status-publish","format-standard","hentry","category-scrum"],"yoast_head":"\nQue signifie DEEP dans le Backlog produit Scrum ?<\/title>\n<meta name=\"description\" content=\"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Que signifie DEEP dans le Backlog produit Scrum ?\" \/>\n<meta property=\"og:description\" content=\"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"ArchiMetric French\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-05T18:32:39+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png\" \/>\n<meta name=\"author\" content=\"archimetric@visual-paradigm.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"archimetric@visual-paradigm.com\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\"},\"author\":{\"name\":\"archimetric@visual-paradigm.com\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\"},\"headline\":\"Scrum : Que signifie DEEP dans le Product Backlog ?\",\"datePublished\":\"2026-03-05T18:32:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\"},\"wordCount\":683,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png\",\"articleSection\":[\"Scrum\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\",\"url\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\",\"name\":\"Que signifie DEEP dans le Backlog produit Scrum ?\",\"isPartOf\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png\",\"datePublished\":\"2026-03-05T18:32:39+00:00\",\"author\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\"},\"description\":\"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage\",\"url\":\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png\",\"contentUrl\":\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.archimetric.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum : Que signifie DEEP dans le Product Backlog ?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/#website\",\"url\":\"https:\/\/www.archimetric.com\/fr\/\",\"name\":\"ArchiMetric French\",\"description\":\"EA, Dev Ops, Scrum, Agile and More\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.archimetric.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\",\"name\":\"archimetric@visual-paradigm.com\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g\",\"caption\":\"archimetric@visual-paradigm.com\"},\"url\":\"https:\/\/www.archimetric.com\/fr\/author\/archimetricvisual-paradigm-com\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Que signifie DEEP dans le Backlog produit Scrum ?","description":"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.","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:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/","og_locale":"fr_FR","og_type":"article","og_title":"Que signifie DEEP dans le Backlog produit Scrum ?","og_description":"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.","og_url":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/","og_site_name":"ArchiMetric French","article_published_time":"2026-03-05T18:32:39+00:00","og_image":[{"url":"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png","type":"","width":"","height":""}],"author":"archimetric@visual-paradigm.com","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"archimetric@visual-paradigm.com","Dur\u00e9e de lecture estim\u00e9e":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#article","isPartOf":{"@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/"},"author":{"name":"archimetric@visual-paradigm.com","@id":"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28"},"headline":"Scrum : Que signifie DEEP dans le Product Backlog ?","datePublished":"2026-03-05T18:32:39+00:00","mainEntityOfPage":{"@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/"},"wordCount":683,"commentCount":0,"image":{"@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png","articleSection":["Scrum"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/","url":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/","name":"Que signifie DEEP dans le Backlog produit Scrum ?","isPartOf":{"@id":"https:\/\/www.archimetric.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage"},"image":{"@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png","datePublished":"2026-03-05T18:32:39+00:00","author":{"@id":"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28"},"description":"Comprenez DEEP dans Scrum : D\u00e9taill\u00e9, Estim\u00e9, \u00c9mergent et Prioris\u00e9 \u2014 les 4 caract\u00e9ristiques cl\u00e9s d'un Backlog produit bien g\u00e9r\u00e9.","breadcrumb":{"@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#primaryimage","url":"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png","contentUrl":"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png"},{"@type":"BreadcrumbList","@id":"https:\/\/www.archimetric.com\/fr\/deep-product-backlog-scrum-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.archimetric.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Scrum : Que signifie DEEP dans le Product Backlog ?"}]},{"@type":"WebSite","@id":"https:\/\/www.archimetric.com\/fr\/#website","url":"https:\/\/www.archimetric.com\/fr\/","name":"ArchiMetric French","description":"EA, Dev Ops, Scrum, Agile and More","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.archimetric.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28","name":"archimetric@visual-paradigm.com","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.archimetric.com\/fr\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/de58c1924d83d002dbce0b79f74ba4b70e2f85238332df6cabc0227effdf470d?s=96&d=mm&r=g","caption":"archimetric@visual-paradigm.com"},"url":"https:\/\/www.archimetric.com\/fr\/author\/archimetricvisual-paradigm-com\/"}]}},"_links":{"self":[{"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/posts\/10905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/users\/3479"}],"replies":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/comments?post=10905"}],"version-history":[{"count":0,"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/posts\/10905\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/media?parent=10905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/categories?post=10905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.archimetric.com\/fr\/wp-json\/wp\/v2\/tags?post=10905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}