Cluster-Planning in Cycles
Each Cycle begins with a Cluster Planning event. In this, the Cluster Product Owner of the Team System Engineer Group (TSEG) presents the current status of the Cluster Backlog . New entries or changes that have not been known to the TSEG since the last Cluster Backlog Refinement are estimated, supplemented by Acceptance Criteria and prioritized by the Cluster Product Owner within the Cluster Backlog.
The TSEG determines the Capacity for the next Cycle by looking at the previous “working speed” of the Cluster (Cluster Velocity) and by looking at the capacity of the Teams in the next Cycle.
The TSEG pulls the number of Cluster Backlog Items (CBI), which corresponds to the TSEG’s assessment of the Capacity in the next Cycle, into the Cycle Backlog of the Cluster. The Team Product Owners then use the TSEG to refine the CBIs in Team Backlog Items that are required to complete the CBIs.
Then the TSEG starts the Cycle by pulling the first items from “open” to “in progress”.
Continuous Cluster Planning
As an alternative to the planning rhythm in Cycles, the work for the Cluster can also be planned continuously. The Cluster Backlog Refinements are used for this, whereby the work on a Cluster Backlog Item can be started immediately after its analysis and estimation.
.
Further suitable links:\r\n
Further suitable links:
Events | Roles | Groups | Artifacts |
Team Planning
. . |
Cluster Product Owner | Team Product Owner Group | Cluster Backlog |