{"id":1897,"date":"2020-01-11T16:45:06","date_gmt":"2020-01-11T15:45:06","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1897"},"modified":"2020-07-21T14:09:25","modified_gmt":"2020-07-21T12:09:25","slug":"backlog","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/backlog\/","title":{"rendered":"Backlog (generic)"},"content":{"rendered":"

A Backlog is an ordered list of everything known that <\/span>should be carried out <\/span>by an organizational unit (<\/span><\/span>Team<\/span><\/span><\/a> , group, <\/span><\/span>Cluster<\/span><\/span><\/a>, <\/span><\/span>Organization<\/span><\/span><\/a> ) and serves as the only source of work by this organizational unit. <\/span>The <\/span><\/span>Product Owner<\/span><\/span><\/a> is responsible for the Backlog, its content, access to it and the order of the entries.<\/span><\/span>
\nA backlog contains only the currently known entries. <\/span>During the development steps it develops with the products and services and their application. <\/span>It is dynamically adjusted to clearly indicate for products and services what it takes to perform their tasks appropriately, to survive in the competition and to offer the greatest possible benefit. <\/span><\/span>
\nIf products and services exist, there are also the associated product, system or application backlogs.<\/span><\/span><\/p>\n

A <\/span><\/span>Backlog Item<\/span><\/span><\/a>\u00a0contains as attributes a description, an effort estimate, as well as acceptance criteria and test descriptions, which prove the completeness and describe when it is done [“Done”].<\/span><\/span><\/p>\n

“The backlog is the only source of work.” <\/span>This principle does the following important things:<\/span><\/span><\/p>\n