{"id":507,"date":"2019-08-11T21:33:17","date_gmt":"2019-08-11T19:33:17","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=507"},"modified":"2026-04-06T15:34:25","modified_gmt":"2026-04-06T13:34:25","slug":"backlogitemtypes","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/backlogitemtypes\/","title":{"rendered":"Backlog Item Types"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">&#8220;The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/backlog\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Backlog<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> is the only source of the work.&#8221; <\/span><span style=\"vertical-align: inherit;\">The general <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/backlog\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">description of\u00a0 Backlogs and their properties can be found here<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/p>\n<p>The hierarchy of the Backlog structure describes (in a simple way) the <a href=\"https:\/\/p4dev.hardscrum.com\/working_process\/\">product development process<\/a>.<\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Backlog entries or Backlog Items are the individual building blocks of backlogs. <\/span><span style=\"vertical-align: inherit;\">They are clearly ranked within the backlogs, i.e. clearly prioritized. <\/span><span style=\"vertical-align: inherit;\">The higher a backlog entry is, the more important it is and the earlier it is processed.<\/span><\/span><\/p>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Common Attributes<\/span><\/span><\/h2>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">All backlog entries have the following properties and attributes:<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">A unique short name or other <\/span><\/span><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">identification<\/span><\/span><\/strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> (e.g. a number)<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">A <\/span><strong><span style=\"vertical-align: inherit;\">description<\/span><\/strong><span style=\"vertical-align: inherit;\"> that is as short as possible but meaningful<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">An indication of who the <\/span><\/span><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">source<\/span><\/span><\/strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> or author of the backlog entry is. <\/span><span style=\"vertical-align: inherit;\">This should make it clear who you can ask if anything is unclear.<\/span><\/span><\/li>\n<li><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Acceptance criteria <\/span><\/span><\/strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">are defined for <\/span><span style=\"vertical-align: inherit;\">concretization and delimitation<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">(Optional) At the Portfolio and system level, the respective Product Owners estimate the <strong>benefit\/value<\/strong><\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> of Applications and Features. For this purpose, benefit values of different applications\/features are evaluated relatively against each other, whereby the Product Owners use Planning Poker, for example.<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">To indicate that the team\/group in question has performed an analysis and estimation, the estimated <\/span><\/span><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">effort <\/span><\/span><\/strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">is noted on the backlog entry<\/span><\/span><\/li>\n<\/ul>\n<h2><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Subdivision of Backlog Items according to Type, Level, Size and Format<\/span><\/span><\/h2>\n<h3><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Formats<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In software development, specifying Backlog Items in the format of <\/span><\/span><a href=\"https:\/\/en.wikipedia.org\/wiki\/User_story\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">User Stories<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> has<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> become common practice. <\/span><span style=\"vertical-align: inherit;\">Here, a user requirement is described in the form of a sentence (who wants what, why). <\/span><span style=\"vertical-align: inherit;\">P4 prefers the term Stakeholder Story here, since the users of the system represent only a part of the stakeholders.<\/span><\/span><\/p>\n<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Use_case\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Use Cases<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> that can be divided into different scenarios <\/span><span style=\"vertical-align: inherit;\">are often <\/span><span style=\"vertical-align: inherit;\">used for <\/span><span style=\"vertical-align: inherit;\">further elaboration<\/span><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Using <\/span><\/span><a href=\"https:\/\/de.wikipedia.org\/wiki\/Anforderung_(Informatik)\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Text Requirements<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , individual Components, interfaces and their capabilities, abilities and properties can be described.<\/span><\/span><\/p>\n<p>Significantly more information can be represented in graphical form. Standard diagrams, as defined in <a href=\"https:\/\/en.wikipedia.org\/wiki\/Unified_Modeling_Language\">UML<\/a> and <a href=\"https:\/\/en.wikipedia.org\/wiki\/Systems_modeling_language\">SysML<\/a>, can describe many structures and processes in such a way that only a few additional explanations are necessary. In order to describe requirements (and solutions) in a compact and &#8220;lean&#8221; way, <a href=\"https:\/\/en.wikipedia.org\/wiki\/Unified_Modeling_Language\">UML<\/a> and <a href=\"https:\/\/en.wikipedia.org\/wiki\/Systems_modeling_language\">SysML<\/a> diagrams have a clear advantage.<\/p>\n<h3><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Size<\/span><\/span><\/h3>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">For a Team to work on and finish<\/span><span style=\"vertical-align: inherit;\">\u00a0a <b>Team Backlog Item<\/b><\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">, it must be small enough to fit into an Iteration. <\/span><span style=\"vertical-align: inherit;\">Larger Backlog Items span multiple Iterations and<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> have to be divided into several TBIs. Backlog items on team level are typically Stories in many tools (e.g. Jira or Azure Boards). Larger backlog items are often called Epic, Feature, Initiative or Theme.<\/span><\/span><\/p>\n<h3><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Type and level<\/span><\/span><\/h3>\n<p>Each Backlog Item Type is described by its own <a href=\"http:\/\/p4dev.hardscrum.com\/definition-of-done\/\">Definition-of-Done<\/a>. The <a href=\"http:\/\/p4dev.hardscrum.com\/definition-of-done\/\">DoDs<\/a> can be different in different <a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\">Clusters<\/a> and <a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\">Teams<\/a>, but they must be consistent with the <a href=\"http:\/\/p4dev.hardscrum.com\/definition-of-ready\/\">Definitions-of-Ready (DoRs = &#8220;Definition of Ready&#8221;)<\/a> of the supplying organizational unit or the organizational unit to be supplied.<\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The sum of each Backlog Item level represents the total effort of product development or a <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/applications\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">System, Market or Application<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> variant that can be delivered.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">This is also the idea of \u200b\u200bEpics, Stories and Tasks that many Teams use when using Scrum. <\/span><span style=\"vertical-align: inherit;\">The sum of the effort in all Epics corresponds to the sum of the effort in all Stories. <\/span><span style=\"vertical-align: inherit;\">This is based on the (theoretical) assumption that a Story is done when all Tasks are done and an Epic is done when all the contained Stories are done. <\/span><span style=\"vertical-align: inherit;\">It is the same with the total effort.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">If an Application Team or the Cluster System Engineer Group is able <\/span><span style=\"vertical-align: inherit;\">to estimate <\/span><span style=\"vertical-align: inherit;\">all backlog entries based on the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/systemreq\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">System Requirements &amp; Functions<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> with the limiting <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/constraints\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Quality Attributes &amp; Constraints<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , the total effort of an application is completely estimated. <\/span><span style=\"vertical-align: inherit;\">Since this is usually not easy, the requirements must be <\/span><span style=\"vertical-align: inherit;\">broken down <\/span><span style=\"vertical-align: inherit;\">further to the solution level of the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/architecture\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">System Concepts, architecture and capabilities<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> . <\/span><span style=\"vertical-align: inherit;\">At this level, too, it will usually not be possible to estimate all concept elements precisely enough, as there are still many unknowns and uncertainties (in P4: <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/knowledgegaps\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Knowledge Gaps<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> ) regarding the feasibility and the type of implementation.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The concept of <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/knowledgegaps\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Knowledge Gaps<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> is based on the assumption that after closing all Knowledge Gaps, the product development is successfully completed. <\/span><span style=\"vertical-align: inherit;\">The sum of the efforts to close all Knowledge Gaps also corresponds to the total effort of product development. <\/span><span style=\"vertical-align: inherit;\">However, making the estimation possible at this level requires a certain amount of experience before the organization has learned to do so with sufficient accuracy.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Organizations normally estimate their efforts based on the <\/span><\/span><strong><a href=\"http:\/\/p4dev.hardscrum.com\/samples\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Samples &amp; Integrations<\/span><\/span><\/a><\/strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> , since the efforts to close the Knowledge Gaps, their boundary conditions and assumptions are defined in a much more concrete way and the backlog entries are refined down to the level of the simulations, patterns and prototypes to be built. <\/span><span style=\"vertical-align: inherit;\">It is important here that the incremental and possibly multiple generation and integration of patterns is sufficiently taken into account and depending on the degree of innovation and the degree of risk of Knowledge Gaps, several &#8220;proven-of-concepts&#8221; or disposable prototypes may be necessary.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">A further breakdown at the working level is necessary when <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/samples\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Samples &amp; Integrations<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> are implemented<\/span><\/span><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> by multiple teams. <\/span><span style=\"vertical-align: inherit;\">For this purpose, the Backlog Items are\u00a0<\/span><span style=\"vertical-align: inherit;\">divided <\/span><span style=\"vertical-align: inherit;\">into <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/teamgoals\/\"><strong><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Goals<\/span><\/span><\/strong><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> according to the Teams involved<\/span><span style=\"vertical-align: inherit;\">, and each Team estimates the effort they incur. <\/span><span style=\"vertical-align: inherit;\">These can be retrospectively assigned to actual expenses and the relative estimates standardized or calibrated.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">At every level of the backlog types, product development is completely described and appreciated. <\/span><span style=\"vertical-align: inherit;\">When using relative points for the assessment, a separate &#8220;effort currency&#8221; is used at each level. <\/span><span style=\"vertical-align: inherit;\">The currencies can be converted into each other if, after some time, data are available that show the speed at which the organization is developing at the various levels (<\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/velocity\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Velocity<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> ).<\/span><\/span><\/p>\n<p>&nbsp;<\/p>\n<hr \/>\n<p>Further suitable links:<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr style=\"background-color: #f8f8f8;\">\n<td>Events<\/td>\n<td>Roles<\/td>\n<td>Groups<\/td>\n<td>Artifacts<\/td>\n<\/tr>\n<tr style=\"background-color: #ffffff;\">\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/planning\/\">Team Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/refinement\/\">Team Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/review\/\">Team Review<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleplanning\/\">Cluster Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterrefinement\/\">Cluster Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cyclereview\/\">Cluster Review<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-planning\/\">Portfolio Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliorefinement\/\">Portfolio Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolio-review\/\">Portfolio Review<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\">Team Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemengineer\/\">Team System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\">Team Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpo\/\">Cluster Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemarch\/\">Cluster System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clustersm\/\">Cluster Scrum Master<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioowner\/\">Portfolio Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioarch\/\">Portfolio Architect<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisationsm\/\">Organisation Scrum Master<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\">Working Team<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cop\/\">Community of Practice<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/pogroup\/\">Team Product Owner Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systeminggroup\/\">Team System Engineer Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/smgroup\/\">Team Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cluster-management\/\">Cluster Management Circle<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterpogroup\/\">Cluster Product Owner Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sysarchgroup\/\">Cluster System Engineer Group<\/a><\/p>\n<p style=\"text-align: left;\"><a href=\"http:\/\/p4dev.hardscrum.com\/csmgroup\/\">Cluster Scrum Master Group<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/org-management\/\">Organisation Management Circle<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/teambl\/\">Team Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\">Team DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/improvementbacklog\/\">Team Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterbl\/\">Cluster Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterdod\/\">Cluster DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/clusterimprovementbacklog\/\">Cluster Improvement Backlog<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliobl\/\">Portfolio Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfoliodod\/\">Organisation DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/portfolioimprovementbacklog\/\">Organisation Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">\u00a0<\/span><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"&#8220;The Backlog is the only source of the work.&#8221; The general description of\u00a0 Backlogs and their properties can be found here. The hierarchy of the Backlog structure describes (in a simple way) the product development process. Backlog entries or Backlog Items are the individual building blocks of backlogs. They are clearly ranked within the backlogs,&hellip;","protected":false},"author":3,"featured_media":2337,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[20,565],"tags":[358,382],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/507"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=507"}],"version-history":[{"count":31,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/507\/revisions"}],"predecessor-version":[{"id":2815,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/507\/revisions\/2815"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/2337"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=507"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=507"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=507"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}