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 with any changes to the Cluster Backlog that were incorporated during the Cycle (e.g. in the Cluster Backlog Refinements), they provide the basis for working together on possible new entries that increase the value of the “Cluster products”. The Cluster Review is an informal meeting, not a status report in the classic sense. The presentation of the results is intended as a suggestion for feedback and the basis for cooperation. At the end of the Cluster Review, the Cluster Product Owner can give an update on costs and planned dates or milestones.

For a twelve-week Cluster Cycle , an upper limit of four hours is set as the time frame for this meeting. A corresponding shorter time frame is estimated for shorter cycles. The Cluster Scrum Master (CSM) ensures that the event takes place and that the participants understand its purpose. The CSM teaches everyone involved to hold the event within the given time frame.

The Cluster Review includes the following elements:

• The participants, consisting of the Team System Engineer Group (TSEG) and important stakeholders who are invited by the Cluster Product Owner . These are often also the POs of the teams, ie the Team Product Owner Group .
• The Cluster Product Owner explains which Cluster Backlog Items (CBI) have been completed.
• The TSEG shows what went well during the Cluster Cycle , which problems arose , and how it solved these problems. The TSEG may ask for support from the stakeholders.
• The TSEG shows the completed work results and answers questions about them. Work results can be:
  • Usable Knowledge and (design) decisions made by TSEG ,
  • an integrated version of the system, platform or application
• The Cluster Product Owner presents the current status of the Cluster Backlog . If necessary, it provides an updated forecast of probable target and delivery dates based on the development progress, e.g. by using a burn-up chart based on the working speed of the Cluster ( velocity )
• All participants work together on what to do next, so that the Cluster Product Owner receives valuable input for the upcoming Cluster Planning .
• Then the schedule, budget, as well as the potential properties and market expectations for the next version of the application (release) are checked.

The result of the Cluster Review is a revised Cluster Backlog that corresponds to the common level of knowledge of the participants and through which the TSEG can work on the Cluster Backlog Items with the highest value in the next Cluster Cycle . The Cluster Backlog can also be extensively reworked to take advantage of new opportunities.

Cluster Review alternatives

Often the Team Reviews are conducted directly before the Cluster Review, whereby the Team Reviews are usually more technical and the holistic aspects, such as costs, milestones, are shown at the Cluster level. This allows the Cluster Review to be much shorter. Including the Team Reviews, however, half a day to a full day must be allowed for.

If there are more than four Teams in the Cluster, it is also possible to organize the Team Reviews using “exhibition stands”. In this case, the teams show their results, as at a trade fair, and the stakeholders are the visitors.

.

Further suitable links: