The basic idea of the Iteration as a time-box for the Teams is used at Organization level by the Portfolio Cycle as a larger fixed period as a basic rhythm for the Organization. Frequently, the System versions, products and Applications are also brought to the market in the rhythm of the Portfolio Cycles. The advantage of a fixed rhythm is its predictability for the Teams, CLusters, managers and stakeholders. In practice, a Portfolio Cycle length of a quarter of a year has proven itself. There are the following options:
- 3 four-week iterations + 1 inter Cycle week
- 4 three-week iterations + 1 inter Cycle week
- 6 two-week iterations + 1 inter Cycle week
This results in 13 weeks per quarter, which corresponds quite accurately to the actual duration (4 x 13 = 52 weeks).
So, one Cluster Cycle consists of:
- Cluster Cycle Pre-Planning by the Team Product Owner Group (TPOG)
- Cluster Planning (all Teams incl. their POs)
- Cluster Cycle Post Planning (again TPOG)
- 3, 4 or 6 Iterations (of 4, 3 or 2 weeks).During the Iterations:
- Team Sync Meetings (Daily Scrums)
- Cluster Sync Meetings (Scrum-of-Scrums)
- Organization Sync (Scrum-of-Scrum-of-Scrums)
- Portfolio Backlog Refinement (by CPOG and CSEG)
- Cluster Backlog Refinements (by TPOGs and TSEGs)
- Team Backlog Refinements (by Working Teams and POs), and
- Team Reviews and Team Retrospectives
- Cluster Reviews (TPOGs + TSEGs + Stakeholder)
- Cluster Retrospectives (all Clusters)
The whole thing is shown in the following picture.
In the same way, the event of the Scrum Masters are interlocked across all three levels:
All Cluster Cycle meetings are held within the Inter Cycle Week, starting with the Cluster Review and ending with the Cycle Post-Planning.
.
Further suitable links:
| Events | Roles | Groups | Artifacts |
| Iteration
. |
Cluster Product Owner
. |
Team Product Owner Group
. |
Cluster Backlog
Usable Knowledge & System Increment . |