{"id":10908,"date":"2026-03-06T02:32:56","date_gmt":"2026-03-05T18:32:56","guid":{"rendered":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/"},"modified":"2026-03-06T02:32:56","modified_gmt":"2026-03-05T18:32:56","slug":"deep-product-backlog-scrum-agile","status":"publish","type":"post","link":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/","title":{"rendered":"Scrum: Co oznacza DEEP w Backlogu Produktu?"},"content":{"rendered":"
Za Backlog Produktu<\/a> to uporz\u0105dkowana lista wszystkiego, co jest znane jako potrzebne w produkcie. Jest to jedyny \u017ar\u00f3d\u0142o prawdy dla wszelkich zmian w produkcie. W\u0142a\u015bciciel Produktu<\/a> jest odpowiedzialny za Backlog Produktu, w tym jego zawarto\u015b\u0107, widoczno\u015b\u0107 i uporz\u0105dkowanie.<\/div>\n
Backlog Produktu nigdy nie jest ostateczny. Zmiany potrzeb biznesowych, warunk\u00f3w rynkowych lub technologii mog\u0105 prowadzi\u0107 do zmian w Backlogu Produktu. Rozwija si\u0119 wraz z rozwojem produktu i \u015brodowiska projektu. Wymagania nie przestaj\u0105 si\u0119 zmienia\u0107, dlatego Backlog Produktu pozostaje \u017cywym artefaktem Scrum<\/a>.<\/div>\n
Wy\u017cszo\u015b\u0107 priorytet\u00f3w w Backlogu Produktu jest bardziej szczeg\u00f3\u0142owa i zawiera wi\u0119cej szczeg\u00f3\u0142\u00f3w \u2014 dzi\u0119ki wi\u0119kszej ilo\u015bci dost\u0119pnych informacji \u2014 wraz z bardziej dok\u0142adnymi szacunkami. Ni\u017csze priorytety to wy\u017csze poziomy, wi\u0119ksze elementy z surowszymi szacunkami. Gdy zesp\u00f3\u0142 zdobywa wi\u0119cej informacji o elementach o ni\u017cszym priorytecie, s\u0105 one dalej dzielone na mniejsze, \u0142atwiejsze do zarz\u0105dzania cz\u0119\u015bci. Zesp\u00f3\u0142 rozwojowy jest odpowiedzialny za szacowanie element\u00f3w w Backlogu Produktu.<\/div>\n
\n

Zrozumienie zarz\u0105dzania Backlogiem Produktu<\/h2>\n<\/div>\n
Backlog Produktu zawiera wszystkie funkcje, wymagania, ulepszenia i poprawki, kt\u00f3re musz\u0105 zosta\u0107 opracowane dla produktu. Elementy Backlogu Produktu maj\u0105 takie cechy jak: D<\/strong>etalny (odpowiedni poziom szczeg\u00f3\u0142owo\u015bci), E<\/strong>szacowany (w punktach historii), P<\/strong>riorityzowany i E<\/strong>zmergowany (ci\u0105gle dodawany, usuwany i aktualizowany), aby odzwierciedla\u0107 odpowiednie i czasowe dostosowania do backlogu.<\/div>\n
Roman Pichler, autor Zarz\u0105dzanie produktem agilnie z wykorzystaniem Scrum<\/em><\/div>\n
\u201eStw\u00f3rz produkt, kt\u00f3ry podoba si\u0119 klientom.\u201d U\u017cywamy skr\u00f3tu DEEP, aby opisa\u0107 cechy dobrze zarz\u0105dzanego Backlogu Produktu. Dlatego DEEP to skr\u00f3t opisuj\u0105cy jako\u015b\u0107 Backlogu Produktu w Scrum, sk\u0142adaj\u0105cy si\u0119 z: D<\/strong>etalny, E<\/strong>szacowany, E<\/strong>zmergowany i P<\/strong>Priorytetowe.<\/em><\/div>\n
\"Understanding<\/div>\n
\n

Szczeg\u00f3\u0142owe<\/h3>\n<\/div>\n
Historie znajduj\u0105ce si\u0119 na szczycie listy produktu powinny zosta\u0107 wykonane w kolejnymSprint<\/a>, dlatego musz\u0105 by\u0107 dok\u0142adnie sformu\u0142owane, aby zesp\u00f3\u0142 m\u00f3g\u0142 je skutecznie obs\u0142u\u017cy\u0107. Zazwyczaj elementy znajduj\u0105ce si\u0119 na szczycie s\u0105 mniejsze i bardziej szczeg\u00f3\u0142owe, podczas gdy elementy po\u0142o\u017cone ni\u017cej staj\u0105 si\u0119 wi\u0119ksze i mniej szczeg\u00f3\u0142owe, jak pokazano na poni\u017cszym rysunku:<\/div>\n
\"Detailed<\/div>\n
\n

Szacowane<\/h3>\n<\/div>\n
Elementy na li\u015bcie produktu s\u0105 szacowane. Elementy znajduj\u0105ce si\u0119 na szczycie listy maj\u0105 bardziej dok\u0142adne szacunki. Elementy o ni\u017cszym priorytecie s\u0105 szacowane na wy\u017cszym poziomie i mog\u0105 by\u0107 ponownie szacowane, gdy zesp\u00f3\u0142 zdob\u0119dzie wi\u0119cej informacji.<\/div>\n
\"User<\/div>\n
\n

Ewolucyjne<\/h3>\n<\/div>\n
Lista produktu nie jest statyczna \u2014 stale si\u0119 rozwija. W miar\u0119 post\u0119pu projektu zdobywane s\u0105 nowe informacje i wiedza, a historie u\u017cytkownika na li\u015bcie produktu s\u0105 dodawane, usuwane lub ponownie sortowane.<\/div>\n
\"Agile<\/div>\n
\n

Priorytetowe<\/h3>\n<\/div>\n
Na li\u015bcie produktu elementy o wy\u017cszym priorytecie s\u0105 bardziej warto\u015bciowe. Elementy o ni\u017cszym priorytecie s\u0105 umieszczane p\u00f3\u017aniej. Zesp\u00f3\u0142 zawsze pracuje nad elementami o najwy\u017cszym priorytecie, aby zapewni\u0107 maksymaln\u0105 warto\u015b\u0107 w produkcie lub systemie w trakcie rozwoju.<\/div>\n
\"Prioritized<\/div>\n
\n

Podsumowanie<\/h2>\n<\/div>\n
DEEP to przydatny koncept stosowany doDostosowania listy produktu<\/a> procesu \u2014 ci\u0105g\u0142ej dzia\u0142alno\u015bci polegaj\u0105cej na dodawaniu szczeg\u00f3\u0142\u00f3w, szacowania i sortowania element\u00f3w na li\u015bcie produktu, aby utrzyma\u0107 j\u0105 w dobrym stanie.<\/div>\n
W trakcie dostosowania listy produktu elementy s\u0105 przegl\u0105darkowane i modyfikowane. Zesp\u00f3\u0142 Scrum decyduje, jak i kiedy przeprowadzane jest dostosowanie. Dostosowanie zwykle zajmuje nie wi\u0119cej ni\u017c 10% pojemno\u015bci zespo\u0142u rozwojowego. Jednak elementy listy produktu mog\u0105 by\u0107 aktualizowane w dowolnym momencie przez w\u0142a\u015bciciela produktu lub w zale\u017cno\u015bci od potrzeb.<\/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":"Co oznacza DEEP w li\u015bcie produktu Scrum?","_yoast_wpseo_metadesc":"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.","fifu_image_url":"","fifu_image_alt":"","footnotes":""},"categories":[83],"tags":[],"class_list":["post-10908","post","type-post","status-publish","format-standard","hentry","category-scrum"],"yoast_head":"\nCo oznacza DEEP w li\u015bcie produktu Scrum?<\/title>\n<meta name=\"description\" content=\"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.\" \/>\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\/pl\/deep-product-backlog-scrum-agile\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Co oznacza DEEP w li\u015bcie produktu Scrum?\" \/>\n<meta property=\"og:description\" content=\"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/\" \/>\n<meta property=\"og:site_name\" content=\"ArchiMetric Polish\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-05T18:32:56+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=\"Napisane przez\" \/>\n\t<meta name=\"twitter:data1\" content=\"archimetric@visual-paradigm.com\" \/>\n\t<meta name=\"twitter:label2\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minuty\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/\"},\"author\":{\"name\":\"archimetric@visual-paradigm.com\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\"},\"headline\":\"Scrum: Co oznacza DEEP w Backlogu Produktu?\",\"datePublished\":\"2026-03-05T18:32:56+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/\"},\"wordCount\":558,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png\",\"articleSection\":[\"Scrum\"],\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/\",\"url\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/\",\"name\":\"Co oznacza DEEP w li\u015bcie produktu Scrum?\",\"isPartOf\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/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:56+00:00\",\"author\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\"},\"description\":\"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/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\/pl\/deep-product-backlog-scrum-agile\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.archimetric.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum: Co oznacza DEEP w Backlogu Produktu?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/#website\",\"url\":\"https:\/\/www.archimetric.com\/pl\/\",\"name\":\"ArchiMetric Polish\",\"description\":\"EA, Dev Ops, Scrum, Agile and More\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.archimetric.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28\",\"name\":\"archimetric@visual-paradigm.com\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/www.archimetric.com\/pl\/#\/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\/pl\/author\/archimetricvisual-paradigm-com\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Co oznacza DEEP w li\u015bcie produktu Scrum?","description":"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.","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\/pl\/deep-product-backlog-scrum-agile\/","og_locale":"pl_PL","og_type":"article","og_title":"Co oznacza DEEP w li\u015bcie produktu Scrum?","og_description":"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.","og_url":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/","og_site_name":"ArchiMetric Polish","article_published_time":"2026-03-05T18:32:56+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":{"Napisane przez":"archimetric@visual-paradigm.com","Szacowany czas czytania":"4 minuty"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#article","isPartOf":{"@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/"},"author":{"name":"archimetric@visual-paradigm.com","@id":"https:\/\/www.archimetric.com\/pl\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28"},"headline":"Scrum: Co oznacza DEEP w Backlogu Produktu?","datePublished":"2026-03-05T18:32:56+00:00","mainEntityOfPage":{"@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/"},"wordCount":558,"commentCount":0,"image":{"@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#primaryimage"},"thumbnailUrl":"https:\/\/www.archimetric.com\/wp-content\/uploads\/2022\/02\/deep-in-product-backlog.png","articleSection":["Scrum"],"inLanguage":"pl-PL","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/","url":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/","name":"Co oznacza DEEP w li\u015bcie produktu Scrum?","isPartOf":{"@id":"https:\/\/www.archimetric.com\/pl\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#primaryimage"},"image":{"@id":"https:\/\/www.archimetric.com\/pl\/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:56+00:00","author":{"@id":"https:\/\/www.archimetric.com\/pl\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28"},"description":"Zrozum DEEP w Scrum: szczeg\u00f3\u0142owe, szacowane, ewolucyjne i priorytetowe \u2014 cztery kluczowe cechy dobrze zarz\u0105dzanej listy produktu.","breadcrumb":{"@id":"https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.archimetric.com\/pl\/deep-product-backlog-scrum-agile\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.archimetric.com\/pl\/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\/pl\/deep-product-backlog-scrum-agile\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.archimetric.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Scrum: Co oznacza DEEP w Backlogu Produktu?"}]},{"@type":"WebSite","@id":"https:\/\/www.archimetric.com\/pl\/#website","url":"https:\/\/www.archimetric.com\/pl\/","name":"ArchiMetric Polish","description":"EA, Dev Ops, Scrum, Agile and More","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.archimetric.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Person","@id":"https:\/\/www.archimetric.com\/pl\/#\/schema\/person\/e4027c9f5b602fc705716009e5671d28","name":"archimetric@visual-paradigm.com","image":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/www.archimetric.com\/pl\/#\/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\/pl\/author\/archimetricvisual-paradigm-com\/"}]}},"_links":{"self":[{"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/posts\/10908","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/users\/3479"}],"replies":[{"embeddable":true,"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/comments?post=10908"}],"version-history":[{"count":0,"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/posts\/10908\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/media?parent=10908"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/categories?post=10908"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.archimetric.com\/pl\/wp-json\/wp\/v2\/tags?post=10908"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}