Cluster Backlog Refinement

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…

Cluster Cycle Transfer within the Inter Cycle Week

The Cluster Cycle  is a kind of large iteration at the Cluster level , it could also be called a “cluster iteration”. A similar cycle is usually also used for the Portfolio level of the entire Organization . The Cycle consists of several Iterations , a preamble consisting of   Cluster Planning and a trailer…

Cluster Cycle

The basic idea of the Iteration as a time-box for the Teams is used at Cluster level by the Cluster Cycle as a larger fixed period as a basic rhythm for the Cluster. Frequently, the System versions, products and Applications are also brought to the market in the rhythm of the Cluster Cycles. The advantage…

Cluster Planning

Cluster-Planning in Cycles Each Cluster-Cycle begins with a Cluster Planning event. In this, the Cluster Product Owner presents the current status of the Cluster Backlog to the Team System Engineer Group (TSEG). New entries or changes that have not been introduced to the TSEG since the last Cluster Backlog Refinement are estimated and supplemented by Acceptance Criteria…

Cluster Retrospective

The Cluster Retrospective offers the Cluster Scrum Master (CSM) the opportunity to review the working methods of the cluster, represented by the Cluster Product Owner and the Team System Engineer Group (TSEG) , as well as improvements in the way of working identify and plan for the coming cycle . The Cluster Retrospective takes place…

Cluster Review

At the end of each Cluster Cycle , a Cluster Review is held in which the Team System Engineer Group (TSEG) and the Cluster Product Owner (CPO) present the results to the stakeholders. They receive feedback from the stakeholders on the results so that the CPO can adjust the Cluster Backlog if necessary . Along…

Cluster Sync (Scrum-of-Scrums)

Cluster Sync (scrum-of-scrums) This event enables multiple Working Teams to communicate with each other in order to coordinate dependencies, disruptions, new findings and decisions, etc. with one another during ongoing work. The teams decide how often this is needed (e.g. daily or weekly). Depending on the context, there can be different types of Cluster Syncs,…

Iteration

The Iteration is a fixed length timebox for each of the Teams within a Cluster and corresponds to a constant basic rhythm. Usually, all Teams within the Cluster choose the same Iteration length, especially if they have interdependencies or supply relationships with each other.   Basically there is a choice between two, three or four…

Cadence

In the pragmatic-agile way of working, the working and decision-making processes are realized through purpose-bound recurring meetings, aka Events. This makes ad hoc meetings unnecessary or at least drastically reduces them. The frequency of the Events determines the maximum waiting time that a work element has to “wait” until it can be dealt with (daily,…

Organization Retrospective

The Organization Retrospective offers the Organization Scrum Master (OSM) the opportunity to review the working methods of the organization, represented by the Portfolio Owner (PFO) and the Cluster System Engineer Group (CSEG) , as well as improvements to the Identify and plan how to work for the coming cycle . The Organization Retrospective takes place…