{"id":1818,"date":"2019-12-31T14:56:38","date_gmt":"2019-12-31T13:56:38","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=1818"},"modified":"2026-04-01T15:53:26","modified_gmt":"2026-04-01T13:53:26","slug":"clusterrefinement","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/clusterrefinement\/","title":{"rendered":"Cluster Backlog Refinement"},"content":{"rendered":"

Refinement of the <\/span><\/span>Cluster Backlog<\/span><\/span><\/a> is viewed as the process of <\/span>adding<\/span><\/a> details to backlog entries, <\/span>making<\/span><\/a> estimates, or determining the order of entries in the Cluster Backlog.<\/span><\/span><\/p>\n

Refinement is a continuous process in which the <\/span><\/span>Cluster Product Owner<\/span><\/span><\/a> and the <\/span><\/span>Team System Engineer Group<\/span><\/span><\/a> collectively detail the Cluster Backlog Items. <\/span>The entries are examined and revised as the Cluster Backlog is refined. <\/span>However, the Cluster Product Owner can update or have the entries in the Cluster Backlog updated at any time.<\/span><\/span><\/p>\n

The Cluster Backlog Refinement meetings mainly serve to prepare the next <\/span><\/span>Cluster Planning<\/span><\/span><\/a> . <\/span>The Cluster Product Owner presents new backlog items to the Team System Engineer Group (TSEG) and has them estimated by the TSEG. <\/span>If items are about to start, the TSEG makes sure that the items are small enough to be pulled into a cycle. <\/span>(This is a prerequisite for the “pull” and is often referred to as <\/span><\/span>definition-of-ready<\/span><\/span><\/a> ). <\/span>If this is not the case, the TSEG refines the corresponding entry by splitting it into several entries (splitting).<\/span><\/span><\/p>\n

Estimation of the effort required to implement backlog entries<\/span><\/span><\/h3>\n

Estimates by the entire Team System Engineer Group are important for two reasons:<\/span><\/span><\/p>\n

    \n
  1. By jointly estimating, the TSEG 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 estimation 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 backlog elements can be dragged into a cycle, namely by comparing the backlog elements completed in the last cycles ( <\/span><\/span>velocity of<\/span><\/span><\/a> the cluster).<\/span><\/span><\/li>\n<\/ol>\n

    The team uses the <\/span><\/span>Planning-Poker<\/span><\/span><\/a> \u00ae <\/span>methodology 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 Cluster Backlog<\/a>; or changes may arise in the Quality Attributes and Constraints (Product QA&Cs<\/a>).<\/p>\n

    How often does the cluster redefinition meeting take place?<\/h3>\n

    First of all, this depends on whether Cluster planning takes place continuously or per Cluster Cycle (usually per quarter).<\/p>\n

    For continuous Cluster planning, the Cluster Refinement should be held between weekly and once per (team) iteration.<\/p>\n

    For quarterly Cycles, at least once per iteration, but several times per quarter.<\/p>\n

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

    \n

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

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

    Cluster planning<\/span><\/span><\/a><\/p>\n

    Cluster Sync<\/span><\/span><\/a><\/p>\n

    Cluster Review<\/span><\/span><\/a><\/p>\n

    Cluster Retrospective<\/span><\/span><\/a><\/p>\n

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

    Portfolio refinement<\/span><\/span><\/a><\/td>\n

    		Cluster Product Owner<\/span><\/span><\/a><\/p>\n

    Cluster System Engineer<\/span><\/span><\/a><\/p>\n

    Cluster Scrum Master<\/span><\/span><\/a><\/td>\n

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

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

    Team Scrum Master Group<\/span><\/span><\/a><\/p>\n

    Cluster Management Circle<\/span><\/span><\/a><\/td>\n

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

    Usable Knowledge<\/span><\/span><\/a> & <\/span><\/span>System Increment<\/span><\/span><\/a><\/p>\n

    Cluster DoD<\/span><\/span><\/a><\/p>\n

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

     <\/p>\n","protected":false},"excerpt":{"rendered":"Refinement of the Cluster Backlog is viewed as the process of adding details to backlog entries, making estimates, or determining the order of entries in the Cluster Backlog. Refinement is a continuous process in which the Cluster Product Owner and the Team System Engineer Group collectively detail the Cluster Backlog Items. The entries are examined…","protected":false},"author":3,"featured_media":1425,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[22,5],"tags":[358,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\/1818"}],"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=1818"}],"version-history":[{"count":22,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1818\/revisions"}],"predecessor-version":[{"id":2138,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/1818\/revisions\/2138"}],"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=1818"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=1818"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=1818"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}