{"id":395,"date":"2019-07-21T22:42:14","date_gmt":"2019-07-21T20:42:14","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=395"},"modified":"2026-04-01T15:53:10","modified_gmt":"2026-04-01T13:53:10","slug":"refinement","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/refinement\/","title":{"rendered":"Team Backlog Refinement"},"content":{"rendered":"

The <\/span><\/span>Team Backlog Refinement<\/span><\/span><\/a> is the process of <\/span>adding<\/span> details to the Team Backlog<\/a> entries, <\/span>making<\/span> estimates, and determining the order of the Team Backlog entries. <\/span>Refinement is a continuous process in which the <\/span><\/span>Team Product Owner<\/span><\/span><\/a> and the Working Team<\/a> together detail the Team Backlog entries. <\/span>When the Team Backlog is refined, the entries are examined and revised. <\/span>It should normally not take up more than 10% of the Working Team’s capacity. <\/span>However, the <\/span><\/span>Team Product Owner<\/span><\/span><\/a> can update or have the entries in the Team Backlog updated at any time.<\/span><\/span><\/p>\n

The Team Backlog Refinement mainly serves to prepare the next <\/span><\/span>Team Planning<\/span><\/span><\/a>. The Team Product Owner presents new team backlog items to the Working Team, and has them estimated by the Working Team.<\/span><\/span>\u00a0<\/span>If items are about to start, the team makes sure that the entries are small enough that they can be pulled into an iteration. <\/span>(This is a prerequisite for the “pull” and is often also referred to as part of the <\/span><\/span>Definition of Ready (DoR)<\/span><\/span><\/a>). <\/span>If this is not the case, the team refines the corresponding entry by splitting it into several entries.<\/span><\/span><\/p>\n

If the team does not work in iterations, but continuously using Kanban, the team agrees on an estimate limit from which it is necessary to split Backlog Items.<\/span><\/span><\/p>\n

Estimation of the implementation effort of backlog entries<\/span><\/span><\/h3>\n

Estimates by the entire team are important for two reasons<\/span><\/span><\/p>\n

    \n
  1. By estimating together, the entire team analyzes the respective backlog entry from different perspectives and enriches it with information such as acceptance criteria and boundary conditions. <\/span>The first ideas for implementation are also generated.<\/span><\/span><\/li>\n
  2. The result of the estimate is a number with which individual backlog elements can be evaluated, for example for prioritization. <\/span>In addition, it is now easy to calculate how many elements can be dragged into an iteration, namely by comparing the backlog elements completed in the last iterations (team <\/span><\/span>velocity<\/span><\/span><\/a> ).<\/span><\/span><\/li>\n<\/ol>\n

    The team uses the <\/span><\/span>Planning-Poker<\/span><\/span><\/a> \u00ae <\/span>method to estimate the effort <\/span>.<\/span><\/span><\/p>\n

    Consideration of Quality Attributes & Constraints, as well as Risks<\/h3>\n

    When refining backlog items, it is important to take existing Quality attributes and Constraint<\/a>s into account. They define the solution space within which the system design must operate.<\/p>\n

    Particularly important in regulated development: Continuous risk management<\/a> may result in additional measures that must be reflected in the planning within the Team Backlog<\/a> or changes may arise in the Quality Attributes and Constraints (Product QA&Cs<\/a>).<\/p>\n

    –<\/span><\/span><\/span><\/p>\n

    \n

    Further suitable links:<\/p>\n\n\n\n\n
    Events<\/td>\nRoles<\/td>\nGroups<\/td>\nArtifacts<\/td>\n<\/tr>\n
    Team Planning<\/a><\/p>\n

    Team Sync<\/a><\/p>\n

    Team Review<\/a><\/p>\n

    Team Retrospective<\/a><\/p>\n

    .<\/span><\/p>\n

    Cluster Backlog Refinement<\/a><\/p>\n

    .<\/span><\/p>\n

    Portfolio Refinement<\/a><\/td>\n

    		Team Product Owner<\/a><\/p>\n

    Team System Engineer<\/a><\/p>\n

    Team Scrum Master<\/a><\/td>\n

    		Working Team<\/a><\/p>\n

    Community of Practice<\/a><\/td>\n

    		Team Backlog<\/a><\/p>\n

    Inspectable Results<\/a><\/p>\n

    Team DoD<\/a><\/p>\n

    Team Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"The Team Backlog Refinement is the process of adding details to the Team Backlog entries, making estimates, and determining the order of the Team Backlog entries. Refinement is a continuous process in which the Team Product Owner and the Working Team together detail the Team Backlog entries. When the Team Backlog is refined, the entries…","protected":false},"author":3,"featured_media":1425,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,21],"tags":[350,348,353,354],"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\/395"}],"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=395"}],"version-history":[{"count":29,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/395\/revisions"}],"predecessor-version":[{"id":397,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/395\/revisions\/397"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1425"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=395"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=395"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=395"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}