{"id":987514837,"date":"2023-09-20T16:48:33","date_gmt":"2023-09-20T15:48:33","guid":{"rendered":"https:\/\/pmchampions.com\/?p=987514837"},"modified":"2023-12-06T09:27:44","modified_gmt":"2023-12-06T09:27:44","slug":"how-to-build-the-product-backlog-mistakes-to-avoid","status":"publish","type":"post","link":"https:\/\/pmchampions.com\/en\/how-to-build-the-product-backlog-mistakes-to-avoid\/","title":{"rendered":"How to Build the Product Backlog: Mistakes to Avoid"},"content":{"rendered":"<p>[et_pb_section fb_built=&#8221;1&#8243; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; custom_padding=&#8221;18px|||||&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_row _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_column type=&#8221;4_4&#8243; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_image src=&#8221;http:\/\/pmchampions.com\/wp-content\/uploads\/2023\/10\/Product-Backlog-en.jpg&#8221; alt=&#8221;Product-Backlog-en&#8221; title_text=&#8221;Product-Backlog-fr&#8221; align=&#8221;center&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; border_radii=&#8221;on|10px|10px|10px|10px&#8221; border_color_all=&#8221;#E02B20&#8243; box_shadow_style=&#8221;preset3&#8243; global_colors_info=&#8221;{}&#8221;][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_column type=&#8221;4_4&#8243; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_text module_class=&#8221;star-list&#8221; _builder_version=&#8221;4.23.1&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h2>WHY A PRODUCT BACKLOG?<\/h2>\n<p>The Product Backlog is:<\/p>\n<ul>\n<li>The most important of the Scrum artifacts and any agile approach.<\/li>\n<li>The representation of the work to be done. It gives a shared vision of what the team will produce. It thus ensures transparent monitoring of the work and the client&#8217;s &#8220;requirements&#8221; with regard to the expected final product.  <\/li>\n<li>The <strong>WHAT<\/strong> of an agile project. As such, it must be established, maintained, updated and disseminated as quickly as possible.<\/li>\n<li>The single source of requirements for all changes to be made to the product. The <strong>Product Owner<\/strong> is responsible for the Product Backlog: its content, distribution and scheduling.<\/li>\n<li>The Product Backlog is not a functional specification document: it describes the <strong>WHAT<\/strong> rather than the <strong>HOW.<\/strong> Therefore, additional functional documentation may be required on a project.<\/li>\n<\/ul>\n<p>[\/et_pb_text][et_pb_text module_class=&#8221;star-list&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h2 class=\"expanded\">WHEN TO DO A PRODUCT BACKLOG?<\/h2>\n<ul>\n<li>The Product Backlog must be established from the beggining of the project, either by the Product Owner on the client side, or from the pre-sales phase.<\/li>\n<li>During the first workshops, the Product Owner adds the initially identified requirements to the Product Backlog.<\/li>\n<li>The Product Owner regularly updates the Product Backlog until the end of the project.<\/li>\n<li>The Product Backlog persists as long as the product exists, it has no end.<\/li>\n<\/ul>\n<p>[\/et_pb_text][et_pb_text module_class=&#8221;star-list&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h2 class=\"expanded\">WHO CREATES AND MAINTAINS THE PRODUCT BACKLOG?<\/h2>\n<ul>\n<li>The Product Owner is responsible for the Product Backlog: its content, distribution and scheduling.<\/li>\n<li>The <strong><a href=\"https:\/\/pmchampions.com\/en\/how-to-refine-the-product-backlog\/\" target=\"_blank\" rel=\"noopener\"> Product Backlog <\/a><\/strong>is not fixed. In an agile context, it evolves in line with changes in the product and its user environment.<\/li>\n<li>The Product Backlog is therefore flexible, undergoing continuous changes to align with the evolving needs of the product in order to deliver value.<\/li>\n<\/ul>\n<p>[\/et_pb_text][et_pb_text quote_border_weight=&#8221;10px&#8221; quote_border_color=&#8221;#E02B20&#8243; module_class=&#8221;pmc-bullet&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; quote_font=&#8221;Crete Round||||||||&#8221; quote_text_color=&#8221;rgba(0,40,76,0.91)&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h2>HOW DO YOU BUILD A PRODUCT BACKLOG?<\/h2>\n<h3>Product Backlog Content<\/h3>\n<p>The Product Backlog lists the items that define the product:<\/p>\n<ul>\n<li>Main features: The key features of the product or project.<\/li>\n<li>Technical tasks: The technical work required to implement features.<\/li>\n<li>Bugs and fixes: Problems to resolve and corrections to make.<\/li>\n<li>Improvements: Suggestions for improvements or optimizations to the product.<\/li>\n<li>Business Requirements: The functional and non-functional requirements of the customer or users.<\/li>\n<\/ul>\n<p>In an agile framework, we recommend writing items in the form of <strong>User Stories<\/strong>.<\/p>\n<p>Product Backlog items are ranked according to their <strong>Business<\/strong> priority. Estimation comes later, when selecting items to include in a given sprint. <\/p>\n<h3>The Sprint 0<\/h3>\n<p>The Product Owner holds several meetings to create the Product Backlog. Methods used include:<\/p>\n<ul>\n<li>Work workshops.<\/li>\n<li>Individual interviews.<\/li>\n<li>Use of questionnaires.<\/li>\n<\/ul>\n<blockquote><p>Each meeting with users should have a specific objective, agreed upon when scheduling the meetings. If necessary, the Product Owner can be assisted by the Quality Analyst and\/or the Business Analyst. <\/p><\/blockquote>\n<p>It is possible to organize a meeting halfway through Sprint 0 to present the first progress.<\/p>\n<p><span style=\"font-size: 18px;\">In general, during Sprint 0, we identify the <strong>Minimum Viable Product (MVP)<\/strong> , which consists of defining the product with the minimum number of features necessary to satisfy the user and obtain initial feedback.<\/span><\/p>\n<h3>Formalization<\/h3>\n<p>The Product Backlog can be created in Excel table, with for each item of the Product Backlog, at least:<\/p>\n<ul>\n<li>Description: As&lt; role&gt; , I can&lt; action&gt; in order to&lt; result&gt;<\/li>\n<li>Priority: within the Product Backlog<\/li>\n<li>Size: in load and\/or complexity<\/li>\n<li>A Business Value: Business Value of the User Story<\/li>\n<li>Acceptance criteria: Given&lt; a state of the application&gt; , When&lt; action&gt; SO&lt; result&gt;<\/li>\n<li>The Epic&#8217;s benchmark<\/li>\n<\/ul>\n<blockquote><p><span class=\"ms-rteStyle-References\">Other columns can be added in ad hoc mode, as you go along, such as an iterative distribution column, a status column (&#8220;New&#8221;, &#8220;Ready&#8221;, &#8220;In Progress&#8221;, &#8220;Done&#8221;)<\/span><\/p><\/blockquote>\n<p>[\/et_pb_text][et_pb_image src=&#8221;http:\/\/pmchampions.com\/wp-content\/uploads\/2023\/09\/BacklogPrioritized.png&#8221; alt=&#8221;Prioritized Backlog&#8221; title_text=&#8221;BacklogPrioritized&#8221; align=&#8221;center&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; width=&#8221;85%&#8221; width_tablet=&#8221;85%&#8221; width_phone=&#8221;85%&#8221; width_last_edited=&#8221;on|tablet&#8221; module_alignment=&#8221;center&#8221; border_radii=&#8221;on|10px|10px|10px|10px&#8221; box_shadow_style=&#8221;preset1&#8243; global_colors_info=&#8221;{}&#8221;][\/et_pb_image][et_pb_button button_url=&#8221;https:\/\/www.atlassian.com\/software\/jira&#8221; url_new_window=&#8221;on&#8221; button_text=&#8221;Jira Starting Guide (to come)&#8221; button_alignment=&#8221;center&#8221; _builder_version=&#8221;4.23&#8243; _module_preset=&#8221;fee02489-cb44-4d68-a726-05506d10cbf1&#8243; button_text_color=&#8221;#0C71C3&#8243; button_bg_color=&#8221;RGBA(255,255,255,0)&#8221; button_border_width=&#8221;1px&#8221; button_border_color=&#8221;#0C71C3&#8243; button_font=&#8221;|700|||||||&#8221; global_colors_info=&#8221;{%22gcid-8cdb4e16-0e89-4c38-b30b-9fe41127e3f5%22:%91%22button_bg_color%22%93}&#8221;][\/et_pb_button][et_pb_text _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h3>Refinement (Grooming) of the Product Backlog<\/h3>\n<p>Early items in the <strong>Product Backlog<\/strong> are more detailed, allowing for a more accurate estimate, while later items are less detailed.<\/p>\n<p>The elements of the next Sprint are refined to be achievable in one Sprint and are ready for planning.[\/et_pb_text][et_pb_button button_url=&#8221;https:\/\/pmchampions.com\/fr\/comment-affiner-le-product-backlog\/&#8221; button_text=&#8221;Article About Backlog Grooming (to come)&#8221; button_alignment=&#8221;center&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;940cac81-1de1-4297-a1e2-3f6f53317ba6&#8243; button_text_color=&#8221;#0C71C3&#8243; button_bg_color=&#8221;RGBA(255,255,255,0)&#8221; button_border_width=&#8221;1px&#8221; button_font=&#8221;|700|||||||&#8221; global_colors_info=&#8221;{%22gcid-af6245ea-df40-48a8-9687-67293107dc0c%22:%91%22button_text_color%22%93}&#8221;][\/et_pb_button][et_pb_text _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]Updating the Backlog is a crucial part of the life of such an artifact, and it&#8217;s done by the Product Owner. The latter can modify the Backlog at any time[\/et_pb_text][et_pb_blurb title=&#8221;Attention !&#8221; use_icon=&#8221;on&#8221; font_icon=&#8221;s||divi||400&#8243; icon_color=&#8221;#FFFFFF&#8221; image_icon_background_color=&#8221;RGBA(255,255,255,0)&#8221; image_icon_width=&#8221;40px&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; header_level=&#8221;h2&#8243; header_font=&#8221;Quicksand|700||on|||||&#8221; header_text_align=&#8221;center&#8221; header_text_color=&#8221;#FFFFFF&#8221; header_font_size=&#8221;20px&#8221; body_font=&#8221;Quicksand|700||on|||||&#8221; body_text_align=&#8221;center&#8221; body_text_color=&#8221;#FFFFFF&#8221; body_font_size=&#8221;16px&#8221; body_line_height=&#8221;1.3em&#8221; background_enable_color=&#8221;off&#8221; use_background_color_gradient=&#8221;on&#8221; background_color_gradient_stops=&#8221;#e07674 0%|rgba(224,11,0,0.81) 13%|#e00b00 88%|rgba(224,28,17,0.64) 100%&#8221; image_icon_custom_margin=&#8221;||-8px||false|false&#8221; image_icon_custom_padding=&#8221;||||false|false&#8221; width=&#8221;60%&#8221; width_tablet=&#8221;60%&#8221; width_phone=&#8221;60%&#8221; width_last_edited=&#8221;on|phone&#8221; max_width=&#8221;100%&#8221; module_alignment=&#8221;center&#8221; custom_margin=&#8221;||||false|false&#8221; custom_padding=&#8221;15px|5px|15px|5px|false|false&#8221; header_text_shadow_style=&#8221;preset3&#8243; header_text_shadow_color=&#8221;#000000&#8243; border_radii=&#8221;on|10px|10px|10px|10px&#8221; border_color_all=&#8221;#000000&#8243; border_width_all_image=&#8221;0px&#8221; box_shadow_style=&#8221;preset3&#8243; global_colors_info=&#8221;{}&#8221;]No modifications are allowed on the User Stories of the <span style=\"text-decoration: underline;\">current sprint !<\/span>[\/et_pb_blurb][et_pb_text quote_border_weight=&#8221;10px&#8221; quote_border_color=&#8221;#E02B20&#8243; module_class=&#8221;pmc-bullet&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; quote_font=&#8221;Crete Round||||||||&#8221; quote_text_color=&#8221;rgba(0,40,76,0.91)&#8221; global_colors_info=&#8221;{}&#8221;]No modifications are allowed on the User Stories of the current sprint, except in exceptional situations such as:<\/p>\n<ul>\n<li>In case of extreme emergency.<\/li>\n<li>When a User Story has become obsolete.<\/li>\n<li>After negotiation, in exchange for the deletion of a User Story of equivalent size that has not yet started.<\/li>\n<li>By taking care not to overload the team, because it is committed to a simple and well-defined scope.<\/li>\n<\/ul>\n<blockquote><p>It is possible to modify the rest of the Product Backlog, but it is essential to take the scope into account, particularly in the context of a fixed-price project.<\/p><\/blockquote>\n<p>[\/et_pb_text][et_pb_text module_class=&#8221;pmc-bullet&#8221; _builder_version=&#8221;4.23.1&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h3>Product Backlog Estimation<\/h3>\n<p>The Backlog <strong><a href=\"https:\/\/pmchampions.com\/en\/planning-poker-estimating-user-stories-in-5-steps\/\" target=\"_blank\" rel=\"noopener\">estimation<\/a><\/strong> process is an ongoing process that occurs as follows:<\/p>\n<ul>\n<li>The initial estimate is made during the <a href=\"https:\/\/pmchampions.com\/en\/how-to-apply-contract-effectively-to-agile-project\/\" target=\"_blank\" rel=\"noopener\"><strong>pre-sales<\/strong><\/a> phase, which represents the initial size of the Backlog.<\/li>\n<li>During <a href=\"https:\/\/pmchampions.com\/en\/facilitating-a-sprint-planning-guide-and-tips\/\" target=\"_blank\" rel=\"noopener\"><strong>Sprint Planning<\/strong><\/a> meetings and <strong><a href=\"https:\/\/pmchampions.com\/en\/how-to-refine-the-product-backlog\/\">Product Backlog<\/a><\/strong> reviews, the estimate is revised to reflect the current size.<\/li>\n<\/ul>\n<p>The Development Team is responsible for the estimate, although the <strong>Product Owner<\/strong> can influence by providing information and guidance, it is the team members who provide the final estimate.[\/et_pb_text][et_pb_button button_url=&#8221;https:\/\/pmchampions.com\/en\/planning-poker-estimating-user-stories-in-5-steps\/&#8221; button_text=&#8221;Read This Article article : %22Facilitating a planning Poker%22&#8243; button_alignment=&#8221;center&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;940cac81-1de1-4297-a1e2-3f6f53317ba6&#8243; button_text_color=&#8221;#0C71C3&#8243; button_bg_color=&#8221;RGBA(255,255,255,0)&#8221; button_border_width=&#8221;1px&#8221; button_font=&#8221;|700|||||||&#8221; global_colors_info=&#8221;{%22gcid-af6245ea-df40-48a8-9687-67293107dc0c%22:%91%22button_text_color%22%93}&#8221;][\/et_pb_button][et_pb_text _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h3>Focus on Technical Tasks<\/h3>\n<div class=\"group w-full text-token-text-primary border-b border-black\/10 gizmo:border-0 dark:border-gray-900\/50 gizmo:dark:border-0 bg-gray-50 gizmo:bg-transparent dark:bg-[#444654] gizmo:dark:bg-transparent\" data-testid=\"conversation-turn-197\">\n<div class=\"p-4 justify-center text-base md:gap-6 md:py-6 m-auto\">\n<div class=\"flex flex-1 gap-4 text-base mx-auto md:gap-6 md:max-w-2xl lg:max-w-[38rem] xl:max-w-3xl }\">\n<div class=\"relative flex w-[calc(100%-50px)] flex-col gap-1 md:gap-3 lg:w-[calc(100%-115px)]\">\n<div class=\"flex flex-grow flex-col gap-3 max-w-full\">\n<div class=\"min-h-[20px] flex flex-col items-start gap-3 overflow-x-auto whitespace-pre-wrap break-words\">\n<div class=\"markdown prose w-full break-words dark:prose-invert light\">\n<p>It is essential to include technical tasks in the Product Backlog and estimate them.<\/p>\n<p>Example of non-functional technical task:<\/p>\n<blockquote><p><strong>As a<\/strong> front-end developer, <strong>I want to<\/strong> optimize website images using lossless image compression, <strong>so that<\/strong> the site loads faster for users and improves user experience.<\/p><\/blockquote>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<p>[\/et_pb_text][et_pb_text module_class=&#8221;star-list&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h2>Recommendations: Mistakes to Avoid<\/h2>\n<p>The ten mistakes to avoid in Product Backlog management:<\/p>\n<ul>\n<li>Not having a Product Backlog.<\/li>\n<li>Having multiple Product Backlogs for a single product (or other spurious sources).<\/li>\n<li>Not sharing the Product Backlog with the entire team.<\/li>\n<li>Do not update the Product Backlog during the project.<\/li>\n<li>Not prioritizing items or giving them equal priorities.<\/li>\n<li>Having elements that are too precise and\/or too vague in the Product Backlog ( <strong>INVEST<\/strong> criteria).<\/li>\n<li>Not having enough ready elements to supply the development team during the next Sprint.<\/li>\n<li>Constantly adding new items without evaluating their value or priority.<\/li>\n<li>Not actively involving the Product Owner in managing and updating the Product Backlog.<\/li>\n<li>Ignore end-user feedback when adding or editing items in the Product Backlog<\/li>\n<\/ul>\n<p>[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row module_class=&#8221;pmc-bullet&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; background_color=&#8221;#ffdbc4&#8243; custom_margin=&#8221;30px||30px||false|false&#8221; custom_css_main_element=&#8221;overflow:visible&#8221; border_radii=&#8221;on|0.25rem|0.25rem|0.25rem|0.25rem&#8221; border_width_all=&#8221;1px&#8221; border_color_all=&#8221;#dee2e6&#8243; box_shadow_style=&#8221;preset3&#8243; box_shadow_vertical=&#8221;5px&#8221; box_shadow_blur=&#8221;15px&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_column type=&#8221;4_4&#8243; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_blurb title=&#8221;Free Tools&#8221; image=&#8221;http:\/\/pmchampions.com\/wp-content\/uploads\/2023\/10\/complementary.png&#8221; alt=&#8221;key point&#8221; icon_placement=&#8221;left&#8221; content_max_width_tablet=&#8221;&#8221; content_max_width_phone=&#8221;&#8221; content_max_width_last_edited=&#8221;on|phone&#8221; _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; header_font=&#8221;Acme||||||||&#8221; header_font_size=&#8221;22px&#8221; background_color=&#8221;#edf8ff&#8221; image_icon_custom_margin=&#8221;1px|0px|0px|0px|false|false&#8221; image_icon_custom_padding=&#8221;||||false|false&#8221; width=&#8221;200px&#8221; width_tablet=&#8221;200px&#8221; width_phone=&#8221;200px&#8221; width_last_edited=&#8221;on|desktop&#8221; max_width=&#8221;200px&#8221; max_width_tablet=&#8221;200px&#8221; max_width_phone=&#8221;200px&#8221; max_width_last_edited=&#8221;on|desktop&#8221; module_alignment=&#8221;center&#8221; custom_margin=&#8221;-55px||||false|false&#8221; custom_margin_tablet=&#8221;-55px||||false|false&#8221; custom_margin_phone=&#8221;-55px||||false|false&#8221; custom_margin_last_edited=&#8221;on|phone&#8221; custom_padding=&#8221;5px|5px|0px|5px|false|false&#8221; child_filter_saturate=&#8221;200%&#8221; header_font_size_tablet=&#8221;22px&#8221; header_font_size_phone=&#8221;22px&#8221; header_font_size_last_edited=&#8221;on|phone&#8221; border_radii=&#8221;on|0.25rem|0.25rem|0.25rem|0.25rem&#8221; border_width_all=&#8221;1px&#8221; border_color_all=&#8221;#dee2e6&#8243; box_shadow_style=&#8221;preset3&#8243; box_shadow_horizontal=&#8221;6px&#8221; box_shadow_vertical=&#8221;11px&#8221; box_shadow_blur=&#8221;8px&#8221; text_shadow_style=&#8221;preset1&#8243; text_shadow_vertical_length=&#8221;0.15em&#8221; text_shadow_blur_strength=&#8221;0.3em&#8221; global_colors_info=&#8221;{}&#8221;][\/et_pb_blurb][et_pb_text _builder_version=&#8221;4.22.0&#8243; _module_preset=&#8221;default&#8221; custom_padding=&#8221;|30px||30px|false|false&#8221; global_colors_info=&#8221;{}&#8221;]<strong>View a list of free tools for managing the <a href=\"https:\/\/teamhood.com\/kanban\/backlog-management-tools\/\" target=\"_blank\" rel=\"noopener\">Product Backlog<\/a><\/strong>[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this article, discover the secrets of the product backlog: development from sprint zero, formalization, refinement, estimation and errors to avoid.<\/p>\n","protected":false},"author":1,"featured_media":987514839,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[59,29],"tags":[24],"class_list":["post-987514837","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile-contracting-and-planning","category-agility","tag-en"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/posts\/987514837","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/comments?post=987514837"}],"version-history":[{"count":0,"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/posts\/987514837\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/media\/987514839"}],"wp:attachment":[{"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/media?parent=987514837"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/categories?post=987514837"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pmchampions.com\/en\/wp-json\/wp\/v2\/tags?post=987514837"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}